Replies: 1 comment 1 reply
-
Thanks for reaching out, @Extarys! Can you share the output of |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I tried setting Nextcloud with an external Nginx server and had a ton of 502 errors, thinking NPM and Nginx had trouble connecting to each other, and the logs weren't either present or useful.
One reddit user suggest I try the linuxserver docker image for nextcloud, which ships with nginx already preconfigured inside the Docekrfile.
When I set Nextcloud and enter the database address in the installer, it failed with Internal Server Error:
After a couple of refresh, it worked, but every 10 seconds I would get antoher 502 and when it works, some css files couldn't be loaded with the same error as above. Disabling cache makes the issue worse and most of the time the main page stops loading.
frontend/compose.yaml:
backend/compose.yaml:
I had a similar issue when using NPM, Nginx and the Nextcloud:fpm image, but I would receive the generic 502 error from NPM directly so I thought it was a NPM <> Nginx issue, and no logs were present.
If I
podman exec -it nextcloud bash
and do pings topostgres
, I had 50 pings with 0% packet loss, but that make sense as the IP doesn't need to be resolved at every ping.I'm suspecting sometimes when the container asks podman for the IP of
postgres
, it doesn't reply in time, or somehow throttle the number of requests, as some DNS servers sometime do... but I'm not familiar enough with how podman works under the hood so this is a wild guess.OS info:
Beta Was this translation helpful? Give feedback.
All reactions