I have the cloudflared daemon running properly and have used it for tons of stuff(meaning the tunnel is installed properly on the server), but I am having trouble getting the Discourse setup(./discourse-setup) to recognize my hostname for my Discourse instance. I am using biohacking.forum as the h…

You have to edit the yml file and enter smtp credentials

Hey, do you have the grey cloud (dns only) for the “A” record before the ./discourse-setup?

I am not using a standard A record, I am using cloudflare tunnels. Here an example of a service that works perfectly on my server(with cloudflare tunnels) and the associated config: Ghost CMS is the service: PORT: 8085:2368 (8085 is host and 2368 is service) HOSTNAME: joshuahabka.com Cloudflare …

So for Discourse I would assume the port is: 443:443 (host:service) which is why I had my original Cloudflare tunnel setup as shown above

Hi @joshhabka :wave: perhaps this topic will help, if you haven’t already seen it [image] Install Discourse on a residential internet with Cloudflare Tunnel Sysadmins Since Discourse now has support for running on a Raspberry Pi , running a small instance in y…

Hi Lilly, the aforementioned guide did not work for me, I still receive the same error even though my cloudflare tunnel configuration is http://localhost:80 as stated I am still stuck on starserver@Starserver:/var/discourse$ sudo ./discourse-setup Ports 80 and 443 are free for use 'samples/standal…

Turning off " Always Use HTTPS Redirect all requests with scheme “http” to “https”. This applies to all http requests to the zone." makes it so port 80 succeeds but not 443

Enabling a page rule to redirect to HTTPS also causes both 80 and 443 to fail, but if I dont use it then 443 fails and 80 succeeds.

[image] Josh U: Lilly, the aforementioned guide did not work for me, You’re not following the instructions. You can’t use discourse-setup except to have it create the yml file. [image] Install Discourse on a residential internet with Cloudflare Tunnel Follow How to install Discourse in p…

Thank you, I am now stuck here: FAILED -------------------- Pups::ExecError: /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end' failed with return #<Process::Status: pid 134 exit 1> Location of failure: /usr/local/l…

Completed that and all is nominal now. I would just put a note in the self-install for cloudflare tunnel post that people need to edit the yaml doc to add their smtp, hostname, emails, etc Thank you!

Tunnels Cloudflare - Configuration de Discourse ne reconnaît pas le nom d'hôte (port inaccessible)

Soutien Installation

Lilly Septembre 28, 2024, 10:06 5

Salut @joshhabka
peut-être que ce sujet vous aidera, si vous ne l’avez pas déjà vu

4 « J'aime »

Sujet		Réponses	Vues
Misconfigured DNS preventing discourse-setup completion Self-hosting	13	1816	Mars 21, 2020
Troubleshooting Port Access Self-hosting	25	1662	Août 18, 2020
Connectivity issues during installation Self-hosting	14	931	Février 5, 2024
WARNING: Port 443 of computer does not appear to be accessible using hostname: forum.rlv.link Self-hosting	12	4847	Janvier 3, 2021
I am trying to install Discourse on Ubuntu BUT it's not working Self-hosting	14	1138	Avril 1, 2021

Tunnels Cloudflare - Configuration de Discourse ne reconnaît pas le nom d'hôte (port inaccessible)

Sujets connexes