Apologies for this being the millionth question about this topic, however I’m still struggling to understand my issue even after looking over many of them!
I have an app deployed to Netlify ( gearcloset.io
). I have purchased the domain from Namecheap. I also want to deploy a Discourse app to DigitalOcean at the url forums.gearcloset.io
.
Currently when I visit the forums url, I receive an error:
The site can't be reached. ERR_CONNECTION_REFUSED
I think I’m very close, I’m just getting extremely confused knowing what records to put where! Please let me know if there is any other information I can provide.
- Netlify name:
gear-closet.netlify.app
Hey @frubalu
In the Netlify Domains section of the UI, add a new record for forums.gearcloset.io
pointing to the Droplet.
Also see
Hi @coelmay, I actually do already have an A record for “forums.gearcloset.io” pointing to the IPv4 address I’m seeing in DigitalOcean.
I don’t see it
% dig forums.gearcloset.io +all
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32348
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.gearcloset.io. IN A
;; Query time: 4 msec
;; SERVER: fe80::be30:d9ff:febc:408b%7#53(fe80::be30:d9ff:febc:408b%7)
;; WHEN: Fri Jun 10 09:24:31 AEST 2022
;; MSG SIZE rcvd: 49
That’s odd, because when I run the same dig command, I can see the IP address?
dig forums.gearcloset.io +all
; <<>> DiG 9.10.6 <<>> forums.gearcloset.io +all
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31357
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;forums.gearcloset.io. IN A
;; ANSWER SECTION:
forums.gearcloset.io. 2910 IN A 143.244.177.225
;; Query time: 97 msec
;; SERVER: 2001:558:feed::1#53(2001:558:feed::1)
;; WHEN: Thu Jun 09 16:25:20 PDT 2022
;; MSG SIZE rcvd: 65
Likely this is why I can’t see it:
It is still propagating to some parts of the world it appears.
1 Like
Any help would be much appreciated!
Well I’m not sure what exactly changed, but I ended up rerunning the build script for the Discourse app, and now it works. Classic.