[Support] Linuxserver.io - Nextcloud - Page 277 - Docker Containers

February 18, 20251 yr

Whilst I think about it, are you able to run occ commands? I'm guessing not, but try this:

change 'nextcloud' to whatever your nextcloud docker is called.

Quote

/mnt/user/Nextcloud# docker exec -it nextcloud occ check
/mnt/user/Nextcloud# docker exec -it nextcloud occ setupchecks

I missed this post from you, I was answering off my phone.

Quote

Well, I have a login screen back BUT still can't get past that - just reloads login page on credential submission.

If you can get to the login screen and no further. Normally, clearing cookies resolves it as a first step.

Run the commands above as well. There are other occ commands, you should always run maintenance data fingerprint after an upgrade.

I've really gotta go, let us know how you get on.

Edited February 18, 20251 yr by Geck0

Quote

February 19, 20251 yr

7 hours ago, Geck0 said:

Whilst I think about it, are you able to run occ commands? I'm guessing not, but try this:

change 'nextcloud' to whatever your nextcloud docker is called.

I missed this post from you, I was answering off my phone.

If you can get to the login screen and no further. Normally, clearing cookies resolves it as a first step.

Run the commands above as well. There are other occ commands, you should always run maintenance data fingerprint after an upgrade.

I've really gotta go, let us know how you get on.

root@Tower:~# docker exec -it mcdnc occ check
root@Tower:~# docker exec -it mcdnc occ setupchecks
        dav:
                ✓ DAV system address book: No outstanding DAV system address book sync.
        network:
                ✓ WebDAV endpoint: Your web server is properly set up to allow file synchronization over WebDAV.
                ✓ Data directory protected
                ✓ Internet connectivity
                ✓ JavaScript source map support
                ✓ JavaScript modules support
                ✓ OCS provider resolving
                ✓ .well-known URLs: Your server is correctly configured to serve `.well-known` URLs.
                ✓ Font file loading
        system:
                ⚠ Errors in the log: 4482 errors in the logs since February 12, 2025, 4:55:30 AM
                ✓ Allowed admin IP ranges: Admin IP filtering isn’t applied.
                ℹ Brute-force Throttle: Your remote address could not be determined.
                ✓ Cron errors: The last cron job ran without errors.
                ✓ Cron last run: Last background job execution ran seconds ago.
                ✓ Debug mode: Debug mode is disabled.
                ✓ File locking
                ✓ Maintenance window start: Maintenance window to execute heavy background jobs is between 19:00 UTC and 1:00 UTC
                ✓ Memcache: Configured
                ✓ Mimetype migrations available: None
                ✓ Architecture: 64-bit
                ✓ Temporary space available: Temporary directory is correctly configured:
- 589.2 GiB available in /tmp (PHP temporary directory)
                ✓ Push service: Free push service
        notifications:
                ✓ Push notifications - Fair use policy
        security:
                ✓ App directories owner: App directories have the correct owner "abc"
                ✓ Old administration imported certificates
                ✓ Code integrity: No altered files
                ℹ Forwarded for headers: Your remote address could not be determined.
                ✓ HTTPS access and URLs: You are accessing your instance over a secure connection, and your instance is generating secure URLs.
                ✓ Old server-side-encryption: Disabled
                ✓ PHP version: You are currently running PHP 8.3.17.
                ✓ Random generator: Secure
                ✓ HTTP headers: Your server is correctly configured to send security headers.
        database:
                ✓ Database missing columns: None
                ✓ Database missing indices: None
                ✓ Database missing primary keys: None
                ✓ Database pending bigint migrations: None
                ✓ MySQL Unicode support: You are not using MySQL
                ✓ Scheduling objects table size: Scheduling objects table size is within acceptable range.
                ✓ Database version: 14.16 (Debian 14.16-1.pgdg120+1)
                ✓ Database transaction isolation level: Read committed
        config:
                ✓ Default phone region: US
                ✓ Email test: Email test was successfully sent
                ✓ Overwrite CLI URL: The "overwrite.cli.url" option in your config.php is set to "https://xxx.xxx.net" which is a correct URL. Suggested URL is "https://localhost".
                ✓ Configuration file access rights: Nextcloud configuration file is writable
        php:
                ✓ PHP default charset: UTF-8
                ✓ PHP set_time_limit: The function is available.
                ✓ Freetype: Supported
                ✓ PHP getenv
                ✓ PHP memory limit: ?
                ✓ PHP modules
                ✓ PHP opcache: Checking from CLI, OPcache checks have been skipped.
                ✓ PHP "output_buffering" option: Disabled
                ✓ PHP Imagick module

occ check did nothing? See above.

Quote

February 19, 20251 yr

35 minutes ago, blaine07 said:

root@Tower:~# docker exec -it mcdnc occ check
root@Tower:~# docker exec -it mcdnc occ setupchecks
        dav:
                ✓ DAV system address book: No outstanding DAV system address book sync.
        network:
                ✓ WebDAV endpoint: Your web server is properly set up to allow file synchronization over WebDAV.
                ✓ Data directory protected
                ✓ Internet connectivity
                ✓ JavaScript source map support
                ✓ JavaScript modules support
                ✓ OCS provider resolving
                ✓ .well-known URLs: Your server is correctly configured to serve `.well-known` URLs.
                ✓ Font file loading
        system:
                ⚠ Errors in the log: 4482 errors in the logs since February 12, 2025, 4:55:30 AM
                ✓ Allowed admin IP ranges: Admin IP filtering isn’t applied.
                ℹ Brute-force Throttle: Your remote address could not be determined.
                ✓ Cron errors: The last cron job ran without errors.
                ✓ Cron last run: Last background job execution ran seconds ago.
                ✓ Debug mode: Debug mode is disabled.
                ✓ File locking
                ✓ Maintenance window start: Maintenance window to execute heavy background jobs is between 19:00 UTC and 1:00 UTC
                ✓ Memcache: Configured
                ✓ Mimetype migrations available: None
                ✓ Architecture: 64-bit
                ✓ Temporary space available: Temporary directory is correctly configured:
- 589.2 GiB available in /tmp (PHP temporary directory)
                ✓ Push service: Free push service
        notifications:
                ✓ Push notifications - Fair use policy
        security:
                ✓ App directories owner: App directories have the correct owner "abc"
                ✓ Old administration imported certificates
                ✓ Code integrity: No altered files
                ℹ Forwarded for headers: Your remote address could not be determined.
                ✓ HTTPS access and URLs: You are accessing your instance over a secure connection, and your instance is generating secure URLs.
                ✓ Old server-side-encryption: Disabled
                ✓ PHP version: You are currently running PHP 8.3.17.
                ✓ Random generator: Secure
                ✓ HTTP headers: Your server is correctly configured to send security headers.
        database:
                ✓ Database missing columns: None
                ✓ Database missing indices: None
                ✓ Database missing primary keys: None
                ✓ Database pending bigint migrations: None
                ✓ MySQL Unicode support: You are not using MySQL
                ✓ Scheduling objects table size: Scheduling objects table size is within acceptable range.
                ✓ Database version: 14.16 (Debian 14.16-1.pgdg120+1)
                ✓ Database transaction isolation level: Read committed
        config:
                ✓ Default phone region: US
                ✓ Email test: Email test was successfully sent
                ✓ Overwrite CLI URL: The "overwrite.cli.url" option in your config.php is set to "https://xxx.xxx.net" which is a correct URL. Suggested URL is "https://localhost".
                ✓ Configuration file access rights: Nextcloud configuration file is writable
        php:
                ✓ PHP default charset: UTF-8
                ✓ PHP set_time_limit: The function is available.
                ✓ Freetype: Supported
                ✓ PHP getenv
                ✓ PHP memory limit: ?
                ✓ PHP modules
                ✓ PHP opcache: Checking from CLI, OPcache checks have been skipped.
                ✓ PHP "output_buffering" option: Disabled
                ✓ PHP Imagick module

occ check did nothing? See above.

Then pass. There is something obvious that you're missing. Your installation seems to check out. 4482 errors in the log since 12th Feb is a Hell'uva lot?! What's in your logs under your data directory? ie. nextcloud.log. There must be an indicator in there of some sort. The log is definately complaining about something.

The only other thing I can think of, which is normally a last resort, is to try "occ maintenance:repair"

Its possible you're upgrade didn't complete and you're missing a few files. If OCC is running then generally the upgrade is missing files for the GUI. Have you dropped the docker and reinstalled it again?

The issue with Redis also refers back to COOLWSD, which is Collabora. Maybe Redis is fine and Collabora is causing the issue. To me, it states simply that there is no connection to Redis, but its in the context of Collabora anyway.

Edited February 19, 20251 yr by Geck0

Quote

February 20, 20251 yr

18 hours ago, Geck0 said:

Then pass. There is something obvious that you're missing. Your installation seems to check out. 4482 errors in the log since 12th Feb is a Hell'uva lot?! What's in your logs under your data directory? ie. nextcloud.log. There must be an indicator in there of some sort. The log is definately complaining about something.

The only other thing I can think of, which is normally a last resort, is to try "occ maintenance:repair"

Its possible you're upgrade didn't complete and you're missing a few files. If OCC is running then generally the upgrade is missing files for the GUI. Have you dropped the docker and reinstalled it again?

The issue with Redis also refers back to COOLWSD, which is Collabora. Maybe Redis is fine and Collabora is causing the issue. To me, it states simply that there is no connection to Redis, but its in the context of Collabora anyway.

{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=Waffles2021&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=Waffles2021&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=XXXXXXXX&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=XXXXXX&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}

At a skim it appears ENTIRE thing is this over and over to tune of 4.95 MB.

I am sure you're 100% right; something stupid on my part; just no idea what that is. No idea why it's still "trying to connect to redis" when we removed that from config.php though.

I'll try OCC maintenance repair; nothing to lose at this point as far as I can tell; its broke LOL.

Maintenance Repair:

root@Tower:~# docker exec -it mcdnc occ maintenance:mode --on
Maintenance mode enabled
root@Tower:~# docker exec -it mcdnc occ maintenance:repair
Nextcloud is in maintenance mode, no apps are loaded.
Commands provided by apps are unavailable.
 - Repair MySQL collation
     - Not a mysql database -> nothing to do
 - Clean tags and favorites
     - 0 tags of deleted users have been removed.
     - 0 tags for delete files have been removed.
     - 0 tag entries for deleted tags have been removed.
     - 0 tags with no entries have been removed.
 - Repair invalid shares
 - Move .step file of updater to backup location
 - Add move avatar background job
     - Repair step already executed
 - Add preview cleanup background jobs
 - Migrate oauth2_clients table to nextcloud schema
     - Update the oauth2_access_tokens table schema.
     - Update the oauth2_clients table schema.
     - Delete clients (and their related access tokens) with the redirect_uri starting with oc:// or ending with *
 - Repair language codes
 - Add log rotate job
 - Clear frontend caches
     - Image cache cleared
     - JS cache cleared
 - Clear every generated avatar
 - Add preview background cleanup job
 - Queue a one-time job to cleanup old backups of the updater
 - Cleanup invalid photocache files for carddav
 - Add background job to cleanup login flow v2 tokens
 - Remove potentially over exposing share links
     - No need to remove link shares.
 - Clear access cache of projects
 - Reset generated avatar flag
 - Keep legacy encryption enabled
 - Check encryption key format
 - Remove old dashboard app config data
 - Add job to cleanup the bruteforce entries
 - Queue a one-time job to check for user uploaded certificates
 - Repair DAV shares
 - Add background job to set the lookup server share state for users
 - Add token cleanup job
 - Clean up abandoned apps
 - Add possibly missing system config
 - Add AI tasks cleanup jobs
 - Queue a job to generate metadata
 - migrate lazy config values
 - Cache logo dimension to fix size in emails on Outlook
     - Theming is not used to provide a logo
 - Remove legacy ".ocdata" file
 - Add cleanup-deleted-users background job
 - AppAPI Daemons configuration GPU params update
     - Daemons configuration GPU params updated: 0
 - Upgrading Circles App
 - Fix component of birthday calendars
     - 2 birthday calendars updated.
 - Regenerating birthday calendars to use new icons and fix old birthday events without year
     - Repair step already executed
 - Fix broken values of calendar objects
    0 [->--------------------------]
 - Registering building of calendar search index as background job
     - Repair step already executed
 - Register building of social profile search index as background job
 - Registering background jobs to update cache for webcal calendars
     - Added 0 background jobs to update webcal calendars
 - Registering building of calendar reminder index as background job
     - Repair step already executed
 - Clean up orphan event and contact data
     - 0 events without a calendar have been cleaned up
     - 0 properties without an events have been cleaned up
     - 0 changes without a calendar have been cleaned up
     - 0 cached events without a calendar subscription have been cleaned up
     - 0 changes without a calendar subscription have been cleaned up
     - 0 contacts without an addressbook have been cleaned up
     - 0 properties without a contact have been cleaned up
     - 0 changes without an addressbook have been cleaned up
 - Remove activity entries of private events
     - Removed 0 activity entries
 - Clean up old calendar subscriptions from deleted users that were not cleaned-up
    0 [----->----------------------]
     - 0 calendar subscriptions without an user have been cleaned up
 - Remove invalid object properties
     - 0 invalid object properties removed.
 - Fix the share type of guest shares when migrating from ownCloud
 - Copy the share password into the dedicated column
 - Set existing shares as accepted
 - Clean up meta table
 - Show a hint about the new editor to existing users
 - Update OAuth token expiration times
 - init metadata
 - Switches from default updater server to the customer one if a valid subscription is available
     - Repair step already executed
 - Force-reset all Text document sessions
 - Initialize migration of background images from dashboard to theming app
 - Add background job to check for backup codes
 - Populating added database structures for workflows
root@Tower:~# docker exec -it mcdnc occ maintenance:mode --off
Maintenance mode disabled

No idea what else to do. :shrug:

EDIT: Each FAILED login generates 30 LINES in the nextcloud.log file by the way. Just the above I shared over and over and over.

EDIT 2: changed log level to "0" and when I go to login:

{"reqId":"SQA6CjaJgk0aifoFlfeG","level":0,"time":"2025-02-20T00:21:49+00:00","remoteAddr":"192.168.1.5","user":"--","app":"no app in context","method":"GET","url":"/login?direct=1&user=Xxxxxx","message":"The loading of lazy AppConfig values have been requested","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36","version":"30.0.6.2","exception":{"Exception":"RuntimeException","Message":"ignorable exception","Code":0,"Trace":[{"file":"/app/www/public/lib/private/AppConfig.php","line":1180,"function":"loadConfig","class":"OC\\AppConfig","type":"->"},{"file":"/app/www/public/lib/private/AppConfig.php","line":100,"function":"loadConfigAll","class":"OC\\AppConfig","type":"->"},{"file":"/app/www/public/lib/private/AllConfig.php","line":169,"function":"getKeys","class":"OC\\AppConfig","type":"->"},{"file":"/app/www/public/lib/private/Security/Bruteforce/Throttler.php","line":95,"function":"getAppKeys","class":"OC\\AllConfig","type":"->"},{"file":"/app/www/public/lib/private/Security/Bruteforce/Throttler.php","line":175,"function":"isBypassListed","class":"OC\\Security\\Bruteforce\\Throttler","type":"->"},{"file":"/app/www/public/lib/private/Security/Bruteforce/Throttler.php","line":192,"function":"getAttempts","class":"OC\\Security\\Bruteforce\\Throttler","type":"->"},{"file":"/app/www/public/core/Controller/LoginController.php","line":151,"function":"getDelay","class":"OC\\Security\\Bruteforce\\Throttler","type":"->"},{"file":"/app/www/public/lib/private/AppFramework/Http/Dispatcher.php","line":208,"function":"showLoginForm","class":"OC\\Core\\Controller\\LoginController","type":"->"},{"file":"/app/www/public/lib/private/AppFramework/Http/Dispatcher.php","line":114,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/www/public/lib/private/AppFramework/App.php","line":161,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/www/public/lib/private/Route/Router.php","line":302,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/app/www/public/lib/base.php","line":1003,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/app/www/public/index.php","line":24,"function":"handleRequest","class":"OC","type":"::"}],"File":"/app/www/public/lib/private/AppConfig.php","Line":1194,"message":"The loading of lazy AppConfig values have been requested","exception":{},"CustomMessage":"The loading of lazy AppConfig values have been requested"}}

Edited February 20, 20251 yr by blaine07

Quote

February 20, 20251 yr

4 hours ago, blaine07 said:

{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=Waffles2021&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"hfhVeMUcEufWb4p8BKMJ","level":3,"time":"2025-02-19T23:55:22+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=Waffles2021&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=XXXXXXXX&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Redis connection not available at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}
{"reqId":"REE2DUgWaE87NoNSkoDK","level":3,"time":"2025-02-19T23:56:23+00:00","remoteAddr":"192.168.1.5","user":"--","app":"PHP","method":"GET","url":"/apps/richdocuments/settings/fonts.json","message":"session_start(): Failed to read session data: redis (path: tcp://192.168.1.5:6384?auth=XXXXXX&amp;) at /app/www/public/lib/private/Session/Internal.php#198","userAgent":"COOLWSD HTTP Agent 24.04.12.3","version":"30.0.6.2","data":{"app":"PHP"}}

At a skim it appears ENTIRE thing is this over and over to tune of 4.95 MB.

I am sure you're 100% right; something stupid on my part; just no idea what that is. No idea why it's still "trying to connect to redis" when we removed that from config.php though.

I'll try OCC maintenance repair; nothing to lose at this point as far as I can tell; its broke LOL.

Maintenance Repair:

root@Tower:~# docker exec -it mcdnc occ maintenance:mode --on
Maintenance mode enabled
root@Tower:~# docker exec -it mcdnc occ maintenance:repair
Nextcloud is in maintenance mode, no apps are loaded.
Commands provided by apps are unavailable.
 - Repair MySQL collation
     - Not a mysql database -> nothing to do
 - Clean tags and favorites
     - 0 tags of deleted users have been removed.
     - 0 tags for delete files have been removed.
     - 0 tag entries for deleted tags have been removed.
     - 0 tags with no entries have been removed.
 - Repair invalid shares
 - Move .step file of updater to backup location
 - Add move avatar background job
     - Repair step already executed
 - Add preview cleanup background jobs
 - Migrate oauth2_clients table to nextcloud schema
     - Update the oauth2_access_tokens table schema.
     - Update the oauth2_clients table schema.
     - Delete clients (and their related access tokens) with the redirect_uri starting with oc:// or ending with *
 - Repair language codes
 - Add log rotate job
 - Clear frontend caches
     - Image cache cleared
     - JS cache cleared
 - Clear every generated avatar
 - Add preview background cleanup job
 - Queue a one-time job to cleanup old backups of the updater
 - Cleanup invalid photocache files for carddav
 - Add background job to cleanup login flow v2 tokens
 - Remove potentially over exposing share links
     - No need to remove link shares.
 - Clear access cache of projects
 - Reset generated avatar flag
 - Keep legacy encryption enabled
 - Check encryption key format
 - Remove old dashboard app config data
 - Add job to cleanup the bruteforce entries
 - Queue a one-time job to check for user uploaded certificates
 - Repair DAV shares
 - Add background job to set the lookup server share state for users
 - Add token cleanup job
 - Clean up abandoned apps
 - Add possibly missing system config
 - Add AI tasks cleanup jobs
 - Queue a job to generate metadata
 - migrate lazy config values
 - Cache logo dimension to fix size in emails on Outlook
     - Theming is not used to provide a logo
 - Remove legacy ".ocdata" file
 - Add cleanup-deleted-users background job
 - AppAPI Daemons configuration GPU params update
     - Daemons configuration GPU params updated: 0
 - Upgrading Circles App
 - Fix component of birthday calendars
     - 2 birthday calendars updated.
 - Regenerating birthday calendars to use new icons and fix old birthday events without year
     - Repair step already executed
 - Fix broken values of calendar objects
    0 [->--------------------------]
 - Registering building of calendar search index as background job
     - Repair step already executed
 - Register building of social profile search index as background job
 - Registering background jobs to update cache for webcal calendars
     - Added 0 background jobs to update webcal calendars
 - Registering building of calendar reminder index as background job
     - Repair step already executed
 - Clean up orphan event and contact data
     - 0 events without a calendar have been cleaned up
     - 0 properties without an events have been cleaned up
     - 0 changes without a calendar have been cleaned up
     - 0 cached events without a calendar subscription have been cleaned up
     - 0 changes without a calendar subscription have been cleaned up
     - 0 contacts without an addressbook have been cleaned up
     - 0 properties without a contact have been cleaned up
     - 0 changes without an addressbook have been cleaned up
 - Remove activity entries of private events
     - Removed 0 activity entries
 - Clean up old calendar subscriptions from deleted users that were not cleaned-up
    0 [----->----------------------]
     - 0 calendar subscriptions without an user have been cleaned up
 - Remove invalid object properties
     - 0 invalid object properties removed.
 - Fix the share type of guest shares when migrating from ownCloud
 - Copy the share password into the dedicated column
 - Set existing shares as accepted
 - Clean up meta table
 - Show a hint about the new editor to existing users
 - Update OAuth token expiration times
 - init metadata
 - Switches from default updater server to the customer one if a valid subscription is available
     - Repair step already executed
 - Force-reset all Text document sessions
 - Initialize migration of background images from dashboard to theming app
 - Add background job to check for backup codes
 - Populating added database structures for workflows
root@Tower:~# docker exec -it mcdnc occ maintenance:mode --off
Maintenance mode disabled

No idea what else to do. :shrug:

EDIT: Each FAILED login generates 30 LINES in the nextcloud.log file by the way. Just the above I shared over and over and over.

EDIT 2: changed log level to "0" and when I go to login:

{"reqId":"SQA6CjaJgk0aifoFlfeG","level":0,"time":"2025-02-20T00:21:49+00:00","remoteAddr":"192.168.1.5","user":"--","app":"no app in context","method":"GET","url":"/login?direct=1&user=Xxxxxx","message":"The loading of lazy AppConfig values have been requested","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36","version":"30.0.6.2","exception":{"Exception":"RuntimeException","Message":"ignorable exception","Code":0,"Trace":[{"file":"/app/www/public/lib/private/AppConfig.php","line":1180,"function":"loadConfig","class":"OC\\AppConfig","type":"->"},{"file":"/app/www/public/lib/private/AppConfig.php","line":100,"function":"loadConfigAll","class":"OC\\AppConfig","type":"->"},{"file":"/app/www/public/lib/private/AllConfig.php","line":169,"function":"getKeys","class":"OC\\AppConfig","type":"->"},{"file":"/app/www/public/lib/private/Security/Bruteforce/Throttler.php","line":95,"function":"getAppKeys","class":"OC\\AllConfig","type":"->"},{"file":"/app/www/public/lib/private/Security/Bruteforce/Throttler.php","line":175,"function":"isBypassListed","class":"OC\\Security\\Bruteforce\\Throttler","type":"->"},{"file":"/app/www/public/lib/private/Security/Bruteforce/Throttler.php","line":192,"function":"getAttempts","class":"OC\\Security\\Bruteforce\\Throttler","type":"->"},{"file":"/app/www/public/core/Controller/LoginController.php","line":151,"function":"getDelay","class":"OC\\Security\\Bruteforce\\Throttler","type":"->"},{"file":"/app/www/public/lib/private/AppFramework/Http/Dispatcher.php","line":208,"function":"showLoginForm","class":"OC\\Core\\Controller\\LoginController","type":"->"},{"file":"/app/www/public/lib/private/AppFramework/Http/Dispatcher.php","line":114,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/www/public/lib/private/AppFramework/App.php","line":161,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/app/www/public/lib/private/Route/Router.php","line":302,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/app/www/public/lib/base.php","line":1003,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/app/www/public/index.php","line":24,"function":"handleRequest","class":"OC","type":"::"}],"File":"/app/www/public/lib/private/AppConfig.php","Line":1194,"message":"The loading of lazy AppConfig values have been requested","exception":{},"CustomMessage":"The loading of lazy AppConfig values have been requested"}}

Is 192.168.1.5 your unRaid server?

That error message is Bruteforce throttling of 192.168.1.5.

I think I know what the issue is. Can you confirm if this is your server??

Although, I just had another quick look: Why do you have :444 and :443 on different ip addresses. Maybe elaborate on what these ip addresses are??

Quote

'trusted_domains' =>
array (
0 => '192.168.1.5:444',
1 => 'XXXX.XXXX.net',
2 => '192.168.1.3:443',

Edited February 20, 20251 yr by Geck0

Quote

February 20, 20251 yr

8 minutes ago, Geck0 said:

Is 192.168.1.5 your unRaid server?

That error message is Bruteforce throttling of 192.168.1.5.

I think I know what the issue is. Can you confirm if this is your server??

Although, I just had another quick look: Why do you have :444 and :443 on different ip addresses. Maybe elaborate on what these ip addresses are??

192.168.1.5 is Unraid, yes.
192.168.1.3 is a internal Nginx Proxy Manager instance.

Quote

February 20, 20251 yr

4 minutes ago, blaine07 said:

192.168.1.5 is Unraid, yes.
192.168.1.3 is a internal Nginx Proxy Manager instance.

Okay,

192.1681.5 is being bruteforce throttled by NC.

Try this first

Quote

docker exec -it nextcloud occ app:disable bruteforcesettings

You may not have to, but restart your NC docker anyway. Check your logs again when you login, so we can check what is going on, whether you can or not, post the logs.

If that works, try this in your config.php

Quote

'trusted_proxies' =>
array (
0 => '192.168.1.146',
1 => '192.168.1.3',
2 => '192.168.1.5',

),

I think you have an issue with your reverse proxy or your Nextcloud's nginx files. Most likely your reverse proxy. It's not recognising your ip address and thinks everything is coming from the unRaid server's ip address. Its blocking 192.168.1.5, which is also the address your Redis is on, I'm guessing.

If I'm right, we can sort out your nginx conf files later. If you can remember messing with your proxy recently, that maybe the goto first.

Quote

February 20, 20251 yr

4 minutes ago, Geck0 said:

Okay,

192.1681.5 is being bruteforce throttled by NC.

Try this first

You may not have to, but restart your NC docker anyway. Check your logs again when you login, so we can check what is going on, whether you can or not, post the logs.

If that works, try this in your config.php

I think you have an issue with your reverse proxy or your Nextcloud's nginx files. Most likely your reverse proxy. It's not recognising your ip address and thinks everything is coming from the unRaid server's ip address. Its blocking 192.168.1.5, which is also the address your Redis is on, I'm guessing.

If I'm right, we can sort out your nginx conf files later. If you can remember messing with your proxy recently, that maybe the goto first.

Disabled brute force; restarted container - no change.

I will have to try config changes in a few hours. Can’t do that on mobile.

Haven’t messed with anything to do with reverse proxy lately though; config has forever had the port numbers following IP though and never been issue.

When not on mobile I’ll have to change nextcloud logging back to “0” and see what log says now/ this time but at moment disabling brute force did no good.

Quote

February 22, 20251 yr

On 2/20/2025 at 3:51 PM, blaine07 said:

Disabled brute force; restarted container - no change.

I will have to try config changes in a few hours. Can’t do that on mobile.

Haven’t messed with anything to do with reverse proxy lately though; config has forever had the port numbers following IP though and never been issue.

When not on mobile I’ll have to change nextcloud logging back to “0” and see what log says now/ this time but at moment disabling brute force did no good.

How'd you go? Or did I lead you up the garden path??

Quote

February 23, 20251 yr

12 hours ago, Geck0 said:

How'd you go? Or did I lead you up the garden path??

Honestly haven't had time to circle back; I think all hope is lost to be honest. Not so sure something isn't wrong with the DB; at one point I saw some DB errors but wouldn't know how to begin with repairing DB. Oddly I can still access the instance using my iPhone I am logged into it with - whatever is broken still purely only affects GUI on a PC browser.

I truly appreciate your help; maybe tonight I can play with it some more - just been super busy but have almost given up hope LOL 😞

Quote

February 24, 20251 yr

On 2/23/2025 at 10:43 PM, blaine07 said:

Honestly haven't had time to circle back; I think all hope is lost to be honest. Not so sure something isn't wrong with the DB; at one point I saw some DB errors but wouldn't know how to begin with repairing DB. Oddly I can still access the instance using my iPhone I am logged into it with - whatever is broken still purely only affects GUI on a PC browser.

I truly appreciate your help; maybe tonight I can play with it some more - just been super busy but have almost given up hope LOL 😞

Something I thought of. Are you accessing Nextcloud using its public facing domain name, and locally via your PC?? I know you have an internal reverse proxy, do you have an external facing reverse proxy as well??

(edited above)

It depends how important the Nextcloud setup is to you, vs how much time you have, etc.

I haven't had to do it in a long time, but I can tell you that when things went wrong, rolling back to a previous backup or a Nextcloud rebuild became the easiest thing to do. I wouldn't want to do it now, as Nextcloud is fully integrated into the family.

However, if I was you, I would use this as an opportunity to move to MariaDB. I use a single MariaDB docker for multiple databases. Its easy to edit, etc. I'm biased, as I no virtually nothing about PSQL.

Good backups are important, a roll back will save you heaps of time. I've actually got another instance of NC running purely for testing an upgrade before I roll it out. That said, I often don't as I get lazy to do it twice.

To me, it sounds like the easiest and quickest thing to do is scrap it and start again. It will take you less than 2 hours. Your data directory is safe (you should have backups anyway) and you're literally only losing your database driven features, like your calender, etc. Even those, you can probably backup if its worth it.

Edited February 24, 20251 yr by Geck0

Quote

1

February 26, 20251 yr

On 2/24/2025 at 3:31 PM, Geck0 said:

Something I thought of. Are you accessing Nextcloud using its public facing domain name, and locally via your PC?? I know you have an internal reverse proxy, do you have an external facing reverse proxy as well??

(edited above)

It depends how important the Nextcloud setup is to you, vs how much time you have, etc.

I haven't had to do it in a long time, but I can tell you that when things went wrong, rolling back to a previous backup or a Nextcloud rebuild became the easiest thing to do. I wouldn't want to do it now, as Nextcloud is fully integrated into the family.

However, if I was you, I would use this as an opportunity to move to MariaDB. I use a single MariaDB docker for multiple databases. Its easy to edit, etc. I'm biased, as I no virtually nothing about PSQL.

Good backups are important, a roll back will save you heaps of time. I've actually got another instance of NC running purely for testing an upgrade before I roll it out. That said, I often don't as I get lazy to do it twice.

To me, it sounds like the easiest and quickest thing to do is scrap it and start again. It will take you less than 2 hours. Your data directory is safe (you should have backups anyway) and you're literally only losing your database driven features, like your calender, etc. Even those, you can probably backup if its worth it.

Internal I have a Nginx Proxy Manager. External I use CloudFlare Proxy.

The instance that is broken wasn't my primary instance - i'll just grab the data I need and start over on it at this point. I suspect the DB is corrupt. I guess, I was always under impression, that Postgresql was "FASTER" but it sure seems that MariaDB is much more stable/reliable. Do you recommend MariaDB? Is it better/simpler to have separate MariaDB(or Postgresql) containers for each "service" on my Unraid or better to have several DBs inside ONE instance of either of the others?

Also, debating upgrading MAIN instance, MariaDB instance, to Nextcloud 31 - how is the upgrade to 31 going for folks? Anything I should know there?

Quote

February 27, 20251 yr

Hello, for anyone having ROW_FORMAT db errors on nextcloud, here is the fix for you.

Nextcloud error

Incorrect row format found in your database. ROW_FORMAT=Dynamic offers the best database performances for Nextcloud. Please update row format on the following list: oc_accounts, oc_accounts_data, oc_activity, oc_activity_mq, oc_addressbookchanges, oc_addressbooks, oc_appconfig, oc_authorized_groups, oc_authtoken, oc_bruteforce_attempts, oc_calendar_appt_bookings, oc_calendar_appt_configs, oc_calendar_invitations, oc_calendar_reminders, 
.....

Open a terminal on your Unraid server and run:

docker exec -it mariadb mysql -u root -p

Enter your MariaDB root password when prompted.

Select the Nextcloud Database:

USE nextcloud;

(Replace nextcloud with your actual Nextcloud database name if different.)

Update the ROW_FORMAT for All Affected Tables:

Run the following command:

SET GLOBAL innodb_large_prefix = 1;
SET GLOBAL innodb_file_format = BARRACUDA;
SET GLOBAL innodb_file_per_table = 1;

Update All Affected Tables to ROW_FORMAT=DYNAMIC

Run this command to generate the required ALTER statements:

SELECT CONCAT('ALTER TABLE ', table_name, ' ROW_FORMAT=DYNAMIC;')
FROM information_schema.tables
WHERE table_schema = 'nextcloud';

(Replace nextcloud with your actual Nextcloud database name if different.)

This will generate ALTER TABLE statements.

Copy the output and execute each ALTER TABLE ... command manually.

(your list will vary)

ALTER TABLE oc_onlyoffice_filekey ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_preferences ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_privacy_admins ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_profile_config ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_properties ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_ratelimit_entries ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_recent_contact ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_assets ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_direct ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_template ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_wopi ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_rocket_file_chats ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_rocket_users ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_schedulingobjects ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_share ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_share_external ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_storages ROW_FORMAT=DYNAMIC;

Then restart Mariadb and Nextcloud

docker restart mariadb
docker restart nextcloud

-This is the way.

Quote

2

February 27, 20251 yr

I was able to solve it this way:

open a console of the mariadb container

the tyoe in

mysql -u root -p -D nextcloud -N -e "
SELECT CONCAT(
  'ALTER TABLE ', TABLE_SCHEMA, '.', TABLE_NAME, ' ',
  'ROW_FORMAT=DYNAMIC;'
) 
FROM INFORMATION_SCHEMA.TABLES
WHERE ENGINE='InnoDB' AND ROW_FORMAT <> 'DYNAMIC';" | mysql -u root -p nextcloud

maybe you need to replace "nextcloud" with your nextcloud database name.\

You will be asked for root password.

That's all.

Quote

2
1

February 27, 20251 yr

After the update to 31 i have another error: Some files have not passed the integrity check :

Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results
=======
- mail
	- EXCEPTION
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Certificate is not valid.

Raw output
==========
Array
(
    [mail] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Certificate is not valid.
                )

        )

)

Can you guys give me a hint, how to resolve this?

Edited February 27, 20251 yr by LuxVita
added version

Quote

February 27, 20251 yr

unsure if this is correct place to post this?.

So i just followed space invaders guide on installing the aio, done one backup as suggested and added the main user and now nextcloud is stuck in a boot loop. I am pretty basic when it comes to this so any advice would be helpful.

This is what the logs are saying, I basically don't know what this means or how to fix it lol

The www-data user doesn't seem to have access rights in the datadir. 2025-02-27T20:42:53.208353317Z Most likely are the files located on a drive that does not follow linux permissions. 2025-02-27T20:42:53.208356622Z Please adjust the permissions like mentioned below. 2025-02-27T20:42:53.208359006Z The found permissions are: 2025-02-27T20:42:53.208361219Z 33:0 750 2025-02-27T20:42:53.208363239Z (userID:groupID permissions) 2025-02-27T20:42:53.208365273Z but they should be: 2025-02-27T20:42:53.208367286Z 33:0 750 2025-02-27T20:42:53.208369230Z (userID:groupID permissions) The www-data user doesn't seem to have access rights in the datadir. 2025-02-27T20:42:53.208353317Z Most likely are the files located on a drive that does not follow linux permissions. 2025-02-27T20:42:53.208356622Z Please adjust the permissions like mentioned below. 2025-02-27T20:42:53.208359006Z The found permissions are: 2025-02-27T20:42:53.208361219Z 33:0 750 2025-02-27T20:42:53.208363239Z (userID:groupID permissions) 2025-02-27T20:42:53.208365273Z but they should be: 2025-02-27T20:42:53.208367286Z 33:0 750 2025-02-27T20:42:53.208369230Z (userID:groupID permissions)

Quote

February 27, 20251 yr

11 hours ago, LuxVita said:

After the update to 31 i have another error: Some files have not passed the integrity check :

Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results
=======
- mail
	- EXCEPTION
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Certificate is not valid.

Raw output
==========
Array
(
    [mail] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Certificate is not valid.
                )

        )

)

Can you guys give me a hint, how to resolve this?

did you click the rescan link?

Quote

1

February 28, 20251 yr

6 hours ago, wizkid941 said:

unsure if this is correct place to post this?.

So i just followed space invaders guide on installing the aio, done one backup as suggested and added the main user and now nextcloud is stuck in a boot loop. I am pretty basic when it comes to this so any advice would be helpful.

This is what the logs are saying, I basically don't know what this means or how to fix it lol

The www-data user doesn't seem to have access rights in the datadir. 2025-02-27T20:42:53.208353317Z Most likely are the files located on a drive that does not follow linux permissions. 2025-02-27T20:42:53.208356622Z Please adjust the permissions like mentioned below. 2025-02-27T20:42:53.208359006Z The found permissions are: 2025-02-27T20:42:53.208361219Z 33:0 750 2025-02-27T20:42:53.208363239Z (userID:groupID permissions) 2025-02-27T20:42:53.208365273Z but they should be: 2025-02-27T20:42:53.208367286Z 33:0 750 2025-02-27T20:42:53.208369230Z (userID:groupID permissions) The www-data user doesn't seem to have access rights in the datadir. 2025-02-27T20:42:53.208353317Z Most likely are the files located on a drive that does not follow linux permissions. 2025-02-27T20:42:53.208356622Z Please adjust the permissions like mentioned below. 2025-02-27T20:42:53.208359006Z The found permissions are: 2025-02-27T20:42:53.208361219Z 33:0 750 2025-02-27T20:42:53.208363239Z (userID:groupID permissions) 2025-02-27T20:42:53.208365273Z but they should be: 2025-02-27T20:42:53.208367286Z 33:0 750 2025-02-27T20:42:53.208369230Z (userID:groupID

This forum is specific to Linixserver.io's Nextcloud docker. Are you sure that's what you're using and not another Nextcloud docker?

With Linuxserver.io's docker instance, you shouldn't have to change permissions, etc. I don't use AIO, I have separate dockers for everything, so apologies in advance if I have this wrong.

Quote

1

March 1, 20251 yr

Don’t worry I’ve now solved the issue. Thanks!

Quote

March 1, 20251 yr

3 hours ago, wizkid941 said:

Don’t worry I’ve now solved the issue. Thanks!

No worries, It helps everybody if you explain what the issue is and the resolution.

Quote

March 11, 20251 yr

Hi all, I'm trying to troubleshoot an upgrade issue. I lost my Dockers apps and have been installing them from 'Previous apps' one by one, due to me not keeping them updated too often I'm having issues.

On Nextcloud I'm getting the below errors when updating, any suggestions?

I'm on an older MariaDB docker app (which was working fine before losing everthing) databases all look to be intact and MariaDBDcontainer is working/running on usual port.

Quote

March 13, 20251 yr

On 3/12/2025 at 6:07 AM, egtrev said:

Hi all, I'm trying to troubleshoot an upgrade issue. I lost my Dockers apps and have been installing them from 'Previous apps' one by one, due to me not keeping them updated too often I'm having issues.

On Nextcloud I'm getting the below errors when updating, any suggestions?

I'm on an older MariaDB docker app (which was working fine before losing everthing) databases all look to be intact and MariaDBDcontainer is working/running on usual port.

Roll back your Nextcloud docker to the previous version, ie. 30.0.14 by tagging the Nextcloud docker. Once that is up and running, upgrade your MariaDB docker, make sure Nextcloud is running fine on the new MariaDB and then upgrade Nextcloud.

I'm not sure if you ran the occ upgrade command, because the upgrade failed, or you're used to doing it that way. Nextcloud will automatically upgrade when you start the docker, if you have the "latest" tag or you tag a higher version than the one you were on. You shouldn't be trying manually on a tagged version.

Edited March 13, 20251 yr by Geck0

Quote

March 13, 20251 yr

After my fiasco a few weeks back been afraid to do much with Nextcloud.

On my MAIN instance - it is currently: lscr.io/linuxserver/nextcloud:version-30.0.5

Would it be wise to go 30.0.7 first and then THEN 31.0.1 or?

Quote

March 14, 20251 yr

On 2/26/2025 at 9:27 PM, Tolete said:
Hello, for anyone having ROW_FORMAT db errors on nextcloud, here is the fix for you.

Nextcloud error
Incorrect row format found in your database. ROW_FORMAT=Dynamic offers the best database performances for Nextcloud. Please update row format on the following list: oc_accounts, oc_accounts_data, oc_activity, oc_activity_mq, oc_addressbookchanges, oc_addressbooks, oc_appconfig, oc_authorized_groups, oc_authtoken, oc_bruteforce_attempts, oc_calendar_appt_bookings, oc_calendar_appt_configs, oc_calendar_invitations, oc_calendar_reminders, 
.....
Open a terminal on your Unraid server and run:
docker exec -it mariadb mysql -u root -p
Enter your MariaDB root password when prompted.

Select the Nextcloud Database:
USE nextcloud;
(Replace nextcloud with your actual Nextcloud database name if different.)

Update the ROW_FORMAT for All Affected Tables:

Run the following command:
SET GLOBAL innodb_large_prefix = 1;
SET GLOBAL innodb_file_format = BARRACUDA;
SET GLOBAL innodb_file_per_table = 1;
Update All Affected Tables to ROW_FORMAT=DYNAMIC

Run this command to generate the required ALTER statements:
SELECT CONCAT('ALTER TABLE ', table_name, ' ROW_FORMAT=DYNAMIC;')
FROM information_schema.tables
WHERE table_schema = 'nextcloud';
(Replace nextcloud with your actual Nextcloud database name if different.)

This will generate ALTER TABLE statements.

Copy the output and execute each ALTER TABLE ... command manually.

(your list will vary)
ALTER TABLE oc_onlyoffice_filekey ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_preferences ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_privacy_admins ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_profile_config ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_properties ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_ratelimit_entries ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_recent_contact ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_assets ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_direct ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_template ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_richdocuments_wopi ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_rocket_file_chats ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_rocket_users ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_schedulingobjects ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_share ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_share_external ROW_FORMAT=DYNAMIC;
ALTER TABLE oc_storages ROW_FORMAT=DYNAMIC;
Then restart Mariadb and Nextcloud
docker restart mariadb
docker restart nextcloud
-This is the way.

why i'm getting this error on step #4
Database changed
MariaDB [nextcloud]> SET GLOBAL innodb_large_prefix = 1;
ERROR 1193 (HY000): Unknown system variable 'innodb_large_prefix'
MariaDB [nextcloud]> SET GLOBAL innodb_file_format = BARRACUDA;
ERROR 1193 (HY000): Unknown system variable 'innodb_file_format'
MariaDB [nextcloud]> SET GLOBAL innodb_file_per_table = 1;
Query OK, 0 rows affected, 1 warning (0.000 sec)

Quote

March 14, 20251 yr

4 minutes ago, Erik1erik1 said:

why i'm getting this error on step #4
Database changed
MariaDB [nextcloud]> SET GLOBAL innodb_large_prefix = 1;
ERROR 1193 (HY000): Unknown system variable 'innodb_large_prefix'
MariaDB [nextcloud]> SET GLOBAL innodb_file_format = BARRACUDA;
ERROR 1193 (HY000): Unknown system variable 'innodb_file_format'
MariaDB [nextcloud]> SET GLOBAL innodb_file_per_table = 1;
Query OK, 0 rows affected, 1 warning (0.000 sec)

You're seeing ERROR 1193 (HY000): Unknown system variable for innodb_large_prefix and innodb_file_format because these settings have been deprecated and removed in MariaDB 10.3+.

Quote

[Support] Linuxserver.io - Nextcloud

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

CHBMB

Konijntjes

gustomucho

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

CHBMB

Konijntjes

gustomucho

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)