Hey guy's
Is it possible to use letsencrypt with nextcloud and omv?
Letsencrypt is installed in a docker image.
i'm not looking to access omv outside my home network , just looking to have a more secure omv.
Any help would be much appreciated.
letsencrypt with nextcloud and omv is it possible
-
- OMV 4.x
- HackitZ
-
Just install containers for Nextcloud and MariaDB and have strong passwords. You don’t need Letsencrypt if you just want LAN access.
Installation and Setup Videos - Beginning, Intermediate and Advanced
-
Yeah if you're not accessing Nextcloud outside your network, this is a pointless endeavor.
-
Then the point still stands...
If you're not trying to access OMV from outside your network (which I think is what you said)... then there's no reason to try and secure it with Letsencrypt. As long as you aren't recklessly forwarding ports in our router to OMV, your router will protect it just fine for local access only
-
If you want to access to OMV from outside safely, then use OpenVPN.
You don't have to worry about open it to the world. -
Assuming that you have letsencrypt installed properly, it is easy to install nextcloud and even get it working in your existing server. I installed mariadb and then created the database. When I installed nextcloud, I didn't use my precious port 443 or 80, but you can use something like this.
-p 3443:443 \
-p 3080:80 \I didn't use nextcloud's official build but from linuxserver\nextcloud because their builds are compatible with my raspberry pi.
Assuming that you mapped your nextcloud subdomain via letsencrypt, you can configure your nextcloud.subdomain.conf like this.
I don't know what kind of server are you running, but on my raspberry pi, I put in proxy_max_temp_file_size should be configured as 1024m; instead of 2048m for some reason. Don't forget to configure your proxy_pass to https://<yourIp>:3443 to match what you have in your nextcloud docker.
-
-p 3443:443 \
-p 3080:80 \https://<yourIp>:3443
Both options are not necessary if you connect letsencrypt and nextcloud in a docker network. Then you dont have to expose the port and dont have to change anything in the .subdomain.conf.
Exept maybe:proxy_max_temp_file_size should be configured as 1024m; instead of 2048m
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!