I have set up the letsencrypt docker to correctly forward to several other containers, ie nextcloud, sonarr etc.
Though how can I forward to the omv web interface
Thanks for any help!
I have set up the letsencrypt docker to correctly forward to several other containers, ie nextcloud, sonarr etc.
Though how can I forward to the omv web interface
Thanks for any help!
you need to change OMV default port and use like other container
eg: if you configure OMV to use ports 81 and 444 you need to type : http://yourNASIP:81
and use this URL in omv.conf file
Hi there!
Accessing OMV locally isn't an issue, what I'm trying to do is access externally via my domain. Let me explain more clearly.
I currently have ports 80 and 443 forwarded to the letsencrypt docker then configured the reverse proxy to forward any subdomains to certain services like nextcloud.mydomain.com
Ideally, I would like the subdomain "omv.mydomain.com" to point to OMV.
Im sure its a matter of configuring one of the nginx/proxy-conf files.
I Loosely followed this tutorial by techno dad life
https://www.youtube.com/watch?v=TkjAcp8q0W0
Thanks!
Thank you!!
That is exactly what I was looking for. I just didn't know what lines to change.
One more thing if it's not too much trouble,
How did you share the certificate with omv web for ssl
basically what omv directory do I need to map to the docker.
or do I even need to do this?
Thanks!
you do not need certificate in OMV because if access from wan the cert use is the letsencrypt cert.
but you allways can copy by hand the letsencrypt cert and copy it to OMV webGUI , but is only usefull to use https en LAN and because your cert is in the way "omv.mydomain.com",your browser says that is not for your machine if you try to access OMV in the "192.168.1.x" way.
Sweet! Thanks for the help!
Alles anzeigenyou need to change OMV default port and use like other container
eg: if you configure OMV to use ports 81 and 444 you need to type : http://yourNASIP:81
and use this URL in omv.conf file
First of, sorry for the "hijack".
I have a working docker letsencrypt https setup with my own domain for some docker container with services as Nextcloud, Sabnzbd etc. Now I want to be able to access my omv webgui remotely using my domain (omv.mydomain.com). I've used your omv conf file and replaced the IP address to my local omv address and changed the letsencrypt docker container (added the omv subdomain).
Probably a NooB question but how do I change the ports of the omv webgui so it's gonna work with my docker letsencrypt setup? I've tried the portchange in the general settings option but there I need a generated SSL certificate.
Thanks in advance
Gr Maart
why do you need to change the port? It should work just like that...
Alles anzeigenFirst of, sorry for the "hijack".
I have a working docker letsencrypt https setup with my own domain for some docker container with services as Nextcloud, Sabnzbd etc. Now I want to be able to access my omv webgui remotely using my domain (omv.mydomain.com). I've used your omv conf file and replaced the IP address to my local omv address and changed the letsencrypt docker container (added the omv subdomain).
Probably a NooB question but how do I change the ports of the omv webgui so it's gonna work with my docker letsencrypt setup? I've tried the portchange in the general settings option but there I need a generated SSL certificate.
Thanks in advance
Gr Maart
change only port 80 to 81 or semeone free and use like other container
Thnx for the replies!
I'm just not able to get it up and running through the letsencrypt reverse proxy docker (like nextcloud and the other containers). I've tried to change ports but no success. My omv.subdomain.conf (based on the .conf file from @raulfg3 that I've put in the proxy-conf directory)
# make sure that your dns has a cname set for omv and that your omv container is not using a base url
server {
listen 443 ssl;
server_name omv.*;
include /config/nginx/ssl.conf;
client_max_body_size 0;
# enable for ldap auth, fill in ldap details in ldap.conf
#include /config/nginx/ldap.conf;
location / {
# enable the next two lines for http auth
#auth_basic "Restricted";
#auth_basic_user_file /config/nginx/.htpasswd;
# enable the next two lines for ldap auth
#auth_request /auth;
#error_page 401 =200 /login;
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_omv omv;
proxy_pass https://192.168.178.25:443;
}
}
Alles anzeigen
I've tried other ports as well (line 27), and forwarded them in my router and I also restarted the letsencrypt docker after changing the ports. I do have my openmediavault setup with a domain name:
Maybe that has something to do with it?
In the end I was able to get my omv.domain.com accessible by creating a letsencrypt certificate using the openmediavault-letsencrypt plugin, enable SSL on 443 in the general settings with this certificate and forwarding a port in my router (445->443) so I have to add https://omv.domain.com:445 to access the webgui not a huge problem of course but I'd rather use the reverse proxy. Maybe you guys have any ideas on what I'm doing wrong?
gr Maart
in line 27. try
proxy_pass http://192.168.178.25:80; (if insert http-port of omv)
you can add this in the .conf file of nginx. But you would have to turn on the listening of nginx in port 80, which is turned off by default. Why do you need this?
When I'm trying to access my nextcloud docker subdomain I explicitly have to add https. When I access my omv subdomain I can just simply use omv.domain.com and this redirects automaticly to the https domain. Like I've mentioned before this isn't a big problem, I just wanted to know why this is and, if possible, how to change this so I can access nextcloud.domain.com without having to add https.
does your config.php in config/www/nextcloud/config/ has the line 'overwriteprotocol' => 'https',?
Yes, this is the file (masked):
<?php
$CONFIG = array (
'memcache.local' => '\\OC\\Memcache\\APCu',
'datadirectory' => '/data',
'instanceid' => '',
'passwordsalt' => '',
'secret' => '' =>
'trusted_domains' =>
array (
0 => '192.168.178.25:444',
1 => 'nextcloud.domain.com',
),
'overwrite.cli.url' => 'https://nextcloud.domain.com',
'overwritehost' => 'nextcloud.domain.com',
'overwriteprotocol' => 'https',
'dbtype' => 'mysql',
'version' => '16.0.1.1',
'dbname' => 'nextcloud',
'dbhost' => '192.168.178.25:3306',
'dbport' => '',
'dbtableprefix' => 'oc_',
'mysql.utf8mb4' => true,
'dbuser' => '...',
'dbpassword' => '',
'installed' => true,
);
Alles anzeigen
Looks good. For me it works without typing https. What message do you get, when you try without?
Attached a screenshot of the message. I've tried it from different endpoints, browsers and connections, so that firewall/proxy message does not refer to my home network setup.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!