ignore the http:// prefix in the host name... that isn't actually there, but the Markdown "I'm going to guess this is a link" got involved when I posted it.
I can reproduce this... in so far as, when I use the app I get 404s and I see them in the logs.
I've put a fix into the nginx caching to ensure the $host was in the cache key, as this avoids 404s generated by the app poisoning the cache for others.
@cyclotron3k I think I have it... you're using the wrong URL.
http://www.lfgss.com GET /api/v1/files/677fd6380f7e4b1f9428035dfa7e3dbcb227cfbd.png HTTP/1.1
ignore the
http://
prefix in the host name... that isn't actually there, but the Markdown "I'm going to guess this is a link" got involved when I posted it.it shouldn't be https://www.lfgss.com/api/v1/files/677fd6380f7e4b1f9428035dfa7e3dbcb227cfbd.png
it should be https://lfgss.microcosm.app/api/v1/files/677fd6380f7e4b1f9428035dfa7e3dbcb227cfbd.png
I can reproduce this... in so far as, when I use the app I get 404s and I see them in the logs.
I've put a fix into the nginx caching to ensure the
$host
was in the cache key, as this avoids 404s generated by the app poisoning the cache for others.In the
server
blockthe
$request_method $scheme://$host
are all new to that.ignore the
proxy_pass http://microcosm;
there, as in nginx that's just talking about a backend proxy not a request URL.