mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 23:15:57 +03:00
[GH-ISSUE #137] Install script issue #2023
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2023
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kpdillon on GitHub (Oct 11, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/137
On installation of new Digital Ocean Droplet, install script does not complete.
Starting meshcentral and waiting for it to install plugins
Mesh Central not ready yet...
Mesh Central not ready yet...
Mesh Central not ready yet..
@dinger1986 commented on GitHub (Oct 11, 2020):
What spec is the droplet? Usually you get this message with a very low spec machine, slow disks and low ram
@wh1te909 commented on GitHub (Oct 11, 2020):
yep, install always hangs at that point when you don't have enough RAM. The bare minimum for the install script to complete is 2GB, 4GB is needed once you start adding agents.
@kpdillon commented on GitHub (Oct 11, 2020):
ok, yes I was only using 1GB for testing. The other issue is openssl doesn't seem to be easily recognizing the TXT records. I am having hit and miss success with this.
@dinger1986 commented on GitHub (Oct 11, 2020):
How quickly after adding the TXT record are you hitting enter? I find the fastest I can do it is after 5 minutes, on some dns providers this will be longer.
@kpdillon commented on GitHub (Oct 11, 2020):
I'll try waiting more than 5 minutes to see if that helps, thank you!
@Omnicef commented on GitHub (Oct 11, 2020):
In regards to the TXT record... the TTL matters. Whatever that number is,
you need to wait at least that long if it is a record you are changing and
is not a new record.
On Sun, Oct 11, 2020 at 11:36 AM kpdillon notifications@github.com wrote:
--
Anthony Fenech
909-992-2031
Anthony@Synergy-Computer.com
@kpdillon commented on GitHub (Oct 11, 2020):
Is there a way to restart the script without rebuilding the droplet? It seems if it fails more than 3 times and I restart the install script I get a looped error on trying to obtain a new cert
@dinger1986 commented on GitHub (Oct 11, 2020):
Agreed to the TTL, but some hosts update it quicker than the TTL it depends what DNS servers the lookups are against. If it’s direct the TTL shouldn’t matter which is how I think letsencrypt works.
@dinger1986 commented on GitHub (Oct 11, 2020):
There’s no way to restart the script, best to rebuild the server and start again. You don’t want to try and verify it too many times with letsencrypt as eventually they will block requests or automatically decline them. Best to verify using https://dnslookup.online/txt.html or similar.
@wh1te909 commented on GitHub (Oct 12, 2020):
closing this please re-open if still have issues installing