moosedookie Posted June 16, 2023 Share Posted June 16, 2023 Hello, I recently upgraded from v6.11.5 to v6.12.0 and am now unable to connect to the webUI from other systems. If I boot unraid in GUI mode it can access the UI from the unraid server but not from other systems. I get "This site can't be reached" "ERR_CONNECTION_REFUSED" in chrome and just get "Unable to connect" in Firefox. I decided to use the unraid connect port check to see if it can connect but get "The Unraid server is unreachable from outside your network.". I've also noticed that I am no longer able to access anything over SMB anymore since the update. I'm not sure what is going on, any help would be appreciated. Thanks. moose-server-diagnostics-20230616-0016.zip Quote Link to comment
JorgeB Posted June 16, 2023 Share Posted June 16, 2023 Try booting in safe mode to rule out any plugin issues. Quote Link to comment
Mario Jutras Posted June 16, 2023 Share Posted June 16, 2023 Same problem! I will need a simple solution Quote Link to comment
Mario Jutras Posted June 16, 2023 Share Posted June 16, 2023 Unable to boot in GUI mode from the server:( Quote Link to comment
DovahDovolom Posted June 16, 2023 Share Posted June 16, 2023 I'm also having an issue accessing the webGUI. Have already tried safe mode and safe mode with gui to see if i could still access with localhost. Was unable to on both those occasions. Any help will is appreciated. Quote Link to comment
JorgeB Posted June 16, 2023 Share Posted June 16, 2023 Since this is not resolved for the OP please start your own thread and post the diagnostics, or it can get confusing. Quote Link to comment
soduah62 Posted June 16, 2023 Share Posted June 16, 2023 How do you even do the diagnostics if you cannot get to the Gui?? Quote Link to comment
JorgeB Posted June 16, 2023 Share Posted June 16, 2023 13 minutes ago, soduah62 said: How do you even do the diagnostics if you cannot get to the Gui?? Click on the link and you'll see. Quote Link to comment
itimpi Posted June 16, 2023 Share Posted June 16, 2023 13 minutes ago, soduah62 said: How do you even do the diagnostics if you cannot get to the Gui?? Can you boot in non-GUI mode to get a console login prompt? If so you can use the ‘diagnostics’ command from the command line. Quote Link to comment
soduah62 Posted June 16, 2023 Share Posted June 16, 2023 What link? I don't see any link on your post. Quote Link to comment
JorgeB Posted June 16, 2023 Share Posted June 16, 2023 3 minutes ago, soduah62 said: What link? There's a link every time the word diagnostics is typed, there's also one in your post. Quote Link to comment
soduah62 Posted June 16, 2023 Share Posted June 16, 2023 Got it, my apologies. I am new to this unRaid thing. Now, to get to the Linux command line, the server should be connected to a monitor. I was running mine headless after installing running unRaid. 1 Quote Link to comment
soduah62 Posted June 16, 2023 Share Posted June 16, 2023 16 minutes ago, itimpi said: Can you boot in non-GUI mode to get a console login prompt? If so you can use the ‘diagnostics’ command from the command line. That will require connecting the server to a monitor, mine was running headless since I began using it Quote Link to comment
soduah62 Posted June 16, 2023 Share Posted June 16, 2023 By the way, I forgot to mention that I can see the server on Windows Network but cannot access it. Quote Link to comment
moosedookie Posted June 16, 2023 Author Share Posted June 16, 2023 9 hours ago, JorgeB said: Try booting in safe mode to rule out any plugin issues. Thanks for the quick reply! When I first tried to boot into GUI safe mode I was just getting a black screen with a flashing cursor in the top left corner. I uninstalled the nvidia driver and rebooted to GUI safe mode and was able to login but I am still having the same issue... Quote Link to comment
JorgeB Posted June 16, 2023 Share Posted June 16, 2023 Try booting with a new flash drive using a stock v6.12.0 install, no key needed, just to confirm if the problem is config related. Quote Link to comment
Olegs Posted June 16, 2023 Share Posted June 16, 2023 My GUI was not loading as well. Not sure if you're issue is related, but this is what I had: ssh to the server, and tried starting nginx, and saw that 445 is used. root@node202:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... Message from syslogd@node202 at Jun 16 21:44:53 ... nginx: 2023/06/16 21:44:53 [emerg] 14086#14086: bind() to 127.0.0.1:445 failed (98: Address already in use) I stopped docker containers root@node202:~# /etc/rc.d/rc.docker stop stopping dockerd ... Cleaning up old /var/run/dockerd.pid. but that did not help, 445 still used. I checked for open ports, and samba was using that root@node202:~# netstat -ltnp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 6136/wsdd2 tcp 0 0 192.168.88.101:445 0.0.0.0:* LISTEN 6121/smbd So I stopped samba and started nginx. It went fine this time. root@node202:~# /etc/rc.d/rc.samba stop root@node202:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... I can see that nginx is using 445 port now tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 5824/nginx: master If I disable Samba - unraid reboots ok and gui starts, if it's enabled - after reboot web gui does not boot. Quote Link to comment
ljm42 Posted June 16, 2023 Share Posted June 16, 2023 1 hour ago, Olegs said: My GUI was not loading as well. Not sure if you're issue is related, but this is what I had: ssh to the server, and tried starting nginx, and saw that 445 is used. root@node202:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... Message from syslogd@node202 at Jun 16 21:44:53 ... nginx: 2023/06/16 21:44:53 [emerg] 14086#14086: bind() to 127.0.0.1:445 failed (98: Address already in use) I stopped docker containers root@node202:~# /etc/rc.d/rc.docker stop stopping dockerd ... Cleaning up old /var/run/dockerd.pid. but that did not help, 445 still used. I checked for open ports, and samba was using that root@node202:~# netstat -ltnp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:3702 0.0.0.0:* LISTEN 6136/wsdd2 tcp 0 0 192.168.88.101:445 0.0.0.0:* LISTEN 6121/smbd So I stopped samba and started nginx. It went fine this time. root@node202:~# /etc/rc.d/rc.samba stop root@node202:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... I can see that nginx is using 445 port now tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 5824/nginx: master If I disable Samba - unraid reboots ok and gui starts, if it's enabled - after reboot web gui does not boot. Please see my comment here, the webgui cannot run on port 445 https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/#comment-1271735 1 Quote Link to comment
ljm42 Posted June 16, 2023 Share Posted June 16, 2023 14 hours ago, moosedookie said: Hello, I recently upgraded from v6.11.5 to v6.12.0 and am now unable to connect to the webUI from other systems. If I boot unraid in GUI mode it can access the UI from the unraid server but not from other systems. I get "This site can't be reached" "ERR_CONNECTION_REFUSED" in chrome and just get "Unable to connect" in Firefox. I decided to use the unraid connect port check to see if it can connect but get "The Unraid server is unreachable from outside your network.". I've also noticed that I am no longer able to access anything over SMB anymore since the update. I'm not sure what is going on, any help would be appreciated. Thanks. Thanks for the diagnostics. Please open a web terminal SSH to the server, or connect a keyboard and monitor and run this, then copy/paste the results back here: cat /etc/nginx/conf.d/servers.conf 1 Quote Link to comment
ljm42 Posted June 16, 2023 Share Posted June 16, 2023 2 hours ago, soduah62 said: That will require connecting the server to a monitor, mine was running headless since I began using it Right. If the web server isn't running then you either need to connect a keyboard/monitor to the system, or you can use SSH (if you previously enabled that on Settings -> Management Access). Either of those methods will give you command line access to the server, where you can run "diagnostics" Quote Link to comment
moosedookie Posted June 16, 2023 Author Share Posted June 16, 2023 2 hours ago, JorgeB said: Try booting with a new flash drive using a stock v6.12.0 install, no key needed, just to confirm if the problem is config related. I put a clean install on a new flash drive and booted up but I am still having the same issue... No connection. Quote Link to comment
moosedookie Posted June 16, 2023 Author Share Posted June 16, 2023 2 hours ago, ljm42 said: Thanks for the diagnostics. Please open a web terminal SSH to the server, or connect a keyboard and monitor and run this, then copy/paste the results back here: cat /etc/nginx/conf.d/servers.conf root@MOOSE-SERVER:~# cat /etc/nginx/conf.d/servers.conf # # Listen on local socket for nchan publishers # server { listen unix:/var/run/nginx.socket default_server; location ~ /pub/(.*)$ { nchan_publisher; nchan_channel_id "$1"; nchan_message_buffer_length $arg_buffer_length; } location ~ /nchan_stub_status$ { nchan_stub_status; } } # # Always accept http requests from localhost # ex: http://localhost # ex: http://127.0.0.1 # ex: http://[::1] # server { listen 127.0.0.1:80; # lo listen 127.0.0.1:14443; # lo listen [::1]:80; # lo listen [::1]:14443; # lo # include /etc/nginx/conf.d/locations.conf; } # # Redirect http requests to https # ex: http://tower.local -> https://lan-ip.hash.myunraid.net # ex: http://192.168.1.100 -> https://lan-ip.hash.myunraid.net # server { listen 10.253.0.1:80 default_server; # wg0 return 302 https://10-253-0-1.hash.myunraid.net:14443$request_uri; } # # Redirect http requests to https # ex: http://[::ffff:192.168.1.100] -> https://lan-ip.hash.myunraid.net # # # Return 404 (Not Found) as default ssl action, using self-signed cert # server { listen 10.253.0.1:14443 ssl http2 default_server; # wg0 # Ok to use concatenated pem files; nginx will do the right thing. ssl_certificate /boot/config/ssl/certs/MOOSE-SERVER_unraid_bundle.pem; ssl_certificate_key /boot/config/ssl/certs/MOOSE-SERVER_unraid_bundle.pem; ssl_trusted_certificate /boot/config/ssl/certs/MOOSE-SERVER_unraid_bundle.pem; # # OCSP stapling ssl_stapling off; ssl_stapling_verify off; return 404; } # # Port settings for https using CA-signed cert # ex: https://lan-ip.hash.myunraid.net # ex: https://hash.unraid.net # server { listen 10.253.0.1:14443 ssl http2; # wg0 server_name 192-168-33-134.hash.myunraid.net 2600-6c40-2d7f-7cc0-215-17ff-fee8-934c.hash.myunraid.net [wanip].hash.myunraid.net 2600-6c40-2d7f-7cc0-215-17ff-fee8-934c.hash.myunraid.net 10-253-0-1.hash.myunraid.net; # Ok to use concatenated pem files; nginx will do the right thing. ssl_certificate /boot/config/ssl/certs/certificate_bundle.pem; ssl_certificate_key /boot/config/ssl/certs/certificate_bundle.pem; ssl_trusted_certificate /boot/config/ssl/certs/certificate_bundle.pem; # # OCSP stapling ssl_stapling on; ssl_stapling_verify on; # location ~ /wsproxy/14443/ { return 403; } include /etc/nginx/conf.d/locations.conf; } Quote Link to comment
ljm42 Posted June 16, 2023 Share Posted June 16, 2023 @moosedookie at a terminal window, what do you get when you type: /etc/rc.d/rc.nginx status 1 Quote Link to comment
moosedookie Posted June 16, 2023 Author Share Posted June 16, 2023 28 minutes ago, ljm42 said: @moosedookie at a terminal window, what do you get when you type: /etc/rc.d/rc.nginx status It says "Nginx is running". 1 Quote Link to comment
ljm42 Posted June 16, 2023 Share Posted June 16, 2023 OK I see the issue @moosedookie. The nginx config is listening on wg0 but not br0: listen 10.253.0.1:14443 ssl http2; # wg0 It should be listening on both, like this: listen 192.168.33.134:14443 ssl http2; # br0 listen 10.253.10.1:14443 ssl http2; # wg0 we are looking for the cause 1 Quote Link to comment
Recommended Posts
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.