Jump to content

Update from 6.12.0 RC6 to 6.120 or 6.12.1 no webgui nginx duplicate entries


Go to solution Solved by exico,

Recommended Posts

I searched but i did not see this problem in another "no webgui" thread.

 

I upgraded from the RC6 to 6.12.0 stable and also tried 6.12.1 but i had to revert on both occasions.

I attached the diagnostics but from what i see:

 

Tried to:
 

 /etc/rc.d/rc.nginx check
 Checking configuration for correct syntax and
then trying to open files referenced in configuration...
nginx: [emerg] a duplicate default server for 192.168.80.105:80 in /etc/nginx/conf.d/servers.conf:43
nginx: configuration file /etc/nginx/nginx.conf test failed

I then checked servers.conf and indeed there are various entries duplicated on my eth3. I tried to comment them and check again, some warnings but no [emerg]. Tried to start and these entries reappear and stop nginx.

For example:

server {
    listen 192.168.80.105:80 default_server; # eth3
    return 302 https://192-168-80-105.c8100b769f7ebe9a046d3c97b75b083b26c4ca45.myunraid.net:443$request_uri;
}
server {
    listen 192.168.80.105:80 default_server; # eth3
    return 302 https://192-168-80-105.c8100b769f7ebe9a046d3c97b75b083b26c4ca45.myunraid.net:443$request_uri;
}
somethingsomething

server {
somethingsomething
    listen 192.168.80.105:443 ssl http2 default_server; # eth3
    listen 192.168.80.105:443 ssl http2 default_server; # eth3
somethingsomething
}

(somethingsomething is just a placeholder for the other config text, just wanted to highligh the duplicated entries)

And there are more.

 

For now i reverted to the RC

 

Since the eth3 is integrated in the MB i cannot even remove it to try if it fix itself, also there is no option in the BIOS to disable it

MB is a supermicro X9SRL-F

unraidsrv-diagnostics-20230623-2116.zip

Edited by exico
typo in the title
Link to comment
  • exico changed the title to Update from 6.12.0 RC6 to 6.120 or 6.12.1 no webgui nginx duplicate entries
  • Solution

Found the problem, I had two interfaces with the same IP but I do not understand why the rc script bind the same ip twice on one interface.

 

I think that a check should be in place for that.

 

Bear in mind that I had one interface disabled

 

I removed the IP from both interfaces and the upgrade has gone smooth

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...