I had the latest version of OC running fine on a Raspberry Pi, and just completed my first sync with the server. I shutdown the Pi to make a backup of my SD card and restarted the system using my flashed copy. Everything comes up except the OC client cannot connect via the https://DDNS address and I can’t access it from a browser either. I can get access to OC using the internal IP address.
I have confirmed that: 1) My WAN IP did not change, 2) My eth0 IP did not change, 3) My router is still port forwarding to the correct IP. Apache appears to be running fine. I also tried going back to my original SD card with the same results.
What else should I check?
Thanks!
And all this without any error message - very strange…
Is there any log in httpd access log?
The only error I see is on the browser where the webpage times out. I don’t see an httpd access log. I’m running Apache2 and was able to find logs at /var/log/apache2 but not sure which log to check.
I had made a few changes that perhaps had not been through a reboot, so maybe one of these did something that caused the external link to stop working.
- I had changed the hostname from raspberrypi to OwnCloud, but I think I did reboot to initiate that change. I saw this message in the /var/log/apache2/error.log:
[Sat Dec 15 11:51:56.712884 2018] [ssl:warn] [pid 694] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
which is why I thought the hostname change might have been a problem. I changed it back and it didn’t make any difference.
2) I had also installed certbot-auto prior to rebooting and did run a cert renew TEST. The test kept failing until I added “webroot /var/www/html/owncloud” to the /etc/letsencrypt/renewal/DDNS.conf file, right after the chain and fullchain parameters. Once I did that, the certbot renew test ran without any errors. I realized that webroot was different than where the test was looking (/var/www/html), but assumed that was only modifying the letsencrypt process, not the server default webroot path.
While doing all of this, I also suddenly realized the clock is off by 5 hours (I’m in CST). The pi is reporting 12:25 CST 2018 while it is actually 17:25 CST. It appears to be picking up my current time as UTC-0. I have rechecked the raspi-config and made sure the CST time zone is selected.
Suggestions?
Ok - resolved the issues! It looks like the time being off was a big hint. My Pi is ethernet connected to a Netgear Wireless Extender and I have been having weird connectivity issues with it since installing a few days ago. Once I shut it down and backleveled the firmware (I had seen posts suggesting the latest firmware was bugware), everything connected back up.
Thanks for the help and suggestions!
2 Likes