Hi there, I’m trying to install Discourse on a testbed fresh Ubuntu 20.04 VM (also tried CentOS Stream 9 and Ubuntu 22.04 and openSUSE MicroOS). I have some experience with Discourse since the early days of the project, and I’m now evaluating it for a migration. In that case it would be to mydomain.…

My best guess is that you did a bunch of rebuilds with something misconfigured and now let’s encrypt won’t issue a certificate because of rate limiting. If that’s the case you can wait a week or try using www as the subdomain, which is really a good idea these days anyway. You can look at the logs…

Hi thanks for the reply. OK that’s a good idea, looks it’s not accepting the connection: $ curl -v mydomain.tld * Trying 1.2.3.4:80... * connect to 1.2.3.4 port 80 failed: Connection refused * Failed to connect to mydomain.tld port 80: Connection refused * Closing connection 0 curl: (7) Failed to…

It’s unlikely. Where’s the server hosted? What sits between it and the client? Giving us the FQDN helps us do some troubleshooting. As-is you’re asking us to help diagnose this whilst blindfolded, so it may take a while to pinpoint.

Was this instance installed using discourse-setup, or did you manually create the YML file? Have you verified that 80/443 are open at Hetzner? Let’s encrypt is enrolled as standard these days, hence the redirect to a secure port.

I used discourse-setup. Yes, the ports are open. Installing to a subdomain works fine, and I also setup a Docker installation of a mailserver with a web frontend on this same VM (but I later reformatted it).

Have you read: [Bild] Configure your hosted Discourse site to run at the root or apex domain (e.g. example.com) Hosted Customers Most hosted discourse instances are on a subdomain: forum.example.com talk.example.com www.example.com This is our general reco…

Hmm no. The registrar is Hover, they’re normally pretty good. That’s bizarre, in 20 years of setting up servers I’ve never had problems with websites at the root of a domain…

I don’t recall it working for the one domain I had at Hover, but that was a while back. You could try swapping your NS to CloudFlare and testing whether DNS is the issue from there at no cost.

Thanks a lot for pointing me to this. You could try swapping your NS to CloudFlare and testing whether DNS is the issue from there at no cost. Sorry for the dumb question, do you mean setting my local DNS server to Cloudflare? (I’m currently using 8.8.8.8) Or using a different DNS service for my…

I asked Hover about it, and they pointed me to this: What you could do is try using an Glue record. This will make your server as the DNS manager and route the domain name to a nameserver you can set up using Glue records. Basically your server becomes the nameserver https://help.hover.com/hc…

No, I mean you don’t need to move your domain between registrars, but you will need to update the NS records at Hover for your domain to point it at a different providers DNS to test this theory. At present they’re set to ns1.hover.com and ns2.hover.com It’s a very quick and pretty painless process…

Installation ohne Subdomain funktioniert nicht

Unterstützung Installation

itsbhanusharma (Bhanu Sharma) 10. Oktober 2022 um 05:02 19

Wenn Sie mehr als ein paar Mal versucht haben, neu zu erstellen, werden Sie wahrscheinlich von Let’s Encrypt Raten-limitiert. Sie können dies umgehen, indem Sie Ihrer Zertifikat eine weitere Hostnamen hinzufügen.

Thema		Antworten	Aufrufe
Discourse Let’s Encrypt Failing Self-hosting letsencrypt	2	570	4. November 2022
New installation not appearing at domain name or IP address Self-hosting	6	788	21. September 2023
Site not showing after following official installation walkthrough Self-hosting	4	602	13. Mai 2020
Defaults domain Support	9	593	25. Januar 2020
WARNING: This server does not appear to be accessible at Self-hosting	11	2757	19. März 2020

Installation ohne Subdomain funktioniert nicht

Verwandte Themen