更改了电子邮件服务,现在论坛无法通过 IP 地址或 URL 解析

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 by IP or url: forum.g2ic.com

I didn’t make any changes to anything else, so I’m at a loss what’s wrong. I have rebuilt the app several times with no difference.

There was another person who had this issue but he had Wordpress running at the same port, but I don’t have anything like that. I ONLY changed the SMTP info.

Can anyone give me ANY insight? I’m willing to pay for help – I’ve been struggling with this for the past 7 hours. I just need this resolved.

Cloudflare is handling my DNS

DigitalOcean is the host.

Thank you thank you thank you

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 There was no cloud firewall enabled on the droplet. I added it per your instructions. It’s been active for about 5 minutes. No change as of right now.

I can try doing the discourse-setup again to see whether it gives me a new message about that port. Maybe?

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

1 个赞

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 not work and I get a “host” error. I try inputting the IP address only and still get the same error.

Any other ideas? :frowning:

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.

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

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 point the other host name to the server with another A record (or cname if it’s a subdomain)