Documentation: docker[-]compose and Apache reverse proxy configuration

Tiny Tiny RSS Support
1
  • [X] I’m using stock [docker compose] setup, unmodified.
  • [ ] I’m using docker compose setup, with modifications (modified .yml files, third party plugins/themes, etc.) - if so, describe your modifications in your post. Before reporting, see if your issue can be reproduced on the unmodified setup.
  • [ ] I’m not using docker on my primary instance, but my issue can be reproduced on the aforementioned docker setup and/or official demo.

Dear valued TT-RSS community and developer(s),

please apologize for any errors or mistakes. Being a very long time TT-RSS self-hoster, I am totally new to the now (since quite some time) recommended docker setup and to this forum.
I struggled a lot setting up this standard installation - at two different points:

Firstly, I figured “docker-compose” is now “docker compose” - maybe somebody could correct that in the docs: https://git.tt-rss.org/fox/ttrss-docker-compose.git/tree/README.md?h=static-dockerhub
(sorry, no clue how to do this myself)

Second, and maybe it’s totally my fault, but I think the example configuration for Apache reverse proxy in the installation guide / environment: https://git.tt-rss.org/fox/ttrss-docker-compose.wiki.git/tree/Home.md#apache-this-assumes-youre-using-https is wrong.
At the end, I figured I have to append tt-rss/ to the 127.0.0.1:8020/ URLs in the apache ProxyPass and ProxyPassReverse directives. Please note that I am serving tt-rss in the /tt-rss directory so that might be the reason, however I don’t believe so. If that’s really would suggest the someone who can edit the above page corrects the example (like the nginx example which seems correct).

I understand that documentation and this forum is focusing on TT-RSS and not on Docker or reverse proxy configurations, however I believe the standard installation documentation should be in a way that people without much knowledge in those areas should be able to follow it and end up with a working setup.

Many thanks for your understanding and for you work on tt-rss and this community!

  • Tiny Tiny RSS version (including git commit id): latest as per May 5, don’t know how to find the exact commit id
  • Platform (i.e. Linux distro, Docker, PHP, PostgreSQL, etc) versions: standard Docker on Debian Bullseye
2

Re: apache config, I have this which definitely works:

  # TT-RSS Reverse Proxy to docker nginx
  <IfModule mod_proxy.c>
    <Location /tt-rss>
      ProxyPreserveHost On
      ProxyPass        http://localhost:8280/tt-rss
      ProxyPassReverse http://localhost:8280/tt-rss
      RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}
    </Location>
  </IfModule>

Edit: I originally had this inside the IfModule mod_proxy.c above, but it’s absolutely un-necessary for tt-rss:

    <IfModule mod_ssl.c>
      SSLProxyEngine On
      SSLProxyVerify none
    </IfModule>
1 Like
3

it’s been years since i’ve last used apache so just tell me what to put in the wiki, and i’ll update it.

i can use the snippet from the post above.

@Athanasius why would you need SSLProxyVerify none when you’re proxying to plain http? am i misreading what this means?

4

@fox That would have been me cargo-culting from one of my other reverse proxy forwards, where the remote end is also doing HTTPS.

Indeed that whole IfModule mod_ssl.c section can be removed (I just tested to be sure).

5

updated here - https://gitlab.tt-rss.org/tt-rss/ttrss-docker-compose/-/wikis/Home#apache

git.tt-rss.org is going to pull this sometime later.

6

awesome, thanks!!
Consider changing docker-compose to docker compose, too :wink:
And I’m looking for a donate button…
Keep up your excellent work

7

i’m using it but i’m not sure how widespread it is. majority of people might still be using legacy docker-compose. anyway this should be obvious enough to figure out.

you won’t find it. because of the, you know, thing.