Sometimes, you might have to delete one or two config files. Once deleted, run systemctl restart nginx. If the error is related to bad config files,ĭelete the bad config files (this is safe, cloudron can always re-generate nginx files). If it is not running,Ĭheck the nginx logs using journactl -u nginx -fa. If the domain looks ok (see above), check if Nginx is running using systemctl status nginx. Move all the apps one by one from the old domain to the new domain by changing the location.ĭelete the old domain and remove the entry we added earlier from /etc/hosts. Add the new domain.Ĭhange the dashboard domain to this new domain. You may have to purge the site from your browser's history to get over HSTS certificate issues. This works because the browser always looks up the /etc/hosts file first before looking up the DNS. With the above entry in place, you can visit in your browser.

Edit your PC/Mac's /etc/hosts and add an entry (the old domain and not the new one) to point to the server.

If the domain has expired and you do not intend to renew it, switch to another domain as follows: Go to Domains view and click the Sync DNSīutton to re-add Cloudron related DNS records. Wait and a bit for the DNS to propagate and login to the dashboard. In such situations, add a DNS A record for my. to point to the server's IP. Some registrars, won't revertīack your old DNS records. Most registrars replace your DNS with parking pages until you renew. If the domain has expired and you renew it, you have to wait a bit for the DNS records to come back. In most cases, you can check this quickly using whois. Expired domainĬheck with your registrar if the domain has expired. Please go through the itemsīelow in order to identify where the issue might be. The Cloudron dashboard can become unreachable for a variety of reasons.

Collabora code lamp