After Update - Dead 'File Not Found' (docker)

Gas Chamber
1

Describe the problem you’re having:

After updating to the latest docker release (the previous image was working fine), TT-RSS broke. Viewing my site whether directly (see below) or using my SITE_URL yields “File not found”
image

If possible include steps to reproduce the problem:

I’m not sure, I just updated my working containers and everything died.

tt-rss version (including git commit id):

Using current:
cthulhoo/ttrss-fpm-pgsql-static
cthulhoo/ttrss-web:latest
postgres:12-alpine

cthulhoo/ttrss-web:latest image
sha256:4b55eeaa166b465ccfd74a73eface11dc15a13b049715000449ab8a02729d5ebv
cthulhoo/ttrss-fpm-pgsql-static:latest image sha256:a1d9fa5c762d7d5a84168094c93e1ce570d1145f05a219ee69690b84ad3220a9
postgres:12-alpine image sha256:10608227870cc7046f8f62c8ebd8bf3224e2b3057a8287ab1e17a81ef0ecf45a

Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:

Docker version 19.03.13
docker-compose version 1.27.4, build 40524192

On Ubuntu 18.04

Please provide any additional information below:

In my ttrss_web_1 container (exposes port 2015) I see the following logged when hitting the site:
See here: https://i.imgur.com/Es29Mmc.png - (this stupid site won’t let me embed a second image).

Looking at the ttrss_app_1 container, it seems to have some extra work, maybe upgrading something?

See here; https://i.imgur.com/sLWHED5.png - (this stupid site won’t let me embed a second image).

I have checked that containers can communicate with each other, that port 9000 is listening on tt_rss_app_1 and that the updater container is actually running through site updates.

I’m just not sure what broke this (or why it was so flaky)… I’ve been running this through many updates and more than 6 months without problems.

2

More info. I went into the ttrss_web_1 container and open the /etc/Caddyfile - here’s what’s in that file:

0.0.0.0
root /var/www/html
log stdout
errors stderr
internal /tt-rss/cache
internal /tt-rss/backups
fastcgi / app:9000 php

Also, looking at the the /var/www/html directory from inside the ttrss_web_1 container:

/srv # ls /var/www/html -al
total 24
drwxr-sr-x    5 1000     1000          4096 Oct 28 17:27 .
drwxr-xr-x    3 root     root          4096 Jan  5 00:16 ..
drwxr-sr-x    2 1000     1000          4096 Oct 28 17:23 app
-rwxrwxrwx    1 1000     1000            51 Oct 28 17:27 index.php
drwxr-xr-x   24 1000     1000          4096 Jan  5 01:05 tt-rss
drwxr-sr-x    2 1000     1000          4096 Oct 28 17:22 web
3

So, a little more - edit /etc/Caddyfile on the ttrss_web_1 container and remove the root /var/www/html line and the Caddy server loaded the /srv/index.html file with a standard page. So, at least something there is working. I’m starting to think maybe php-fpm was updated to 7 and the caddy container isn’t cable of talking to that?
image

4

try switching to web-nginx container as discussed in the main docker thread.

stop everything, comment out web, uncomment web-nginx, etc.

e: fwiw i’ve just tested on a latest dynamic image while testing an unrelated change and it works just fine with caddy, so it’s not like like web container got broken or is somehow suddenly incompatible with fpm.

5

That’s great… thanks. I’ll try that. In fact, i have an nginx container running - is there an example nginx .conf I could see so I might attempt to hook that in?

6

nginx configuration is included with the container. i don’t think you understand how these things work, maybe you should read the README.

7

I get it, you’re a salty mf, but don’t substitute your lack of understanding the question for shitting on me (as if we all have to know everything).

The file I was asking about is here: https://git.tt-rss.org/fox/ttrss-docker-compose/src/master/web-nginx/nginx.conf

I should have gone looking for it assuming it would be online somewhere.

8

enjoy 2 months probation for whatever this is supposed to be

10

Ban evasion is not acceptable and your second account has been deleted.