Hi everybody again after a while.
I re-opened this thread (I’m not sure if this is fine) because after some time I realized my owncloud is not working anymore.
I just changed the PC and can’t access the owncloud from the old or the new one.
Is there some way to check if owncloud is still in my diet-pi and how to restore it?
Anyway, all the files are saved on the old PC.
thanks again for any precious suggestions.
Hello, I moved your problem into a new thread.
Can you please provide more info about your system:
#### Required Information
- DietPi version | `cat /boot/dietpi/.version`
- Distro version | `echo $G_DISTRO_NAME $G_RASPBIAN`
- Kernel version | `uname -a`
- Architecture | `dpkg --print-architecture`
- SBC model | `echo $G_HW_MODEL_NAME` or (EG: RPi3)
What happens when you access your nextcloud via browser, do you get any error messages or what is happening?
Can you also try on the CLI:
occ list
DietPi version | v9.0.2
Distro version | bullseye 1
Kernel version | Linux DietPi 6.1.21+ #1642 Mon Apr 3 17:19:14 BST 2023 armv6l GNU/Linux
Architecture | armhf
SBC model | RPi Zero W (armv6l)
The problem is that I can’t reach the owncloud server. In the browser, nothing happens… just rolling the weel for long time 
Is it possible to reboot owncloud with dietpi interface?
No, it’s a webapp running on your webserver. Do you have other stuff running on your server? Are they still reachable? And which webserver do you use?
Can you share the output of
php -v
Thanks @Jappe,
I’m quite sure I don’t have any other stuff running… at least something that is not necessary for owncloud.
This is the output for the command suggested:
PHP 7.4.33 (cli) (built: Jun 9 2023 16:51:37) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.33, Copyright (c), by Zend Technologies
You can also have a look into the logs of your webserver for possible error messages.
Which webserver do you use?
journalctl
these are the first 15 rows of the Journalctl command:
Feb 08 01:25:02 DietPi systemd-timesyncd[14131]: Initial synchronization to time server 212.45.144.206:123 (0.debian.pool.ntp.org).
Feb 08 01:25:02 DietPi systemd[1]: Stopping Network Time Synchronization...
Feb 08 01:25:02 DietPi systemd[1]: systemd-timesyncd.service: Succeeded.
Feb 08 01:25:02 DietPi systemd[1]: Stopped Network Time Synchronization.
Feb 08 01:25:09 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 29 using dwc_otg
Feb 08 01:25:10 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 30 using dwc_otg
Feb 08 01:25:12 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 31 using dwc_otg
Feb 08 01:25:13 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 32 using dwc_otg
Feb 08 01:25:15 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 33 using dwc_otg
Feb 08 01:25:16 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 34 using dwc_otg
Feb 08 01:25:17 DietPi kernel: usb 1-1.2.4: device not accepting address 34, error -71
Feb 08 01:25:18 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 35 using dwc_otg
Feb 08 01:25:19 DietPi kernel: usb 1-1.2.4: device descriptor read/all, error -71
Feb 08 01:25:19 DietPi kernel: usb 1-1.2-port4: attempt power cycle
Feb 08 01:25:21 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 37 using dwc_otg
Feb 08 01:25:21 DietPi kernel: usb 1-1.2.4: device not accepting address 37, error -71
And these the last
Feb 08 10:11:09 DietPi kernel: scsi host2: usb-storage 1-1.2.4:1.0
Feb 08 10:11:10 DietPi kernel: scsi 2:0:0:0: Direct-Access WD Elements 1078 1065 PQ: 0 ANSI: 6
Feb 08 10:11:10 DietPi kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Feb 08 10:11:10 DietPi kernel: sd 2:0:0:0: [sdc] Spinning up disk...
Feb 08 10:11:42 DietPi kernel: ........................
Feb 08 10:11:42 DietPi kernel: usb 1-1.2.4: USB disconnect, device number 64
Feb 08 10:11:43 DietPi kernel: .ready
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Sense not available.
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] 0-byte physical blocks
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Write Protect is off
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 00 00 00
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Asking for cache data failed
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through
Feb 08 10:11:43 DietPi kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
Feb 08 10:11:44 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 65 using dwc_otg
Feb 08 10:11:45 DietPi kernel: usb 1-1.2.4: new high-speed USB device number 66 using dwc_otg
Feb 08 10:11:45 DietPi systemd-udevd[28968]: sdc: Process '/lib/udev/hdparm' failed with exit code 2.
the problem is that in the middle there are thousands of other rows that I didn’t copy because they are really a lot.
About the webserver I honestly don’t remember. How can I check?
You can have a look into the “uninstall” section of dietpi-software.
Better to check status of all services.
dietpi-services status
This is the services status:
DietPi-Services
─────────────────────────────────────────────────────
Mode: status
[ OK ] DietPi-Services | avahi-daemon active (running) since Wed 2024-01-31 08:53:23 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | redis-server active (running) since Wed 2024-01-31 08:53:24 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | mariadb active (running) since Wed 2024-01-31 08:53:26 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | php7.4-fpm active (running) since Wed 2024-01-31 08:53:28 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | lighttpd active (running) since Wed 2024-01-31 08:53:36 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | cups active (running) since Wed 2024-01-31 08:53:37 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | cron active (running) since Wed 2024-01-31 08:53:37 CET; 1 weeks 1 days ago
[ OK ] DietPi-Services | dropbear active (running) since Mon 2024-01-29 18:17:18 CET; 1 weeks 2 days ago
[ INFO ] DietPi-Services | dietpi-vpn inactive (dead)
[ OK ] DietPi-Services | pihole-FTL active (exited) since Mon 2024-01-29 18:17:35 CET; 1 weeks 2 days ago
[ OK ] DietPi-Services | unbound active (running) since Mon 2024-01-29 18:17:28 CET; 1 weeks 2 days ago
[ INFO ] DietPi-Services | dietpi-cloudshell inactive (dead)
[ OK ] DietPi-Services | dietpi-ramlog active (exited) since Mon 2024-01-29 18:17:18 CET; 1 weeks 2 days ago
[ OK ] DietPi-Services | dietpi-preboot active (exited) since Mon 2024-01-29 18:17:20 CET; 1 weeks 2 days ago
[ OK ] DietPi-Services | dietpi-postboot active (exited) since Mon 2024-01-29 18:17:25 CET; 1 weeks 2 days ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
I can’t see owncloud, is this correct?
Yes this is correct since it has not it’s own service, it runs on top of lighttpd.
Can you check
journalctl -xe -u lighttpd
Can you check available porta
ss -tulpn | grep LISTEN
And how do access OC? Using IP address or DDNS?
-- Journal begins at Thu 2024-02-08 20:15:01 CET, ends at Fri 2024-02-09 09:26:56 CET. --
-- No entries --
Should I paste the output here, is this safe for me?
Usually, I use my DDNS (no-ip), I tried with some workaround to access it from local IP but I preferred to sync outside my network since it was too complicated. I’m often out.
yes
Are you able to access OC web site with local IP address inside your local network?
tcp LISTEN 0 256 127.0.0.1:8953 0.0.0.0:* users:(("unbound",pid=682,fd=6))
tcp LISTEN 0 1024 0.0.0.0:443 0.0.0.0:* users:(("lighttpd",pid=17674,fd=6))
tcp LISTEN 0 5 127.0.0.1:4711 0.0.0.0:* users:(("pihole-FTL",pid=828,fd=11))
tcp LISTEN 0 32 0.0.0.0:53 0.0.0.0:* users:(("pihole-FTL",pid=828,fd=5))
tcp LISTEN 0 1000 0.0.0.0:22 0.0.0.0:* users:(("dropbear",pid=376,fd=4))
tcp LISTEN 0 4096 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=320,fd=4),("systemd",pid=1,fd=66))
tcp LISTEN 0 1024 0.0.0.0:80 0.0.0.0:* users:(("lighttpd",pid=17674,fd=4))
tcp LISTEN 0 511 127.0.0.1:6379 0.0.0.0:* users:(("redis-server",pid=17525,fd=7))
tcp LISTEN 0 80 127.0.0.1:3306 0.0.0.0:* users:(("mariadbd",pid=17587,fd=15))
tcp LISTEN 0 256 127.0.0.1:5335 0.0.0.0:* users:(("unbound",pid=682,fd=4))
tcp LISTEN 0 128 0.0.0.0:631 0.0.0.0:* users:(("cupsd",pid=17685,fd=7))
tcp LISTEN 0 1024 [::]:443 [::]:* users:(("lighttpd",pid=17674,fd=7))
tcp LISTEN 0 32 [::]:53 [::]:* users:(("pihole-FTL",pid=828,fd=7))
tcp LISTEN 0 1000 [::]:22 [::]:* users:(("dropbear",pid=376,fd=5))
tcp LISTEN 0 511 [::1]:6379 [::]:* users:(("redis-server",pid=17525,fd=8))
tcp LISTEN 0 4096 [::]:111 [::]:* users:(("rpcbind",pid=320,fd=6),("systemd",pid=1,fd=69))
tcp LISTEN 0 1024 [::]:80 [::]:* users:(("lighttpd",pid=17674,fd=5))
tcp LISTEN 0 256 [::1]:8953 [::]:* users:(("unbound",pid=682,fd=5))
tcp LISTEN 0 5 [::1]:4711 [::]:* users:(("pihole-FTL",pid=828,fd=13))
I’ll try tomorrow when I’ll be back home
ok lighttpd is correctly LISTEN to port 80/443 and you should be able to reach the web server by it’s local IP address.
I’m trying now but I can’t reach the server. Nor the dietpi nor the Owncloud…
I tried both with the terminal and with the server… This is strange, isn’t it?
So you are not able to connect via SSH? Did you already reboot? What about connecting a screen?
Exactly I’m not able to connect via SSH if I’m on my network. If I’m outside everything goes well.
About the screen, I should work a bit to connect one. If I connect with a screen should I see something?