Complete amateur here. I had to remove Sendgrid because I was being overcharged for my small site, so I switched to SMTP2Go. I received the instructions for what to use for Discourse, and made the changes via the discourse-setup command in the console. Since I did that, I cannot access the forum b…

[изображение] NFULFX: Can anyone tell me though WHY on earth this happened by just changing the SMTP values?? I did a docker logs -f app and saw errors about LETSENCRYPT_ACCOUNT_EMAIL being invalid (it appears to have the value “OFF” in your earlier versions of the file). I changed it to your…

Im not sure, but i think you can change SMTP details in app.yml then rebuild? And as you have done it by discourse setup, maybe you should grey out the “a” record and re-try it in 5 minutes, to install it in the correct ip adress. Hope its helps

It should be caused by the lack of an HTTPS (443) inbound rule in the DO cloud firewall rules. Please check the DigitalOcean firewall rules under Inbound Rules to see if there is an HTTPS (443) rule. If not, try adding it.

@David_Ghost I tried removing the “A” entries, waiting about 15 mins, and then re-added them. No change. (BTW, I assumed you meant the A entries in Cloudflare. Tell me if I misunderstood you). But yes, I did check the app.yml detail via the “nano” command and everything appears correct. @anoedo The…

That’s not correct. You should edit the “A” record to set it as “DNS ONLY” (grey cloud) temporally then re do a discourse setup after 5 minutes. It should works

Understood. The “A” for the forum was proxied. I have set it to “DNS Only”. I’ll wait the 5 minutes then run the setup again. Will report results.

It actually let me get through the discourse-setup process this time (although it DID let me the very first time 8-ish hours ago). I did not get any port errors, and the rebuild completed. I still have the same issue. I appreciate the response!! g2ic.com which auto-forwards to forum.g2ic.com does …

I will be back later tonight to check on things. But would really appreciate any thoughts or further suggestions. Thank you very, very much for reading. Maybe there’s a clue in the rebuild app log? I don’t know how to record that, but if anyone can tell me how, I’ll gladly post that when I get home…

I did leave it grey for a while, then went back to proxied because all my other subdomains were proxied (orange). I’ll leave it grey from now on until this is resolved. Thanks!

It looks like you were rate limited and don’t have a certificate so nginx won’t start up. You’ll need to wait until the rate limit is over or add another subdomain (maybe the apex domain) using hostname aliases as described at Set up Let’s Encrypt with multiple domains / redirects You’ll need to po…

Сменили почтовый сервис: теперь форум не открывается ни по IP-адресу, ни по URL

Поддержка Самостоятельное хостинг

pfaffman (Jay Pfaffman) 11.Октябрь.2025 21:28:16 9

You still have the orange cloud. This keeps let’s encrypt from getting a certificate. And after a few tries, you get rate limited.

Тема		Ответов	Просм.
Port 443 Blocked on Discourse Digital Ocean With One Click Support	14	1197	05.08.2020
WARNING: Port 443 of computer does not appear to be accessible using hostname: forum.rlv.link Self-hosting	12	4832	03.01.2021
Cannot send mail with Discourse on new install but can from command line (on digital ocean) Self-hosting	8	2284	01.06.2020
Misconfigured DNS preventing discourse-setup completion Self-hosting	13	1808	21.03.2020
Troubleshooting Port Access Self-hosting	25	1639	18.08.2020

Сменили почтовый сервис: теперь форум не открывается ни по IP-адресу, ни по URL

Связанные темы