Hi all, I’m migrating to a new server and I want to use Traefik 2.0 as a reverse proxy. I’m currently struggling with the new configuration. I added a section at the bottom of the app.yml file. (Source: Discourse behind Traefik 🐭 ) ... expose: - "8060:80" # http - "8070:443" # https ... do…

After some trying I could solve it by my own. For further notice I attach my app.yml: ... templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" ## Uncomment these two lines if you wish to a…

[Bild] SvenC56: docker_args: why it is neccessary to sue docker_args? According to https://github.com/discourse/discourse_docker#labels it shall work like: labels: monitor: 'true' app_name: {{config}}_discourse Add labels to the current container. The above will add --l monitor=true -l …

@Cameron_D how did you find out that docker_args is the way to go? [Bild] Discourse behind Traefik mouse installation I never got the labels section working, so I just have a docker_args section that looks like this: docker_args: - "--network=web" - "--expose=80" -…

I just couldn’t get the labels section working as expected. I’m not sure exactly why it wasn’t working anymore, or whether or not its been fixed since because I’ve just left my configuration as-is because its working.

Hi there, can you share your traefik configuration? I end up with 302, redirects automatically to https and then it ends… Traefik dashbord says all ok. ▶ my docker-compose.yml is here ▶ my discourse app.yml is here

There were problems make Traefik’s dashboard available via a subdomain but discourse is still not reachable, see https://community.containo.us/t/discourse-instance-is-handled-by-api-internal-is-that-normal/3690/1 Here are my working configs. With my comments ▶ docker-compose: traefikV2_docker-co…

@Cameron_D @SvenC56 @Cerix @huberfe sorry for tagging your directly but it looks like that you are the only documented users running discourse behind Traefik. Albeit there promise, that Traefik will take care about anything it seems not so simple to set up. So far, I haven’t been successful: ▶ …

As i am only on my mobile, please check my config here: traefik - SeAT Discourse Documentation Please Note: i only had it running with v1.6 and v1.7 of traefik. No idea if that will work with v2 With that multiple users were able to use my plugin, use discourse and traefik. Note: i haven’t read a…

thx a ot :slight_smile: :partying_face: [Bild] huberfe: Please Note: i only had it running with v1.6 and v1.7 of traefik. No idea if that will work with v2 I will try to translate it from v1 to v2. I’m already getting an idea out of it, need some hours to think through it. I assume that th…

[Bild] PackElend: I assume that the templates for SSL and Let’s Encrypt are commmented so the to the template section looks like yeah why would you want the discourse container to manage your ssl-certificates, if you are about to enable a proxy infront? [Bild] PackElend: I will try to tr…

[Bild] huberfe: yeah why would you want the discourse container to manage your ssl-certificates, if you are about to enable a proxy infront? in Run other websites on the same machine as Discourse - #301 see [Bild] Run other websites on the same machine as Discourse Just thinking out loud. …

Diskussion mit Traefik 2.0

Unterstützung Installation

PackElend (Pack Elend) 30. November 2019 um 19:09 4

@Cameron_D
wie bist du darauf gekommen, dass docker_args der richtige Weg ist?

Thema		Antworten	Aufrufe
Solved: Discourse behind Traefik Self-hosting	6	1858	11. Juni 2022
Run other websites on the same machine as Discourse Self-Hosting advanced-setup , how-to	66	137490	23. Februar 2025
Fresh install returning 502 Bad Gateway Self-hosting unsupported-install	28	922	11. April 2024
Inaccessible behind Traefik Proxy Self-hosting	2	523	15. Februar 2024
Discourse working with jwilder /nginx proxy & acme-companion Self-hosting	7	5548	9. Februar 2022

Diskussion mit Traefik 2.0

Verwandte Themen