Also is that the domain the site is on? Because it looks like there’s no DNS records pointing to it, which means 1. nobody can access it and 2. lets-encrypt can’t verify the domain and won’t give you a certificate
By deploy logs I mean the terminal output when you deploy.
Now that the DNS is setup, you will likely need to tell mup to setup the proxy and request a certificate again. I think the command for that is mup reconfig
I think I have to run again mup setup, but my concerns is: will it delete my mongo db and reinstall everything again? I have a backup but it is huge and takes more than an hour to restore.
Also, make sure you can reach the site without an entry in your hosts file before using using reconfig.
I just checked and it looks like the nameserver change hasn’t propagated
It’s showing digitalocean as the DNS server but no A or cname records on digitalocean’s dns servers