i’m sure most would agree that having to set this variable up is the single most annoying part of installing tt-rss. looking through the code, i managed to find one valid use-case where SELF_URL_PATH is actually needed and we can’t figure it out from server/request variables - digest template, which is prepared and sent on the backend.
therefore, i’m changing this to work as follows: SELF_URL_PATH config option becomes a fallback value for the CLI SAPI where HTTP request variables are not available, in any other case we’ll just go with whatever got auto-detected and hope for the best.
i’ll set the default to example.com/tt-rss or something like that so it would be obvious where to dig, but otherwise it’s not going to prevent application startup or anything of that nature.
passing correct Host header through the reverse proxy remains your responsibility.
unless you’re using email digest and simply can’t live without correct tt-rss links in the template (it’s in the footer somewhere, i think), you shouldn’t need it anymore.
you can remove it or keep it, it won’t break anything.
It is possible this broke ttrss-api-resize for the Android app? I’m no longer getting images (on either feed listing or article preview) unless I disable image resizing. I still have SELF_URL_PATH set.
Android app is 1.305-fdroid (539). tt-rss version is v23.10-c28955c8.
Edit: I do see GET requests logged in the web-nginx container. E.g. 2023/10/23 10:59:48 stdout 172.22.0.1 - - [23/Oct/2023:14:59:48 +0000] "GET /tt-rss/api/public.php?op=api_resize_media--api_resize&url=https%3A%2F%2Fassets.amuniversal.com%2F00c252a08484013be1bc005056a9545d&referrer=https%3A%2F%2Fwww.gocomics.com%2Fgarfield-classics%2F2023%2F10%2F23&width=1024&force_stamp=0 HTTP/1.1" 404 153 "-" "Dalvik/2.1.0 (Linux; U; Android 14; Pixel 7 Pro Build/UP1A.231005.007)"
Edit 2: Clarification, on the feed listing, there is just blank space, on the article preview, a broken image placeholder is shown. If I take the resized image URL call logged in the Android app, I get a 404 response.
I set up my nginx to proxy tt-rss. before I was just using localhost:8280 I can get to the login page but when I enter my credentials I get a 404 and this UEL is shown in the address bar:
could be my set up for reverse proxy but thought I’d share, in case. If I use the localhost:8280 it still works. Just using the server name (myserver.my-localnet.domain) that fails.
not proud of this hack but at least there’s a unit test for this method now