The user, Matt_Shields, is troubleshooting port access issues while installing Discourse on Digital Ocean. They encountered errors related to port 443 and port 80 accessibility when using a subdomain (discourse.wewiser.co), despite having DNS records configured in Cloudflare pointing to their Digital Ocean IP. The issue was resolved by ensuring the DNS record for the subdomain was correctly set as an A record and by updating the domain name in the app.yml file to wewiser.co instead of discourse.wewiser.co. After rebuilding the app, the site became accessible, though SSL was initially not implemented. The user then faced email delivery issues with SendGrid, which was confirmed by Discourse Doctor as accepted by the SMTP server but not appearing in SendGrid logs. IAmGav suggested checking for misspelled domains, which was addressed by Matt_Shields Matt_Shields.
I have 2 A records in cloudflare that point to Digital Ocean.. isn’t that the only DNS records needed? I also have a number of cname set up but that is for sendgrid
hmm… So if I enter in the hostname simply as somedomain.co it will connect.. however if I enter it as discourse.somedomain.co then it can’t reach the port… are you not supposed to include discourse in the host name?
got it… just reloaded it and now it looks like the SSL is not implemented.. maybe I just need to rebuild the entire thing… distry this instance and launch a new one and update the ips?