charts
charts copied to clipboard
truecharts
[Nextcloud] fails to start if there are issues connecting to Nextcloud
App Name
Nextcloud
SCALE Version
22.02.1
App Version
5.x.x
Application Events
https://discord.com/channels/830763548678291466/996734458289983528
Application Logs
https://discord.com/channels/830763548678291466/996734458289983528
Application Configuration
https://discord.com/channels/830763548678291466/996734458289983528
Describe the bug
When there are connection issues, Nextcloud fails to start, because it cannot fetch Notify_Push from the Nextcloud versions.
To Reproduce
- Have connection issues
- Start Nextcloud
Expected Behavior
Nextcloud Starting correctly
Screenshots
Not needed
Additional Context
The solution is to include said Apps in the image and trying to update them in a non-failing way at start. After which we enable them. This should guarantee the App can be ran, regardless of connection quality
I've read and agree with the following
- [X] I've checked all open and closed issues and my issue is not there.
Have the same issue, any solution already how to fix?
The main maintainer open the bug report, less than 24h ago. If there was a fix, it would have been fixed.
Workaround is have a good connection between your server and nextcloud download servers. Either on your end or NC end.
Maybe you guys already discussed some workarounds on Discord. Thats why I asked. The problem occurs already after installing nextcloud with default settings. The installation of Nextcloud from truescale itself works fine. But maybe it's another issue, the logs shows the next error: High Performance Backend service not accessable ... waiting..
Maybe you guys already discussed some workarounds on Discord. Thats why I asked. The problem occurs already after installing nextcloud with default settings. The installation of Nextcloud from truescale itself works fine. But maybe it's another issue, the logs shows the next error: High Performance Backend service not accessable ... waiting..
I serieusly doubt this is even the same bug, as the error you're sharing is not direclt related to this error at all. I'm also going to give you a Github timeout, because we have a "do some damn basic research before asking" policy. Which means we expect people to click the damn link above.
To be clear: This issue is NOT caused by our code, and is NOT a priority to be fixed. Please ensure your internet setting are fixed and/or internal Nextcloud timeouts get increased as discussed.
I've also double checked: This behavior is the same for the official AIO docker-images as well.
However: this did bring me to the idea to move more parts into the fpm container and out of the HPB container.
I'm going to not implement this, as it's not technically an issue on our side at all and we are currently not planning to put considerable development effort into reworking nextcloud yet-again.
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists
