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…

Hard to help without knowing the domain. What happens when you try a verbose curl from another machine in the internet to your domain.tld ?

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: [изображение] 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 gener…

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 Connecting your domain us…

Установка без поддомена не работает

Поддержка Самостоятельное хостинг

Stephen (Stephen) 09.Октябрь.2022 18:00:56 8

Вы уже читали:

Тема		Ответов	Просм.
Discourse Let’s Encrypt Failing Self-hosting letsencrypt	2	593	04.11.2022
New installation not appearing at domain name or IP address Self-hosting	6	838	21.09.2023
Site not showing after following official installation walkthrough Self-hosting	3	628	13.04.2020
Defaults domain Support	8	677	26.12.2019
WARNING: This server does not appear to be accessible at Self-hosting	11	2802	19.03.2020

Установка без поддомена не работает

Связанные темы