A user is experiencing connection issues with their Discourse installation on a DigitalOcean VPS, receiving a ‘Connection Refused’ error when accessing the server’s IP address. Despite opening ports and testing with Apache, the issue persists. The user has followed the official Discourse installation guide and confirmed Docker is running, with the Discourse container active and ports exposed. The problem appears to be related to Let’s Encrypt certificate issuance, as the user has hit the rate limit of five certificates per week, preventing the SSL setup from completing. Attempts to bypass SSL by removing the email configuration and rebuilding the app have not resolved the issue. The user is considering waiting for the limit to reset or exploring alternative solutions, such as using a different domain or seeking help with multi-domain SSL configuration. LouisPiaf, Falco, and pfaffman have provided troubleshooting steps and insights into the certificate issue.
I’ve purchased a VPS from digital ocean and used there one click install for discourse droplet.
After entering the domain name etc. and doing the standard set up. Every time I go to my vps ip address (discourse has been installed on the main domain which I’ve pointed to the vps ip). Every time I go to the vps ip. It keeps saying:
This site can’t be reached
(MY-VPS-IP) refused to connect.
Try:
Checking the connection
[Checking the proxy and the firewall]
ERR_CONNECTION_REFUSED
I’ve opened the http and https ports as well and thats showing as open when I run the sudo ufw status command.
I’ve tried clearing my cache in case its a browser local issue; but still no luck.
Any suggestions/help? If anyone has any ideas or needs additional information; feel free to post below.
Droplet ip: 104.248.170.134 (it’s got the domain robloxfrance.com pointing towards it. But i’ve only recently updated the dns records to point the domain to the ip.)
Docker ps output:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0296e70dba0b local_discourse/app “/sbin/boot” 6 minutes ago Up 6 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app
We tried this command: sudo systemctl restart docker.service
Which worked for a split second when we refreshed the web page (brought up ngix web server) but when we refreshed again; it went back to refused to connect.
We also ran: docker run -it --rm hello-world
which was executed fine and without error.
At the moment we’re thinking it could be a discourse issue and not a docker issue.
We’re currently re-configuring the discourse installation on the vps, so we dont use the lets encrypt email.
update:
Update:
We re-configured the installation and ran the normal installation and didnt ass the lets encrypt email. And now we’re back to the first situation of it refusing to connect.
It sounds like you’ve hit the let’s encrypt rate limits. It’s hard to figure out how not to use let’s encrypt, so you’re probably still requesting the certificate (but now if the certificate is going to expire, you won’t get a warning via email). If I’m right, then you can
wait until next week (easy unless you’re impatient)
use a different domain name (easy, unless you really love your name or are bad at DNS)