Letsencrypt and Nextcloud

Zitat von monsen

Thank you for bringing this up. That exactly solved my problem of changing the nextcloud port to a custom port.

Maybe i should mention here a bit more precisely how to do it:

1. Add this to your config.php of nextcloud:

Code

'overwritehost' => 'yourDynHost:444',

Where 444 is the port of your letsencrypt docker for https. In the original howto this port is where you forward your traffic from external access on 443 to

(443 -> 444).

2. Add a rule in your router config to forward 444 external (WAN) to 444 internal (LAN).

Of course you do not need the 443 to 444 rule anymore afterwards.

This is how i got it running here now.

Alles anzeigen

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

According to the OMV 4.x docks (which respectively appear identical to 5.x):

Zitat

LetsEncrypt

Lets Encrypt certificates can be imported directly, just locate your /etc/letsencrypt/live/<mydomain.com>/<em>fullchain,privkey</em>.pem files and copy their contents in their respective field. No need to convert.

Couldn't you just create the certs with docker (or the shell preferably) and put them in the above? I'm brand new to docker and the linuxserver/letsencrypt container is awesome, but you don't have to use it. This will explain how to generate a cert on your OMV box independently without docker: https://certbot.eff.org/instructions. However, I'm not sure about letting it autoconfig your nginx or whatever OMV runs, but still you can generate the keys without doing that, it's pretty basic *AND* if even I can do it on a desktop... :-).

BTW, I completely understand why you're doing this and will be doing this _VERY_ soon. I'm learning to use Docker Swarm and to my beginner eyes, it seems easier this way with multiple remote OMV boxes from the remote maintenance side of things. In fact, I'm having a hard time seeing why you'd want the Docker container to have the certs while leaving OMV without them, but again I'm new.

But otherwise, wouldn't this simply be monson's quote up there with -p 443:444 or without that directive just -p 444:443? Maybe the reasoning you need to change ports would help suggestions.

Why do you want to install letsencrypt docker when you generate the certificates elsewhere and also don’t seem to intend to use the inbuilt reverse proxy?

Unless its a wildcard cert, or explicity for your nextcloud subdomain that won't work.

PS: Wildcard certs only work via DNS Challenge.

Greetings

David

If its the same domain name it could work just fine.

Greetings

David