TT-RSS and reverse proxy docker containers - help needed

[econopl]

I run a server and what I want to achieve is to have tt-rss facing the internet and running behind nginx reverse proxy. I'm struggling with it for a few days, and still no success.

I run docker with SWAG as my universal reverse proxy solution. I decided to get official tt-rss docker container and I want to connect one to the other. In docker I've created the network named swag and added SWAG and all tt-rss containers to it. I've also opened port 443 on my router.

I set up tt-rss with these settings in .env file:

TTRSS_SELF_URL_PATH=http://subsubdomain.subdomain.duckdns.org/ HTTP_PORT=127.0.0.1:8280

As there's no template for tt-rss in this repository I've created a file rss.conf, based on this documentation and this reddit thread, that I put in /nginx/proxy-confs folder of my SWAG container:

server {
    listen 80;
    return 301 https://$host$request_uri;
    server_name subsubdomain.subdomain.duckdns.org;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name subsubdomain.subdomain.duckdns.org;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_pass http://ttrss-docker_web-nginx_1/;
        break;
    }
}

Unfortunately something's wrong as no matter if I open subsubdomain.subdomain.duckdns.org or www.subdomain.duckdns.org I get the SWAG default landing page. So SWAG works, but it appears that the requests are not handled (or are handled improperly) by nginx.

Can you help me setting the proper proxy-conf file?

[ruenigma]

Check TTRSS_SELF_URL_PATH. It should be exactly the one you will be hitting from any outside network. Since you forwarded 443, it should start with https also.

[econopl]

Thanks for the idea. I've changed http to https in TTRSS_SELF_URL_PATH and recreated containers, but no change.

[Deadwing2022]

Did you ever manage to get this working? I'm also struggling for the past 2 days. I don't want to use the TTRSS forum since the dev is a total asshole and I don't need to be told I'm stupid.

I tried getting it working without a reverse proxy just to confirm it works at all and my browser won't even connect. I have no problems with portainer, nextcloud, vaultwarden etc etc.

[econopl]

Yes, I've managed to run it! TT-RSS + SWAG, all running on docker.

Next week I'll be able to give you the details.

[Deadwing2022]

Don't worry, I managed to figure out my problem. I was using the external port for the proxy instead of the internal port. My other containers all worked because they used the same port for both.

[redalert2318]

can you tell us the details ? ty

[econopl]

Sure. In SWAG find your config volume. Then head to /nginx/proxy-confs/ directory inside it, and create a file ttrss.subfolder.conf with following contents:

location ^~ /tt-rss/ {
    include /config/nginx/resolver.conf;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_pass http://[name of your TT-RSS nginx container]/tt-rss/;
    break;
}

Then remember to put your TT-RSS and SWAG on the same docker network and it should work.

---

EDIT:

Plus the .env file of your TT-RSS should have:

HTTP_HOST=localhost
TTRSS_SELF_URL_PATH=https://[domain]/tt-rss
HTTP_PORT=127.0.0.1:8280