-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test Deploy fails with Error 500 or Error 504 #419
Comments
Sorry for this, maybe it is caused by actions from our side(we are moving all Ecosystem stuff) to the Nextcloud organization. Can you try again please? |
I have tried this many times over the last few weeks with the same result. I have tried again, still Error 504. |
Can you say which error you get when executing |
pulling the image on the host works as expected:
|
It looks like for some reason the deployment is just really slow. I increased the timeouts in HA proxy from 10s to 60s and now it works.
I'll look into the performance of my setup, but since nextcloud is working OK, maybe the timeouts are just too tight? I'd suggest increasing them, or maybe make them configurable. |
will I have already created a PR to raise the default value from 10s to 30s, - I wonder if 30s is enough or do we still need 60s? (I really wouldn't want to set such a high timeout for the connection process) |
30s seems to work ok. |
Describe the bug
I have a fresh install of NC30i (all-in-one) with some minimal configuration (oidc login).
When I try to test the AppAPI deployment, it always fails, either with the error "500 Internal Server Error" or "504 Gateway Time-out"
Steps/Code to Reproduce
Expected Results
Successful deployment.
Actual Results
nextcloud.log:
journalctl -feu docker.service:
Setup configuration
compose.yaml:
/etc/docker/daemon.json
The text was updated successfully, but these errors were encountered: