Hi,
This worked fine on OMV 2.1 but since I moved to 3.0, this doesn't work.
Does anyone have a solution?
Thanks and merry Christmas!
Hi,
This worked fine on OMV 2.1 but since I moved to 3.0, this doesn't work.
Does anyone have a solution?
Thanks and merry Christmas!
What worked? Are you using the nginx plugin?
What worked? Are you using the nginx plugin?
I was able to re-route subdomains to specific ports. As subzero79 explained in the guide.
I did this without a plugin in Stone Burner but since I re-installed OMV and used Erasmus instead, this method no longer works, even though the nginx.conf includes /etc/nginx/sites-enabled/* and I have a multi_host file in that folder.
different version of nginx. some things have changed slightly @subzero79 can probably help you again
I think the problem now ngnix loads in order. So first should be omv default config, then use your file. So maybe change the first letter to z of your ngnix configuration.
I think the problem now ngnix loads in order. So first should be omv default config, then use your file. So maybe change the first letter to z of your ngnix configuration.
I have a file called openmediavault-something in te sites-enabled folder but no default. Which nginx-configuration should I rename? /etc/nginx/nginx.conf?
no, the ones at /etc/nginx/sites-enabled/
no, the ones at /etc/nginx/sites-enabled/
Sorry, still doesn't work.
I've tried manually including the multi_host file in nginx.conf. I've tried changing the name of multi_host to zmulti_host.
Nothing seem to do the trick. Are you using OMV 2.1 or 3.0 yourself?
EDIT 1: I just noticed that when I try to change the webGUI port, the new port works (88) but 80 still work as well.
Tried setting it to 80 and 88 through OMV-firstaid and the port I specify show up in the webGUI but 80 always work either way.
EDIT 2: my /etc/nginx/sites-enabled/openmediavault-webgui file listened on port 80 while the same file in sites-available was listening to whatever I specified in the webGUI config page (General Settings) or OMV-firstaid.
I'm not sure if I've messed with a symlink during first day of setup, but I managed to get a grip on the listening port by symlinking from sites-available/openmediavault-webgui to sites-enabled/openmediavault-webgui, which then resolves that issue.
However, no luck with proxy_pass and the multi_host file.
EDIT 3: Resolved by editing openmediavault-webgui. Swapped listen 80; to listen [::]:80 default_server ipv6only=off; which I fortunately found in the old multi_host backup where I "accidentally" backed up the whole folder.
Merry Christmas!
Maybe I need to review the guide for omv3.0. I'll test that out
Sorry i forgot that i had this issue, it came to me when i changed a setting in omv general settings in nginx, there was a commit in dec 2015 about the default server, when i applied the change all my local domains went down (almost a year after the commit). I solved this by adding one extra listen line in each block, so every host should have
You can return to your default omv nginx by using omv-mkconf nginx then restart the service
Sorry i forgot that i had this issue, it came to me when i changed a setting in omv general settings in nginx, there was a commit in dec 2015 about the default server, when i applied the change all my local domains went down (almost a year after the commit). I solved this by adding one extra listen line in each block, so every host should have
You can return to your default omv nginx by using omv-mkconf nginx then restart the service
I just noticed that the listening port change each time I edit a setting in the webGUI that change anything with NGINX. The new line gets deleted.
Thanks!
That's expected behavior of Omv. Not sure if is working for you now?
That's expected behavior of Omv. Not sure if is working for you now?
It does. I have to manually change it each time I fiddle with LetsEncrypt tho.
I have to manually change it each time I fiddle with LetsEncrypt tho
Why would you have to do that? openmediavault-webui server block is to be left there, you can add your own nginx separate file for a different web page.
Why would you have to do that? openmediavault-webui server block is to be left there, you can add your own nginx separate file for a different web page.
You mean I can add a separate file from openmediavault-webui and make it listen to [::]:80 and it will not interfere with the OMV webGUI?
Of course. That's the idea of the guide. I've never mentioned in the guide to change the listening port in Omv.
will this be correct :
{
listen 80;
listen [::]:80;
location /tvheadend {
return 301 https://$host:9981/;
}
}
Try it and report back. The guide is for domain not URL. I believe URL proxy pass need to be at openmediavault-webui.d/ folder
Alles anzeigenwill this be correct :
{
listen 80;
listen [::]:80;
location /tvheadend {
return 301 https://$host:9981/;
}
}
i tested this. didn´t work
I created a new document which is tvheadend.conf in /etc/nginx/openmediavault-webgui.d/
if I use the lines with port 80 i get an error by nginx that listening twice on port 80 isn´t okay.
If I only use
location /tvheadend {
return 301 https://$host:9981/;
}
I get error: net:ERR_Connection_Closed (the website couldn´t be loaded)
Hey guys.. I still work on this problem and I still have no solution..
In sites-enabled I have the openmediavault-webgui.conf (for sure) and the zzz-omv.conf for Letsencrypt.
so everything goes to https://
I´m still not be able to have access to my TVserver which runs on port 9981.
I always get an 404 error..
It drives me crazy..
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!