Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

I meant only to remove the port forwards from the nextcloud container. The letsencrypt container needs a least port 443 open. But 444:443 is already a non standart port. Port 80 needs only to be open when renewing the certs.

I had already deleted the nextcloud port forwarding. But that did not help to enable nextcloud access on a custom port and i honestly dont see how it could.

Maybe I just dont understand what you want to do. With letsencrypt set up you usually access nextcloud through letsencrypt's reverse proxy.

Additionally you want to access nextcloud in your LAN on another port than 443? If yes, just bind nextclouds 443 port to another port like -p 4567:443.

Zitat von Morlan

Maybe I just dont understand what you want to do. With letsencrypt set up you usually access nextcloud through letsencrypt's reverse proxy.

Maybe, maybe not. I am most likely not able to properly explain what i want

I just want to move nextcloud from 443 to another port so it is not that obvious when accessing from the WAN. I dont care that much about LAN. it can stay on port 443 or use the same as WAN. Doesnt matter.

Zitat von Morlan

Additionally you want to access nextcloud in your LAN on another port than 443? If yes, just bind nextclouds 443 port to another port like -p 4567:443.

Ok, if it is that easy. I will try....

From WAN side just forward another port to your letsencrypt container.

I got Nextcloud up and running as shown in the tutorial. But I ran into a database issue that is most likely a utf8 4 byte issue but I am unable to correct it.

Doctrine\DBAL\Exception\DriverException: An exception occurred while executing 'SELECT * FROM `oc_comments` WHERE (`message` COLLATE utf8mb4_general_ci LIKE ?) AND (`object_type` = ?) ORDER BY `creation_timestamp` DESC, `id` DESC LIMIT 100' with params ["%%", "files"]: SQLSTATE[42000]: Syntax error or access violation: 1253 COLLATION 'utf8mb4_general_ci' is not valid for CHARACTER SET 'utf8'

I tried to login into the mysql database with this commands

$ sudo mysql -u root -p

MariaDB [(none)]> use nextcloud;

MariaDB [nextcloud]> set global innodb_large_prefix=on;

MariaDB [nextcloud]> set global innodb_file_format=Barracuda;

$ sudo -u www-data php occ maintenance:repair

But once I am on the first innodb_large_prefix=on" command it says

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'set_global innodb_large_prefix=on' at line 1

Due to that I am unable to list / edit the users in the nextcloud backend and of course more.

Any hints would be very much appreciated

Zitat von Morlan

From WAN side just forward another port to your letsencrypt container.

I tried that and it did not work. I think that is because of ngninx rewrite rules?

Zitat von Morlan

Maybe I just dont understand what you want to do. With letsencrypt set up you usually access nextcloud through letsencrypt's reverse proxy.

Additionally you want to access nextcloud in your LAN on another port than 443? If yes, just bind nextclouds 443 port to another port like -p 4567:443.

Also tried that. None of your suggested way forward for chaning ports worked for me, sadly

Zitat von Morlan

From WAN side just forward another port to your letsencrypt container.

Okay, maybe this doesn't work.

Anyone got Redis running with this setup?

Zitat von bunducafe

I got Nextcloud up and running as shown in the tutorial. But I ran into a database issue that is most likely a utf8 4 byte issue but I am unable to correct it. (...)

Interesting that so far nobody appears to have had the same issues. Since then I was unable to get the inno_db scheme to be updated from Antelope to Barracuda... I am not entirely sure why the changes I've made in MariaDB do not hold... I might give NextcloudPi a try.

monsen: Redis runs like a charm: see here

Zitat von riff-raff

monsen: Redis runs like a charm: see here

Thanks i will give it a try

I've finally installed NextcloudPi.
It seems to work better on my RockPro64.

Zitat von aldrick

I've finally installed NextcloudPi.
It seems to work better on my RockPro64.

I did the same on the Odroid HC1. It has been flawless so far and no fatal errors in the logs.

Anyone managed to get access to nextcloud through it's LAN IP?

I can use it fine through the WAN domain but using the LAN IP.

I added the local IP to the 'trusted_domains' in config.php but that is not enough.

When accessing trough "https://<nextcloud_local_IP>:444/nextcloud" i get redirected to "https://<nextcloud_local_IP>/nextcloud" and then get a 404 error there.

I guess some settings within in the proxy have to be adjusted as well?

did you use the internal IP of your host?

i can reach my cloud with its internal IP, but certificate is not valid for this "domain".

why would you do this anyways?

Yes that is what i did.

Why would i go through WAN when being on the same LAN?

Depends on your internet connection

I do not use the webinterface, but sync-clients with different plattforms. Using an internal IP would cut clients mobility and flexibility for the use of other networks.

I am not saying i want to move to sole LAN IP. It should be possible to access it through different IPs/hosts. I just miss the correct configuration.