-
Notifications
You must be signed in to change notification settings - Fork 724
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
Containers fail on starting - Nextcloud AIO v1.7.0 #1000
Comments
I have also been dealing with this issue. |
I dunno know if this helps but I tried to do the manual install and had to change the postgres sql user in the lastest.yml file from nextcloud to oc_nextcloud and everything started working |
This should be fixed with 1.7.1 Beta by #1018. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
Thanks Simon,
Any ETA on beta timing and release of 1.7.1?
(Wont hold you to it : )
…On Wed, 17 Aug 2022, 9:58 pm Simon L., ***@***.***> wrote:
This should be fixed with 1.7.1 Beta. Testing and feedback is welcome! See
https://github.com/nextcloud/all-in-one#how-to-switch-the-channel
—
Reply to this email directly, view it on GitHub
<#1000 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2NEJPMLCQ4WT4V5F4Q3EQ3VZTHWXANCNFSM552P475A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
See #1012. Planned is currently to release it on 24.08. |
Hi Simon, I tested now release 1.71 and error persists In container nextcloud-aio-nextcloud:
in container nextcloud-aio-database:
|
Facing the same issue as well |
Same issue for me. For testing I destroyed and recreated the master container (while leaving db and nextcloud intact) and issue persisted. |
Hi guys, so looks like changing timezone on AIO setup screen causes the issue (no idea why). To confirm, I have created 2 x new Nextcloud servers from scratch. On reaching the domain and optional addon setup screen the timezone is left blank. The Apache and Nextcloud containers are last to start but they reach "running" status within 1 min with no errors in the logs! Hope this helps : ) |
How to use GitHub
Steps to reproduce
Expected behavior
All containers start / run
Actual behavior
Apache - Tries starting / gets stuck
Error = Waiting for Nextcloud to start...
nc: getaddrinfo for host "nextcloud-aio-nextcloud" port 9000: Name or service not known
Database Running OK
Nextcloud - Tries starting / gets stuck
Error = Configuring Redis as session handler
Appdata is not present. Did you maybe change the datadir after aio was first started?
psql: error: connection to server at "nextcloud-aio-database" (172.18.0.3), port 5432 failed: FATAL: password authentication failed for user "oc_nextcloud"
Redis Running OK
Host OS
Linode server - Ubuntu 22.04 LTS
Nextcloud AIO version
AIO v1.7.0
Current channel
Latest
Other valuable info
The text was updated successfully, but these errors were encountered: