Hello, I am trying to setup Lets Encrypt SSL, so while installing discourse, I tried setting the email for Lets encrypt but I got below error :- Checking your domain name . . . WARNING:: This server does not appear to be accessible at domainex.com:443 . A connection to http://domainex.com (port …

Your discourse server is not at http://domainex.com/ . Click the link you included. You’ll need to update your DNS to make it point to your discourse server. If there is something that could make that message more clear, please suggest it.

Hi Jay, that is an just an example link

Then it’s impossible to diagnose. Is it the case that your DNS does point to your server and the ports are open?and you can access discourse with your hostname? If so, you can ignore those warnings [image] WallBB: you might try anyway And see what happens. I don’t know under what condition…

Hi pfaffman, I am able to access my domain and see the Congratulations page on discourse in http scenario, only thing is I get Error host not found if I try to access the account activate link. But this is a different issue. Now regarding the original issue, I pasted the exact message from discour…

[image] WallBB: only thing is I get Error host not found if I try to access the account activate link. But this is a different issue. I suspect that is the same issue. If you can’t share your domain name, I can’t help. One possibility is that you have two A records.

Hi Jay, I do have two A records, one is www and one is without www in GCP. Should I delete www ?

I mean that you may have two A records for your hostname. Only the hostname that you put in app.yml is checked by the script. If you think your DNS is right you can try enabling let’s encrypt. The evidence that I have is that you have something wrong.

Ah, hostname was incorrect :slight_smile: If I just rename the hostname, it should work pfaffman or I need to use launcher ?

For other people who see this in the future and have the same problem. I had to enable the port through firewall on Ubuntu sudo ufw allow 443/tcp

Getting error when setting up Let's Encrypt SSL on GCP

Product Support Self-hosting

Antichrist Octobre 22, 2019, 12:21 11

Pour les autres personnes qui verront cela dans le futur et qui rencontrent le même problème.
J’ai dû activer le port via le pare-feu sur Ubuntu
sudo ufw allow 443/tcp

Sujet		Réponses	Vues
Minimum needed to get LetsEncrypt working on a GCE instance Product Support	3	1328	Juin 21, 2017
No connection accepted on http / https after fresh installation on Ubuntu 22.04 LTS Self-hosting	5	2541	Décembre 16, 2022
Let's Encrypt: Azure hostname issue Self-hosting	14	2185	Octobre 14, 2017
Lets Encrypt Certificate - Issuing Problem Self-hosting	2	773	Novembre 6, 2023
Using letsencrypt inside Discourse Self-hosting letsencrypt	11	938	Mars 22, 2019

Getting error when setting up Let's Encrypt SSL on GCP

Sujets connexes