@joseph Now what should I do?
vaibhav
Posts
-
queryNs ECONNREFUSED for SSL Renewal -
queryNs ECONNREFUSED for SSL RenewalResponse by running the command:
[OK]node version is correct
[OK]docker is running
[OK]MySQL is running
[OK]nginx is running
[FAIL]Could not load dashboard website with loopback check -
queryNs ECONNREFUSED for SSL RenewalHi,
I'm reaching out for assistance with a critical issue on my Cloudron instance running on AWS Lightsail. After several months of inactivity, I've logged back in to find all SSL certificates expired.
While restarting the instance didn't trigger a renewal, I was able to access the Cloudron interface by temporarily changing my system date. However, manual SSL renewal attempts are getting stuck.
The logs consistently show the following error message:
box:dns/waitfordns Attempt 1 failed. Will retry: queryNs ECONNREFUSED sterlingspares.app
This error repeats multiple times daily.To troubleshoot further, I've even opened all ports on the firewall, but the issue persists. I'm at a loss for solutions and would greatly appreciate your help in resolving this matter.
Here's what I've done so far:
- Confirmed all SSL certificates are expired
- Restarted the Cloudron instance (unsuccessful in renewing certificates)
- Accessed Cloudron interface by temporarily changing system date (workaround, not a solution)
- Attempted manual SSL renewal (stuck, not completing)
- Checked Cloudron logs and identified the "queryNs ECONNREFUSED" error
- Opened all firewall ports (no improvement)
What I need help with:
Understanding the cause of the "queryNs ECONNREFUSED" error and how to resolve it
Successfully renewing the expired SSL certificates on my Cloudron instanceI've included relevant details about my setup to expedite the troubleshooting process. Any assistance you can provide would be much appreciated.
-
Cloudron Installation on a fresh AWS does not workSetup script hanged in the earlier cases.
-
Cloudron Installation on a fresh AWS does not workI have since deleted those other stuck VPS instances.
-
Cloudron Installation on a fresh AWS does not workI managed to fix it @girish.
Applying the commands in the terminal did not work.
I then asked AWS to apply these instructions while creating a new instance.Worked like a charm.
But in hindsight, my original attempts should have worked. I dunno why it didn't. -
Cloudron Installation on a fresh AWS does not workI have created a new VPS on AWS lightsail (2 GB RAM, 2 vCPUs, 60 GB SSD) 22.04 Ubuntu
I have run the commands as mentioned individually with sudo
wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setupNginx is running.
I have opened all ports (temporarily)
IP is 13.202.121.11Opening the same IP on https does not work for initial config
running the below command
tail -f /var/log/cloudron-setup.logsays:
# the nologin will also disable su/login. hardcoding uid helps in restoring if ! id yellowtent 2>/dev/null; then useradd --system --uid 808 --comment "Cloudron Box" --create-home --shell /usr/sbin/nol ogin yellowtent fi # add support user (no password, sudo) if ! id cloudron-support 2>/dev/null; then useradd --system --comment "Cloudron Support (support@cloudron.io)" --create-home --no- user-group --shell /bin/bash cloudron-support fi
I have tried destroying the VPS and redoing only to get the same result.
Please help.