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: bin…

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. Set up Let’s Encrypt with multiple domains / redirects

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

새 호스트의 SSL

제품 지원 자체 호스팅

pfaffman (Jay Pfaffman) 5월 1, 2024, 7:03오후 5

아마도 rsync를 사용하여 Discourse 사이트를 다른 VPS로 이동하기를 참고해 보세요.

글		댓글	조회수
SSL Let's Encrypt Error After Installation Product Support	8	1464	2월 22, 2019
Letsencrypt issued on every build? Product Support	7	1512	2월 28, 2022
Getting error when setting up Let's Encrypt SSL on GCP Self-hosting	10	1574	10월 22, 2019
Workaround for the 1 week Let's Encrypt limit Self-hosting	2	1354	6월 16, 2023
Trying to use Let's Encrypt + Cloudflare Product Support	19	3614	2월 2, 2019

새 호스트의 SSL

Related topics