I almost despaired when trying to get the popular RSS server Tiny Tiny RSS working with Traefik. I’ve also tested other RSS reader, but none have pleased me as much as ttrss.
Since I got it working after a long time of testing, I would like to show you here how I got it working.
In my example, the docker configuration files are located unter /opt/containers/.
So first we navigate to this path and clone the GIT repository:
git clone https://git.tt-rss.org/fox/ttrss-docker-compose.git ttrss && cd ttrss
Then we copy the configuration file and adjust the content:
cp .env-dist .env
TTRSS_DB_USER=postgres TTRSS_DB_NAME=postgres TTRSS_DB_PASS=
So this means in my case I’ve created a subdomain ttrss.example.com which will then be used by traefik to set up the certificate etc.
Now we need to create a docker-compose.override.yml file where we add the traefik labels and network settings.
version: '3' services: web-nginx: networks: - proxy - default labels: - "traefik.enable=true" - "traefik.docker.network=proxy" - "traefik.http.routers.ttrss.entrypoints=http" - "traefik.http.routers.ttrss.rule=Host(`ttrss.example.com`)" - "traefik.http.services.ttrss.loadbalancer.server.port=80" - "traefik.http.middlewares.ttrss-secured.redirectscheme.scheme=https" - "traefik.http.routers.ttrss-secured.rule=Host(`ttrss.example`)" - "traefik.http.routers.ttrss-secured.entrypoints=https" - "traefik.http.routers.ttrss-secured.tls.certresolver=production" networks: proxy: external: true
Publish the configuration file:
…and start the container:
docker compose up
Now the website should be reachable over https://ttrss.example.com/tt-rss/.
When going productive, of course it makes more sense to use
docker compose up -d
I was following your example very, very closely. But for some weird reason I get an error:
web-nginx_1 | 2022/05/18 18:50:55 [error] 27#27: *41 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: „GET /tt-rss/index.php HTTP/1.1“, upstream: „fastcgi://172.20.0.5:9000“, host: „localhost“
web-nginx_1 | 127.0.0.1 – – [18/May/2022:18:50:55 +0000] „GET /tt-rss/index.php HTTP/1.1“ 502 157 „-“ „curl/7.80.0“
I guess it means that web-nginx can’t talk to app, because it requests the index.php on the proxy network, not the internal one.
That does not happen if I expose the port directly without traefik.
What am I doing wrong?
I had the same issue. You have to attach the app container to the proxy and the internal network (please see my updated docker-compose.yml above). Then it worked for me.
Seems we’re not the only one with this. See https://community.traefik.io/t/tt-rss-is-selecting-the-wrong-network-for-internal-communication/14500 and https://community.tt-rss.org/t/docker-compose-with-multiple-networks-and-reverse-proxy-fails-ambiguous-container-id/4390.
I hope this helps you.
Could you share your web-nginx/nginx.conf?
I can’t make webnginx: use the internal network to talk to app:
It is not necessary to adapt the original docker-compose.yml.
Instead you create a docker-compose.override.yml file where you put the network definitions and labels for traefik.
This works really well and is independent from the source code – important during updates.
Needless to say that you can also add other changes there like mounting plugins.local to filesystem for easier installation of custom plugins.
Thanks for the comment! have adjusted the article accordingly.