I’ve been up all night! I changed host, but I realize lets encrypt is the culprit, now I can’t use full ssl, only Cloudflare edge, I changed host, same app.yml file, same everything, why won’t lets encrypt work?
I also see this error Warning: Could not create server TCP listening socket *:6379: bind: Address already in use note, its a fresh server, took me hours to upload large backup too, I really don’t want to rebuild server again. I need help
AI-generated summary
SSL Issues after Changing Host
Genesis is experiencing issues with Let’s Encrypt after changing hosts, despite using the same app.yml file. The error message “Could not create server TCP listening socket *:6379: bind: Address already in use” is displayed.
Genesis rebuilt the server multiple times, which led to hitting Let’s Encrypt rate limits. pfaffman suggests turning off Cloudflare’s orange cloud, waiting a week, or using a different host name to resolve the issue.
Alternatively, pfaffman recommends checking if copying the certificates from the old server could work, referencing the guide Move a Discourse site to another VPS with rsync.
Turn off cloudflare orange cloud.
If you rebuilt a bunch of times then you’re hit let’s encrypt rate limits. You will need to wait a week or use or add a different host name.
I did turn it off, I stayed up all night, from the get go it wasn’t working, hence the rebuild, server rebuild till it worked with me adding back # to the ssl templates, do I have to wait a whole week? And won’t a different host name mess it up? Can let’s encrypt remove my ban any sooner?
would it work if I copy the certificates from old server?
Perhaps, see Move a Discourse site to another VPS with rsync