Nextcloud = 1.20.1
OS = Debian GNU/Linux 10 (buster)
Arch = 5.4.6-sunxi arm71
Hardware = Banana Pi M1
I encountered a bug, a configuration problem or a documentation leak.
After installed nextcloud with the proper image provided by nextcloudpi I setted up console, drives and maschine name via ssh on console.
After rebooting the pi, it comes up, using the proper settings. In the next step I tried to set up nextcloud as described in the HOW-TO.
Even on the first start nextcloud via https://“mypiname.local” wasn’t accessable.
The admin interface was accessable at port 4443, but it seems to be without function.
So I configured via ssh and ncp-config.
After setting up nextcloud proper with ncp-config the access error via https still persists.
As a workaround I did ncp-config / networking / dnsforwarding and in additional ncp-config / networking / nc-forward-ports. After these steps my nextcloud became accessable via https://“mypiname.myddnsprovider”, but NOT via https://“mypiname.local”.
The next morning my nextcloud wasn’t accessable via browser at all. My internet provider is changing my ip in the early morning, and I thought my DDNS provider wasn’t informed by my router. So I checked my record, figuring out that my router works fine, updating my DDNS record after having a new ip address from my provider. Next step was to check out my router, but there where still the proper port forwardings active.
For quick solution I did ncp-config / networking / nc-forward-ports, and after that at least nextcloud was accessable via https://“mypiname.myddnsprovider”.
Next day, the same problem occured again. So decided to investigate a little more and basicly I found out, that the problem is caused renaming my pi to “mypiname”.
In /var/www/nextcloud/config/config.php in trusted domains the records 5, 7 and 8 still had the values nextcloudpi, nextcloudpi.local, nextcloudpi.lan but in my understanding there should be the values “mypiname”, “mypiname.local” and “mypiname.lan”.
After changing the records to “mypiname” and restarting, everything works fine now.
Normaly I shouldn’t edit config.php myself. I suggested that nextcloud put the machine name in the proper places by itself. Or did I “forgot” to tell nextcloud to do so, and how can I do this?
Otherways it might be a bug or, if renaming of a machine is not supported, a hint in the documentation would be usefull for newbies like me.
Thank’s a lot for reading. Would be nice, if this problem and its workaround and proper solve would be documented somewhere.