i let is run a bit longer when booting from the usb stick and tried another power source for the pi and it still did not boot. but letting it run longer it gave me this
something seems to be wrong with your USB stick, as it is reporting I/O errors.
@MichaIng any further ideas?
Hi, Ok I reinstalled dietpi on a new SD card and installed Nextcloud and set it up as per the instructions here And all on the Nextcloud seems to be working. File Browser and allo.com still not working.
When running
dietpi-services status I get
root@DietPi:~# dietpi-services status
DietPi-Services
─────────────────────────────────────────────────────
Mode: status
[ OK ] DietPi-Services | redis-server active (running) since Tue 2024-03-05 14:10:40 GMT; 1min 40s ago
[ OK ] DietPi-Services | mariadb active (running) since Tue 2024-03-05 14:10:43 GMT; 1min 38s ago
[ OK ] DietPi-Services | php8.2-fpm active (running) since Tue 2024-03-05 14:10:45 GMT; 1min 36s ago
[ OK ] DietPi-Services | apache2 active (running) since Tue 2024-03-05 14:10:46 GMT; 1min 34s ago
[FAILED] DietPi-Services | × filebrowser.service - File Browser (DietPi)
Loaded: loaded (/etc/systemd/system/filebrowser.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-03-05 14:10:41 GMT; 1min 40s ago
Duration: 2.182s
Docs: https://filebrowser.org/
Main PID: 575 (code=exited, status=2)
CPU: 48ms
Mar 05 14:10:41 DietPi filebrowser[575]: github.com/spf13/cobra.(*Command).ExecuteC(0xdef0c0)
Mar 05 14:10:41 DietPi filebrowser[575]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x320
Mar 05 14:10:41 DietPi filebrowser[575]: github.com/spf13/cobra.(*Command).Execute(...)
Mar 05 14:10:41 DietPi filebrowser[575]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
Mar 05 14:10:41 DietPi filebrowser[575]: github.com/filebrowser/filebrowser/v2/cmd.Execute()
Mar 05 14:10:41 DietPi filebrowser[575]: /home/runner/work/filebrowser/filebrowser/cmd/cmd.go:9 +0x24
Mar 05 14:10:41 DietPi filebrowser[575]: main.main()
Mar 05 14:10:41 DietPi filebrowser[575]: /home/runner/work/filebrowser/filebrowser/main.go:8 +0x1c
Mar 05 14:10:41 DietPi systemd[1]: filebrowser.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 05 14:10:41 DietPi systemd[1]: filebrowser.service: Failed with result 'exit-code'.
[ OK ] DietPi-Services | cron active (running) since Tue 2024-03-05 14:10:43 GMT; 1min 38s ago
[ OK ] DietPi-Services | dropbear active (running) since Tue 2024-03-05 14:10:39 GMT; 1min 42s ago
[ OK ] DietPi-Services | nxserver active (running) since Tue 2024-03-05 14:10:39 GMT; 1min 42s ago
[ INFO ] DietPi-Services | dietpi-vpn inactive (dead)
[ INFO ] DietPi-Services | dietpi-cloudshell inactive (dead)
[ OK ] DietPi-Services | dietpi-ramlog active (exited) since Tue 2024-03-05 14:10:15 GMT; 2min 6s ago
[ OK ] DietPi-Services | dietpi-preboot active (exited) since Tue 2024-03-05 14:10:15 GMT; 2min 6s ago
[ OK ] DietPi-Services | dietpi-postboot active (exited) since Tue 2024-03-05 14:10:39 GMT; 1min 42s ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
root@DietPi:~# `
Next time, when checking an ext4 partition on another system, run fsck -af /dev/sda2, to force an actual check. Because if no dirty bit was set, fsck just skips the check, which is what happened on your other Pi:
/dev/sda2: clean, 76398/3833856 files, 999573/15326976 blocks
Is is pretty common that I/O errors at certain stages or when going along with a kernel crash, fail to set the dirty bit, so this -f is a must whenever diagnosing ext4 partitions after a failure.
Can you show the full output of File Browser:
journalctl -u filebrowser
ok thanks for that
here is the result for
Mar 05 14:56:01 DietPi systemd[1]: Started filebrowser.service - File Browser (DietPi).
Mar 05 14:56:03 DietPi filebrowser[592]: panic: stat /mnt/dietpi_userdata/filebrowser/filebrowser.db: permission denied
Mar 05 14:56:03 DietPi filebrowser[592]: goroutine 1 [running]:
Mar 05 14:56:03 DietPi filebrowser[592]: github.com/filebrowser/filebrowser/v2/cmd.init.python.func11(0x400017a700?, {0x400003c900, 0x0, 0x2})
Mar 05 14:56:03 DietPi filebrowser[592]: /home/runner/work/filebrowser/filebrowser/cmd/utils.go:93 +0x1e4
Mar 05 14:56:03 DietPi filebrowser[592]: github.com/spf13/cobra.(*Command).execute(0xdef0c0, {0x4000030190, 0x2, 0x2})
Mar 05 14:56:03 DietPi filebrowser[592]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920 +0x640
Mar 05 14:56:03 DietPi filebrowser[592]: github.com/spf13/cobra.(*Command).ExecuteC(0xdef0c0)
Mar 05 14:56:03 DietPi filebrowser[592]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x320
Mar 05 14:56:03 DietPi filebrowser[592]: github.com/spf13/cobra.(*Command).Execute(...)
Mar 05 14:56:03 DietPi filebrowser[592]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
Mar 05 14:56:03 DietPi filebrowser[592]: github.com/filebrowser/filebrowser/v2/cmd.Execute()
Mar 05 14:56:03 DietPi filebrowser[592]: /home/runner/work/filebrowser/filebrowser/cmd/cmd.go:9 +0x24
Mar 05 14:56:03 DietPi filebrowser[592]: main.main()
Mar 05 14:56:03 DietPi filebrowser[592]: /home/runner/work/filebrowser/filebrowser/main.go:8 +0x1c
Mar 05 14:56:03 DietPi systemd[1]: filebrowser.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 05 14:56:03 DietPi systemd[1]: filebrowser.service: Failed with result 'exit-code'.
Mar 05 15:00:54 DietPi systemd[1]: Started filebrowser.service - File Browser (DietPi).
Mar 05 15:00:54 DietPi filebrowser[4209]: panic: stat /mnt/dietpi_userdata/filebrowser/filebrowser.db: permission denied
Mar 05 15:00:54 DietPi filebrowser[4209]: goroutine 1 [running]:
Mar 05 15:00:54 DietPi filebrowser[4209]: github.com/filebrowser/filebrowser/v2/cmd.init.python.func11(0x4000134700?, {0x40000ca8c0, 0x0, 0x2})
Mar 05 15:00:54 DietPi filebrowser[4209]: /home/runner/work/filebrowser/filebrowser/cmd/utils.go:93 +0x1e4
Mar 05 15:00:54 DietPi filebrowser[4209]: github.com/spf13/cobra.(*Command).execute(0xdef0c0, {0x40000a4160, 0x2, 0x2})
Mar 05 15:00:54 DietPi filebrowser[4209]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920 +0x640
Mar 05 15:00:54 DietPi filebrowser[4209]: github.com/spf13/cobra.(*Command).ExecuteC(0xdef0c0)
Mar 05 15:00:54 DietPi filebrowser[4209]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x320
Mar 05 15:00:54 DietPi filebrowser[4209]: github.com/spf13/cobra.(*Command).Execute(...)
Mar 05 15:00:54 DietPi filebrowser[4209]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
Mar 05 15:00:54 DietPi filebrowser[4209]: github.com/filebrowser/filebrowser/v2/cmd.Execute()
Mar 05 15:00:54 DietPi filebrowser[4209]: /home/runner/work/filebrowser/filebrowser/cmd/cmd.go:9 +0x24
Mar 05 15:00:54 DietPi filebrowser[4209]: main.main()
Mar 05 15:00:54 DietPi filebrowser[4209]: /home/runner/work/filebrowser/filebrowser/main.go:8 +0x1c
Mar 05 15:00:54 DietPi systemd[1]: filebrowser.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 05 15:00:54 DietPi systemd[1]: filebrowser.service: Failed with result 'exit-code'.
Mar 05 15:21:46 DietPi systemd[1]: Started filebrowser.service - File Browser (DietPi).
Mar 05 15:21:46 DietPi filebrowser[41320]: panic: stat /mnt/dietpi_userdata/filebrowser/filebrowser.db: permission denied
Mar 05 15:21:46 DietPi filebrowser[41320]: goroutine 1 [running]:
Mar 05 15:21:46 DietPi filebrowser[41320]: github.com/filebrowser/filebrowser/v2/cmd.init.python.func11(0x400017a700?, {0x400003c900, 0x0, 0x2})
Mar 05 15:21:46 DietPi filebrowser[41320]: /home/runner/work/filebrowser/filebrowser/cmd/utils.go:93 +0x1e4
Mar 05 15:21:46 DietPi filebrowser[41320]: github.com/spf13/cobra.(*Command).execute(0xdef0c0, {0x4000030190, 0x2, 0x2})
Mar 05 15:21:46 DietPi filebrowser[41320]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:920 +0x640
Mar 05 15:21:46 DietPi filebrowser[41320]: github.com/spf13/cobra.(*Command).ExecuteC(0xdef0c0)
Mar 05 15:21:46 DietPi filebrowser[41320]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x320
Mar 05 15:21:46 DietPi filebrowser[41320]: github.com/spf13/cobra.(*Command).Execute(...)
Mar 05 15:21:46 DietPi filebrowser[41320]: /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
Mar 05 15:21:46 DietPi filebrowser[41320]: github.com/filebrowser/filebrowser/v2/cmd.Execute()
Mar 05 15:21:46 DietPi filebrowser[41320]: /home/runner/work/filebrowser/filebrowser/cmd/cmd.go:9 +0x24
Mar 05 15:21:46 DietPi filebrowser[41320]: main.main()
Mar 05 15:21:46 DietPi filebrowser[41320]: /home/runner/work/filebrowser/filebrowser/main.go:8 +0x1c
Mar 05 15:21:46 DietPi systemd[1]: filebrowser.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 05 15:21:46 DietPi systemd[1]: filebrowser.service: Failed with result 'exit-code'.
Again some permission issue
Can you check
ls -la /mnt/dietpi_userdata/filebrowser/
chown -R filebrowser:root /mnt/dietpi_userdata/filebrowser
systemctl restart filebrowser
Makes perfectly sense. This basically needs to be done for every software title, which stores stuff in /mnt/dietpi_userdata. UNIX permissions are stored with user IDs (UID) and group IDs (GID), no names. And the IDs are given in ascending order, hence they can be different on a new system, depending on the order in which users are added.
While for Nextcloud in particular it was easier to install it freshly first, and adjust /mnt/dietpi_userdata afterwards, in most other cases it is actually the other way round: Switch /mnt/dietpi_userdata first to the old data drive, then install software. Those will migrate the existing data/configs, re-apply permissions etc.
Actually would be great to have it the same way for Nextcloud, i.e. doing the migration steps automatically if the data directory exists already, but no database. If only the list of things to do was not much larger than time to work on things 
.
I used the above but when I go to http:<my.ip.address>:8084 it still does not load
pls reboot your system and check service logs again
I rebooted the dietpi and ran
here is the result
Mar 06 08:23:15 DietPi systemd[1]: Started filebrowser.service - File Browser (DietPi).
Mar 06 08:23:18 DietPi filebrowser[615]: 2024/03/06 08:23:18 No config file used
Mar 06 08:23:18 DietPi filebrowser[615]: 2024/03/06 08:23:18 Listening on 127.0.0.1:8080
looks like Filebrowser has been started with default configs, without DietPi adjustments
you can try following
systemctl stop filebrowser
cd /mnt/dietpi_userdata/filebrowser
/opt/filebrowser/filebrowser config set -a 0.0.0.0 -p 8084 -r /mnt
systemctl start filebrowser
replies:
Sign up: false
Create User Dir: false
Auth method: json
Shell:
Branding:
Name:
Files override:
Disable external links: false
Disable used disk percentage graph: false
Color:
Theme:
Server:
Log: stdout
Port: 8084
Base URL:
Root: /mnt
Socket:
Address: 0.0.0.0
TLS Cert:
TLS Key:
Exec Enabled: false
Defaults:
Scope: .
Locale: en
View mode: mosaic
Single Click: false
Commands:
Sorting:
By:
Asc: false
Permissions:
Admin: false
Execute: true
Create: true
Rename: true
Modify: true
Delete: true
Share: true
Download: true
Auther configuration (raw):
{
"recaptcha": null
}
yes this is the configuration. Did you checked logs after service restart?
no, how do I do that? sorry
Is this all something to do with Apache? when I just enter my IP address into firefox it gives me this page:
You did this already
This has noting to do with Apache.
ok. restarted again and ran
got
ar 06 09:29:10 DietPi systemd[1]: Started filebrowser.service - File Browser (DietPi).
Mar 06 09:29:12 DietPi filebrowser[569]: 2024/03/06 09:29:12 No config file used
Mar 06 09:29:12 DietPi filebrowser[569]: 2024/03/06 09:29:12 Listening on [::]:8084
in firefox it now shows the file browser login page, but when entering the standard login and password, it says wrong login credentials
you can try to set a new one
systemctl stop filebrowser
cd /mnt/dietpi_userdata/filebrowser
/opt/filebrowser/filebrowser users update dietpi <password> --perm.admin
systemctl start filebrowser
returns
bash: password: No such file or directory
what exactly you have entered?
I entered this