Hello, I have problems with my Nextcloud. When I open the page and want to log in, it takes forever until I am in the dashboard. When browsing, it takes forever or not at all. Can you please tell me what could be the reason for this? I don’t have much installed on it. My Raspberry 4 is with 8gb. Hope you can help me.
Greetings
Please fill the troubleshooting template, and add the info which web server you chose.
sorry. please provide more information. I am totally new in this field.
cat /boot/dietpi/.version
echo $G_DISTRO_NAME $G_RASPBIAN
uname -a
echo $G_HW_MODEL_NAME or (EG: RPi3)ss -tulpn | grep LISTEN
dietpi-software list | grep " =2 "
and please paste the output of:
dpkg -l lighttpd apache2 nginx
oot@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=9
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
bullseye 0
root@DietPi:~# echo $G_HW_MODEL_NAME or (EG: RPi3)
-bash: Syntaxfehler beim unerwarteten Symbol »(«
tcp LISTEN 0 1024 127.0.0.1:32401 0.0.0.0:* users:(("Plex Media Serv",pid=714,fd=11))
tcp LISTEN 0 128 127.0.0.1:33141 0.0.0.0:* users:(("Plex Script Hos",pid=794,fd=4))
tcp LISTEN 0 32 0.0.0.0:53 0.0.0.0:* users:(("pihole-FTL",pid=507,fd=5))
tcp LISTEN 0 1000 0.0.0.0:22 0.0.0.0:* users:(("dropbear",pid=369,fd=4))
tcp LISTEN 0 256 127.0.0.1:5335 0.0.0.0:* users:(("unbound",pid=503,fd=4))
tcp LISTEN 0 128 127.0.0.1:32600 0.0.0.0:* users:(("Plex Tuner Serv",pid=843,fd=10))
tcp LISTEN 0 256 127.0.0.1:8953 0.0.0.0:* users:(("unbound",pid=503,fd=6))
tcp LISTEN 0 50 0.0.0.0:445 0.0.0.0:* users:(("smbd",pid=539,fd=44))
tcp LISTEN 0 128 0.0.0.0:5252 0.0.0.0:* users:(("dietpi-dashboar",pid=475,fd=6))
tcp LISTEN 0 5 127.0.0.1:4711 0.0.0.0:* users:(("pihole-FTL",pid=507,fd=11))
tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=605,fd=17))
tcp LISTEN 0 511 127.0.0.1:6379 0.0.0.0:* users:(("redis-server",pid=546,fd=7))
tcp LISTEN 0 50 0.0.0.0:139 0.0.0.0:* users:(("smbd",pid=539,fd=45))
tcp LISTEN 0 1024 0.0.0.0:80 0.0.0.0:* users:(("lighttpd",pid=705,fd=4))
tcp LISTEN 0 32 [::]:53 [::]:* users:(("pihole-FTL",pid=507,fd=7))
tcp LISTEN 0 1000 [::]:22 [::]:* users:(("dropbear",pid=369,fd=5))
tcp LISTEN 0 256 [::1]:8953 [::]:* users:(("unbound",pid=503,fd=5))
tcp LISTEN 0 50 [::]:445 [::]:* users:(("smbd",pid=539,fd=42))
tcp LISTEN 0 5 [::1]:4711 [::]:* users:(("pihole-FTL",pid=507,fd=10))
tcp LISTEN 0 511 [::1]:6379 [::]:* users:(("redis-server",pid=546,fd=8))
tcp LISTEN 0 50 [::]:139 [::]:* users:(("smbd",pid=539,fd=43))
tcp LISTEN 0 1024 *:32400 *:* users:(("Plex Media Serv",pid=714,fd=10))
tcp LISTEN 0 1024 [::]:80 [::]:* users:(("lighttpd",pid=705,fd=5))
ID 0 | =2 | OpenSSH Client: Feature-rich SSH, SFTP and SCP client |
ID 7 | =2 | FFmpeg: Audio & video codec libary and programs |
ID 17 | =2 | Git: Clone and manage Git repositories locally |
ID 42 | =2 | Plex Media Server: web interface media streaming server | | https://dietpi.com/docs/software/media/#plex-media-server
ID 81 | =2 | LLSP: Lighttpd + SQLite + PHP | +Lighttpd +SQLite +PHP | https://dietpi.com/docs/software/webserver_stack/#llsp-web-stack
ID 82 | =2 | LLMP: Lighttpd + MariaDB + PHP | +Lighttpd +MariaDB +PHP | https://dietpi.com/docs/software/webserver_stack/#llmp-web-stack
ID 84 | =2 | Lighttpd: Extremely lightweight webserver | +PHP | https://dietpi.com/docs/software/webserver_stack/#lighttpd
ID 87 | =2 | SQLite: Persistent single-file database system | | https://dietpi.com/docs/software/databases/#sqlite
ID 88 | =2 | MariaDB: Persistent cached file-per-table database server | | https://dietpi.com/docs/software/databases/#mariadb
ID 89 | =2 | PHP: Hypertext Preprocessor for dynamic web content | | https://dietpi.com/docs/software/webserver_stack/#php
ID 91 | =2 | Redis: Volatile in-memory non-SQL database server | | https://dietpi.com/docs/software/databases/#redis
ID 93 | =2 | Pi-hole: block adverts for any device on your network | +Git +PHP +webserver | https://dietpi.com/docs/software/dns_servers/#pi-hole
ID 96 | =2 | Samba Server: Feature-rich SMB/CIFS server | | https://dietpi.com/docs/software/file_servers/#samba
ID 103 | =2 | DietPi-RAMlog: Makes /var/log a RAM disk, preserves file structure on reboot | | https://dietpi.com/docs/software/log_system/#dietpi-ramlog
ID 104 | =2 | Dropbear: Lightweight SSH server | | https://dietpi.com/docs/software/ssh/#dropbear
ID 114 | =2 | Nextcloud: File sync, sharing and collaboration platform | +MariaDB +PHP +Redis +webserver | https://dietpi.com/docs/software/cloud/#nextcloud
ID 130 | =2 | Python 3: Runtime system, pip package installer and development headers | | https://dietpi.com/docs/software/programming/#python-3
ID 182 | =2 | Unbound: validating, recursive, caching DNS resolver | | https://dietpi.com/docs/software/dns_servers/#unbound
ID 200 | =2 | DietPi-Dashboard (beta): Official lightweight DietPi web interface (Rust) | | https://dietpi.com/docs/software/system_stats/#dietpi-dashboard
dpkg-query: Kein Paket gefunden, das auf apache2 passt
dpkg-query: Kein Paket gefunden, das auf nginx passt
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Architektur Beschreibung
+++-==============-================-============-===============================
=============
ii lighttpd 1.4.59-1+deb11u2 arm64 fast webserver with minimal mem
ory footprint
Does no one have an idea what this could be?
how does system resourcing look like? Have a look to htop while trying to connect to NC.
You still didn’t answer the questions properly so we can just guess.
Do you use a SD card? If yes, what card do you use?
Does the pihole page is loading faster then nextcloud?
when i type htop i get this:
0[||| 4.6%] Mem[||||| 301M/7.61G]
1[| 0.7%] Swp[ 0K/0K]
2[|| 2.6%] Tasks: 33; 1 running
3[| 0.7%] Load average: 0.97 0.36 0.13
Avg[|| 2.2%] Uptime: 00:01:41
PID△USER RES NI CPU% TIME+ Command
1 root 9668 0 0.0 0:00.84 /sbin/init
133 root 7200 0 0.0 0:00.23 ├─ /lib/systemd/systemd-journald
169 root 4772 0 0.0 0:00.21 ├─ /lib/systemd/systemd-udevd
338 root 2696 0 0.0 0:00.01 ├─ /usr/bin/vmtouch -l /boot/dietpi /boot/dietpi.txt
346 root 828 0 0.0 0:00.03 ├─ /usr/sbin/rngd -f
368 root 184 0 0.0 0:00.00 ├─ /usr/sbin/dropbear -p 22 -W 65536
1577 root 2492 0 0.0 0:00.15 │ └─ /usr/sbin/dropbear -p 22 -W 65536
1578 root 5792 0 0.0 0:00.03 │ └─ -bash
1603 root 3752 0 2.0 0:00.92 │ └─ htop
472 root 4000 0 0.0 0:00.44 ├─ /opt/dietpi-dashboard/dietpi-dashboard
1510 root 5872 0 0.0 0:00.03 │ └─ /bin/bash
1611 root 3932 0 0.7 0:00.26 │ └─ htop
481 root 1488 0 0.0 0:00.00 ├─ /sbin/agetty -o -p -- \u --noclear tty1 linux
482 root 1872 0 0.0 0:00.00 ├─ /sbin/agetty -o -p -- \u --keep-baud 115200,57600,38400,9600 ttyS
503 unbound 12424 0 0.0 0:00.10 ├─ /usr/sbin/unbound -d -p
507 pihole 7572 -10 0.0 0:00.17 ├─ /usr/bin/pihole-FTL
533 root 14748 0 0.0 0:00.13 ├─ /usr/sbin/nmbd --foreground --no-process-group
540 root 22840 0 0.0 0:00.14 ├─ /usr/sbin/smbd --foreground --no-process-group
543 root 12128 0 0.0 0:00.00 │ ├─ /usr/sbin/smbd --foreground --no-process-group
544 root 6736 0 0.0 0:00.00 │ └─ /usr/sbin/smbd --foreground --no-process-group
547 redis 9680 0 0.0 0:00.36 ├─ /usr/bin/redis-server 127.0.0.1:6379
606 mysql 120M 0 0.0 0:01.93 ├─ /usr/sbin/mariadbd
648 root 29580 0 0.0 0:00.16 ├─ php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf)
682 www-data 44664 0 0.0 0:01.80 │ ├─ php-fpm: pool www
684 www-data 41620 0 4.6 0:00.44 │ ├─ php-fpm: pool www
685 www-data 41384 0 0.0 0:00.35 │ ├─ php-fpm: pool www
1541 www-data 43896 0 0.0 0:00.39 │ ├─ php-fpm: pool www
1574 www-data 7280 0 0.0 0:00.00 │ └─ php-fpm: pool www
704 www-data 3216 0 0.0 0:00.03 ├─ /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
so my dietpi runs smoothly. It is only about Nextcloud. I don’t have a SD card in it. Use the Raspberry with a m.2 ssd.
The Pi-hole admin interface behaves fine?
Generally Nextcloud web UI is kind of complex indeed, but an RPi 4 should be able to handle it. It could be also the database.
Is it a fresh Nextcloud instance? And are there any hints in the admin panel? Probably rebuilding the database tables can help, but this can take a while:
sudo mysqlcheck -o nextcloud
Let’s alao check some logs:
journalctl -u mariadb -u lighttpd -u php7.4-fpm -u redis-server
dmesg -l emerg,alert,crit,err
tail -5 /mnt/dietpi_userdata/nextcloud_data/nextcloud.log
root@DietPi:/# sudo mysqlcheck -o nextcloud
nextcloud.oc_accounts
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_accounts_data
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_activity
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_activity_mq
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_addressbookchanges
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_addressbooks
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_appconfig
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_authorized_groups
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_authtoken
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_bruteforce_attempts
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendar_invitations
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendar_reminders
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendar_resources
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendar_resources_md
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendar_rooms
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendar_rooms_md
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendarchanges
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendarobjects
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendarobjects_props
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendars
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_calendarsubscriptions
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_cards
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_cards_properties
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_circle
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_event
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_member
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_membership
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_mount
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_mountpoint
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_remote
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_share_lock
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_circles_token
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_collres_accesscache
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_collres_collections
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_collres_resources
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_comments
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_comments_read_markers
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_dav_cal_proxy
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_dav_shares
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_direct_edit
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_directlink
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_external_applicable
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_external_config
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_external_mounts
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_external_options
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_federated_reshares
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_file_locks
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_file_metadata
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_filecache
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_filecache_extended
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_files_trash
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_flow_checks
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_flow_operations
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_flow_operations_scope
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_group_admin
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_group_user
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_groups
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_jobs
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_known_users
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_login_flow_v2
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_migrations
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_mimetypes
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_mounts
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_notifications
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_notifications_pushhash
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_notifications_settings
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_oauth2_access_tokens
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_oauth2_clients
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_preferences
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_privacy_admins
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_profile_config
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_properties
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_ratelimit_entries
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_reactions
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_recent_contact
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_schedulingobjects
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_share
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_share_external
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_storages
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_storages_credentials
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_systemtag
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_systemtag_group
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_systemtag_object_mapping
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_text_documents
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_text_sessions
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_text_steps
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_trusted_servers
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_twofactor_backupcodes
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_twofactor_providers
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_user_status
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_user_transfer_owner
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_users
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_vcategory
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_vcategory_to_object
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_webauthn
note : Table does not support optimize, doing recreate + analyze instead
status : OK
nextcloud.oc_whats_new
note : Table does not support optimize, doing recreate + analyze instead
status : OK
root@DietPi:/# journalctl -u mariadb -u lighttpd -u php7.4-fpm -u redis-server
dmesg -l emerg,alert,crit,err
tail -5 /mnt/dietpi_userdata/nextcloud_data/nextcloud.log
-- Journal begins at Mon 2022-10-17 14:17:03 CEST, ends at Mon 2022-10-17 19:09:03 CEST. --
Okt 17 14:17:07 DietPi systemd[1]: Starting Advanced key-value store...
Okt 17 14:17:07 DietPi redis-server[547]: 547:C 17 Oct 2022 14:17:07.784 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
Okt 17 14:17:07 DietPi redis-server[547]: 547:C 17 Oct 2022 14:17:07.785 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Okt 17 14:17:07 DietPi redis-server[547]: 547:C 17 Oct 2022 14:17:07.785 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=547, just started
Okt 17 14:17:07 DietPi redis-server[547]: 547:C 17 Oct 2022 14:17:07.785 # Configuration loaded
Okt 17 14:17:07 DietPi redis-server[547]: WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
Okt 17 14:17:07 DietPi redis-server[547]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Okt 17 14:17:07 DietPi redis-server[547]: Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=547, just started
Okt 17 14:17:07 DietPi redis-server[547]: Configuration loaded
Okt 17 14:17:07 DietPi redis-server[547]: 547:M 17 Oct 2022 14:17:07.794 # Server initialized
Okt 17 14:17:07 DietPi redis-server[547]: 547:M 17 Oct 2022 14:17:07.794 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Okt 17 14:17:07 DietPi redis[547]: Server initialized
Okt 17 14:17:07 DietPi redis[547]: WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Okt 17 14:17:07 DietPi systemd[1]: Started Advanced key-value store.
Okt 17 14:17:07 DietPi systemd[1]: Starting MariaDB 10.5.15 database server...
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 606 ...
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Uses event mutexes
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Number of pools: 1
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Using ARMv8 crc32 instructions
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Using Linux native AIO
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Completed initialization of buffer pool
Okt 17 14:17:08 DietPi mariadbd[606]: 2022-10-17 14:17:08 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=206325089,206325089
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: Starting final batch to recover 107 pages from redo log.
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: 128 rollback segments are active.
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: 10.5.15 started; log sequence number 231365738; transaction id 844840
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] InnoDB: Loading buffer pool(s) from /mnt/dietpi_userdata/mysql/ib_buffer_pool
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] Plugin 'FEEDBACK' is disabled.
Okt 17 14:17:10 DietPi mariadbd[606]: 2022-10-17 14:17:10 0 [Note] Server socket created on IP: '127.0.0.1'.
Okt 17 14:17:11 DietPi mariadbd[606]: 2022-10-17 14:17:11 0 [Note] Reading of all Master_info entries succeeded
Okt 17 14:17:11 DietPi mariadbd[606]: 2022-10-17 14:17:11 0 [Note] Added new Master_info '' to hash table
Okt 17 14:17:11 DietPi mariadbd[606]: 2022-10-17 14:17:11 0 [Note] /usr/sbin/mariadbd: ready for connections.
Okt 17 14:17:11 DietPi mariadbd[606]: Version: '10.5.15-MariaDB-0+deb11u1' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 11
Okt 17 14:17:11 DietPi systemd[1]: Started MariaDB 10.5.15 database server.
Okt 17 14:17:11 DietPi systemd[1]: Starting The PHP 7.4 FastCGI Process Manager...
Okt 17 14:17:11 DietPi /etc/mysql/debian-start[647]: Looking for 'mysql' as: /usr/bin/mysql
Okt 17 14:17:11 DietPi /etc/mysql/debian-start[647]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Okt 17 14:17:11 DietPi /etc/mysql/debian-start[647]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Okt 17 14:17:11 DietPi /etc/mysql/debian-start[647]: There is no need to run mysql_upgrade again for 10.5.15-MariaDB.
Okt 17 14:17:11 DietPi /etc/mysql/debian-start[647]: You can use --force if you still want to run mysql_upgrade
Okt 17 14:17:11 DietPi /etc/mysql/debian-start[660]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
Okt 17 14:17:12 DietPi mariadbd[606]: 2022-10-17 14:17:12 0 [Note] InnoDB: Buffer pool(s) load completed at 221017 14:17:12
Okt 17 14:17:12 DietPi systemd[1]: Started The PHP 7.4 FastCGI Process Manager.
Okt 17 14:17:12 DietPi systemd[1]: Starting Lighttpd Daemon...
Okt 17 14:17:13 DietPi systemd[1]: Started Lighttpd Daemon.
[ 0.442256] bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.
{"reqId":"N0FBfkx10NHvL9ri8nWP","level":3,"time":"2022-10-14T19:29:42+00:00","remoteAddr":"192.168.178.21","user":"--","app":"core","method":"GET","url":"/nextcloud/index.php/login?redirect_url=/nextcloud/index.php/apps/dashboard/","message":"Tried to log in admin but could not verify token","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0","version":"24.0.6.1","data":{"app":"core"}}
{"reqId":"r4T5EMtHU4gTDRlslO0V","level":3,"time":"2022-10-14T19:29:44+00:00","remoteAddr":"192.168.178.21","user":"--","app":"core","method":"POST","url":"/nextcloud/index.php/login","message":"Tried to log in admin but could not verify token","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0","version":"24.0.6.1","data":{"app":"core"}}
{"reqId":"Psi0OkUzYodJ91UHqGXe","level":3,"time":"2022-10-15T04:17:27+00:00","remoteAddr":"192.168.178.21","user":"--","app":"core","method":"GET","url":"/nextcloud/index.php/apps/dashboard/","message":"Tried to log in admin but could not verify token","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0","version":"24.0.6.1","data":{"app":"core"}}
{"reqId":"zfp3yEi9MZQFDlq2oN6A","level":3,"time":"2022-10-15T04:17:27+00:00","remoteAddr":"192.168.178.21","user":"--","app":"core","method":"GET","url":"/nextcloud/index.php/login?redirect_url=/nextcloud/index.php/apps/dashboard/","message":"Tried to log in admin but could not verify token","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0","version":"24.0.6.1","data":{"app":"core"}}
{"reqId":"3pOOXZ26IGR5iEMDOJYo","level":3,"time":"2022-10-15T04:17:30+00:00","remoteAddr":"192.168.178.21","user":"--","app":"core","method":"POST","url":"/nextcloud/index.php/login","message":"Tried to log in admin but could not verify token","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0","version":"24.0.6.1","data":{"app":"core"}}
root@DietPi:/#
Another thing I noticed is that my Raspi just turns off. But I don’t know why that is. I have to restart it manually. Has now also happened a few times.
The logs look all good aside of two or three failing Nextcloud login attempts over two days.
Is this a fresh Nextcloud instance?
I see Plex installed but no related running process. It that one fine?
journalctl -u plex
You could btw do some cleanup if you’re not using vmtouch manually:
apt autopurge vmtouch
So all the programs were running fine before the Nextcloud installation. Have now entered the commands what you have written. Get then that here:
root@DietPi:/# journalctl -u plex
-- Journal begins at Mon 2022-10-17 14:17:03 CEST, ends at Tue 2022-10-18 18:04:05 CEST. --
-- No entries --
root@DietPi:/# apt autopurge vmtouch
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden Pakete werden ENTFERNT:
vmtouch*
0 aktualisiert, 0 neu installiert, 1 zu entfernen und 0 nicht aktualisiert.
Nach dieser Operation werden 53,2 kB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] J
(Lese Datenbank ... 30377 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von vmtouch (1.3.1-dietpi1) ...
Deconfiguring vmtouch systemd service ....................................................................]
Removed /etc/systemd/system/local-fs.target.wants/vmtouch.service.
(Lese Datenbank ... 30373 Dateien und Verzeichnisse sind derzeit installiert.)............................]
Löschen der Konfigurationsdateien von vmtouch (1.3.1-dietpi1) ...
I have rebooted but it still does not work. I think I need to remove Nextcloud. This makes me too much problem 
you could try to remove, reboot and install again. This should reimport all your data automatically.
I think it’s not a general nextcloud problem.
Do you use DDNS and let’s encrypt / SSL? I had some trouble in the past with redirection / hostname / DNS (I modified manually some stuff in a try-and-error style and created some sort of loop 
)
Did you chang anything before these problems occured?
Do you have this problem regardless of whether you connect over the internet or from LAN?
Does other web services (Pihole) behave the same?
I run now nextcloud, pihole, unbound, some file servers and other stuff on a RPi 3 b+ (booting from USB SSD) without any problems.
You also said you Raspi just turns randomly off, which is very odd too. If i had these problems I would start from scratch.
I didn’t actually change anything before I installed Nextcloud. Raspi is connected to a lan and via my Iphone from outside this is good to reach. only in home network I have the problem… As I said at the beginning everything worked fine but a few days later it became really slow.
you mean access from internet is fine without slowness?