I know this has been discussed before, but most of the older discussions regarded older versions of both discourse and traefik - so I’m standing here and need help :smiley: What works? Discourse was reachable from the outside and working fine until I commented out every exposed port. Traefik is r…

[изображение] Karsten: traefik.http.services.discourse.loadbalancer.server.port Try port 80, not 3000

[изображение] Karsten: Trying to reach Discourse gives me a bad gateway error, That suggests that your container is broken somehow, but that you have successfully configured traefik to connect to it, so you probably want to get back to that. Perhaps you didn’t wait long enough for the web ser…

Thank you, @pfaffman ! I have waited a while (11 hours, and that computer isn’t THAT slow) - and that does not solve it. I wonder if I managed to force discourse to connect to my network named “proxy”. Is there any way to check that? docker ps tells me that discourse no longer uses ports, which is…

./launcher enter app wget www.google.de shows me that discourse is connected to the internet. But I can’t reach it from the outside…

IT WORKS!!! Thank you VERY, VERY much. This was bothering me for a week now.

Решено: Обсуждение за Traefik

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

pfaffman (Jay Pfaffman) 12.Май.2022 01:49:58 5

Попробуйте порт 80, а не 3000

Тема		Ответов	Просм.
Inaccessible behind Traefik Proxy Self-hosting	1	561	15.02.2024
Discourse with Traefik 2.0 Self-hosting	42	9151	22.02.2020
Discourse behind Traefik on a subdomain Self-hosting	2	1091	27.01.2020
Ghost Discourse integration Support	0	675	31.05.2021
Discourse behind Traefik :mouse: Self-hosting	7	4080	03.06.2018

Решено: Обсуждение за Traefik

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