-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
[BUG] Security Check Does Not Complete #483
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Happening during initial setup - needs to be tested internally. |
Bug was happening on ubuntu 24.04 - potentially an issue with the distro/docker packages. |
I should add that I always get a 504 gateway time-out error on this machine during installation. After refreshing the page, I am at the login page. Whenever I get the 504 error, the following is also true:
And of course the error this issue is about occurs. I have tried to set timeouts to 3600 seconds prior to installation, via the config files in /config/, but to no avail. Nextcloud AIO works without a hitch on the same machine, so if the timeout interrupts the installation and it doesn't quite finish, then it would probably be something specific to LSIO's container - just an idea. I haven't seen this issue with other deployment methods so far. Edit: After setting the log level to debug, I found this by searching for "timeout" in the ~3000 lines of logs:
Edit2: It was indeed a timeout issue. I followed this reddit post, editing
Of course the timeout is a little on the high side, so I may go a fair bit lower, but all three things got fixed by this:
Might I suggest that the default values for the container be increased a little bit? Or that some form of hint is dropped when the timeout hits during installation? FAQ entry maybe? Just anything really, so that people don't stumble around in darkness like me. Thanks again for the help troubleshooting :) |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Current Behavior
The Security & setup warnings self check under administration settings -> overview always throw this error:
Error occurred while checking server setup.
There are no related log entries about this, nextcloud.log only contains notices about
as well as 2x from right after the installation, but never again:
Expected Behavior
The check should complete.
Steps To Reproduce
Start up the container, go through installation. After login, go to administration settings and be presented the error.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: