October 1, 20241 yr As the title says one specific computer (win11) on my network regularly cannot access unraid's webgui, any dockers or connect via SSH. PING always works. I am trying to connect via the local IPv4 address but get a 'ERR_CONNECTION_REFUSED' refused message from chrome and the equivalent message from Edge. The computer has an static IP assigned by the router and automatic DNS. I've tried the 'Network reset' option in windows but no luck. I have no problem with access from other windows computers and my android phone. Any ideas?
October 1, 20241 yr Author 51 minutes ago, Veah said: Be sure your computer is not connected as Guest network. The WiFi is set as 'private network'
October 1, 20241 yr Community Expert Try a different random IP, preferably DHCP assigned. If that works then it's a networking issue. If not, probably (not definitely) a windows/PC side issue. I've no reason to think there is anything on Unraid side. Edited October 1, 20241 yr by Veah
October 1, 20241 yr Author 1 minute ago, Veah said: Try a different random IP, preferably DHCP assigned. If that works then it's a networking issue. If not, probably (not definitely) a windows/PC side issue. I've no reason to think there is anything on Unraid side. A different IP for the windows machine or unraid?
October 1, 20241 yr Community Expert The windows machine. Don't mess with unraid at this point cause it's working for everything else I believe
October 1, 20241 yr Author 8 hours ago, Veah said: The windows machine. Don't mess with unraid at this point cause it's working for everything else I believe I removed the static I.P assignment from the router and rebooted the windows machine. It picked the same I.P anyway. I have tried manually assigning a different I.P manually on the windows machine and it still can't access the unraid webui etc..
October 2, 20241 yr Community Expert Its acting like it's on a different subnet than the server. That gets assigned either by your router/ap or on the workstation itself. Possibly port isolation ... Can you plug it into a different port on the switch/router?
October 2, 20241 yr Community Expert If connected via wifi, verify not connected to a guest network. And be sure your windows network profile set to Private not Public.
October 2, 20241 yr Community Expert Open the Settings app. Navigate to Network & Internet > Wi-Fi (or Ethernet for wired connections). Select the connected network. Click on Properties. Under Network profile, toggle the switch to change the profile from Public to Private.
October 2, 20241 yr Author Ok, the wifi was already set to private so can't try that. I have tried plugging the windows machine directly into the router and letting it pickup an I.P via DHCP but I still cannot access the unraid machine over a wired connection.
October 2, 20241 yr Community Expert What are the server and workstation IP's? I'm looking for them to be same subnet like: 192.168.1.x for both. Is that the case? If the two IPs look something like this: 192.168.2.x and 192.168.1.x you may need a firewall rule to allow traffic to pass between subnets.
October 2, 20241 yr Author 29 minutes ago, Veah said: What are the server and workstation IP's? I'm looking for them to be same subnet like: 192.168.1.x for both. Is that the case? If the two IPs look something like this: 192.168.2.x and 192.168.1.x you may need a firewall rule to allow traffic to pass between subnets. They are both on the 192.168.1.xxx subnet
October 2, 20241 yr Community Expert This sounds like a network problem. Try rebooting the router and all of the switches. If you are assigning static IP addresses, make sure that the router 'knows' about all of them. (I only assign static IP addresses to dedicated servers and printers. Everything else has to use DHCP for an address.)
October 2, 20241 yr Author I've just tried a reboot of the router and the (passive switch) but no luck. All the static I.Ps are assigned by the router, no device sets its own I.P as far I know.
October 2, 20241 yr Community Expert Let's try this. On the workstation, open a command prompt in administrator mode. Run this command to reset the tcp stack. netsh int ip reset Then try again to connect to Unraid.
October 2, 20241 yr Author 2 hours ago, Veah said: Let's try this. On the workstation, open a command prompt in administrator mode. Run this command to reset the tcp stack. netsh int ip reset Then try again to connect to Unraid. The command ran fine and I rebooted, but the issue remains.
October 2, 20241 yr Community Expert I'm running out of ideas. Can you tracert 192.168.x.x from the workstation? Even a ping?
October 3, 20241 yr Author 7 hours ago, Veah said: I'm running out of ideas. Can you tracert 192.168.x.x from the workstation? Even a ping? Ping to the server works just fine. Tracert below Tracing route to 192.168.1.222 over a maximum of 30 hops 1 2 ms 1 ms 1 ms 192.168.1.222 Trace complete.
October 3, 20241 yr Community Expert That's good they are physically connected. My very last thought is to edit your hosts file on the workstation. Tutorial info page here. And below is a copy paste from the pop-up info in Unraid under Settings>Management Access when clicking Use SSL/TLS. Hoping it can help spark an idea. Sorry I'm not more help. Best of luck. Determines how the webGUI responds to HTTP and/or HTTPS protocol on your LAN. Select No to use HTTP. To access your server use this URL: http://<server-name>.<localTLD> or this URL: http://<server-ip-address> Select Yes to enable use of an automatically-generated self-signed SSL certificate. Use this URL to access your server: https://<server-name>.<localTLD> Note that use of a self-signed SSL certificate will generate a browser warning. Select Strict to enable exclusive use of a myunraid.net SSL certificate for https access (see Provision below). Note that a DNS server must be reachable. Redirects: When accessing http://<server-ip-address> or http://<server-name>.<localTLD>, the behavior will change depending on the value of the Use SSL/TLS setting: If Use SSL/TLS is set to Strict, you will be redirected to https://<lan-ip>.<hash>.myunraid.net If Use SSL/TLS is set to Yes, you will be redirected to https://<server-ip-address> or https://<server-name>.<localTLD> If Use SSL/TLS is set to No, then the http url will load directly. Important: Strict may not be selectable if your router or upstream DNS server has DNS rebinding protection enabled. DNS rebinding protection prevents DNS from resolving a private IP network range. DNS rebinding protection is meant as a security feature on a LAN that may include legacy devices with buggy/insecure "web" interfaces. One source of DNS rebinding protection could be your ISP DNS server. In this case the problem may be solved by switching to a different DNS server such as OpenDNS where DNS rebinding proection can be turned off. More commonly, DNS rebinding protection could be enabled in your router. Most consumer routers do not implement DNS rebinding protection; but, if they do, a configuration setting should be available to turn it off. Higher end routers usually do enable DNS rebinding protection. Typically there are ways of turning it off entirely or selectively based on domain. Examples: DD-WRT: If you are using "dnsmasq" with DNS rebinding protection enabled, you can add this line to your router configuration file: rebind-domain-ok=/myunraid.net/ pfSense: If you are using pfSense internal DNS resolver service, you can add these Custom Option lines: server: private-domain: "myunraid.net" Ubiquiti USG router: you can add this configuration line: set service dns forwarding options rebind-domain-ok=/myunraid.net/ OpenDNS: Go to Settings -> Security and remove the checkbox next to "Suspicious Responses - Block internal IP addresses". It is an all-or-nothing setting. When all else fails, you may be able create an entry in your PC's hosts file to override external DNS and directly resolve your servers myunraid.net FQDN to its local IP address.
October 7, 20241 yr Author On 10/3/2024 at 11:54 AM, Veah said: That's good they are physically connected. My very last thought is to edit your hosts file on the workstation. Tutorial info page here. And below is a copy paste from the pop-up info in Unraid under Settings>Management Access when clicking Use SSL/TLS. Hoping it can help spark an idea. Sorry I'm not more help. Best of luck. Determines how the webGUI responds to HTTP and/or HTTPS protocol on your LAN. Select No to use HTTP. To access your server use this URL: http://<server-name>.<localTLD> or this URL: http://<server-ip-address> Select Yes to enable use of an automatically-generated self-signed SSL certificate. Use this URL to access your server: https://<server-name>.<localTLD> Note that use of a self-signed SSL certificate will generate a browser warning. Select Strict to enable exclusive use of a myunraid.net SSL certificate for https access (see Provision below). Note that a DNS server must be reachable. Redirects: When accessing http://<server-ip-address> or http://<server-name>.<localTLD>, the behavior will change depending on the value of the Use SSL/TLS setting: If Use SSL/TLS is set to Strict, you will be redirected to https://<lan-ip>.<hash>.myunraid.net If Use SSL/TLS is set to Yes, you will be redirected to https://<server-ip-address> or https://<server-name>.<localTLD> If Use SSL/TLS is set to No, then the http url will load directly. Important: Strict may not be selectable if your router or upstream DNS server has DNS rebinding protection enabled. DNS rebinding protection prevents DNS from resolving a private IP network range. DNS rebinding protection is meant as a security feature on a LAN that may include legacy devices with buggy/insecure "web" interfaces. One source of DNS rebinding protection could be your ISP DNS server. In this case the problem may be solved by switching to a different DNS server such as OpenDNS where DNS rebinding proection can be turned off. More commonly, DNS rebinding protection could be enabled in your router. Most consumer routers do not implement DNS rebinding protection; but, if they do, a configuration setting should be available to turn it off. Higher end routers usually do enable DNS rebinding protection. Typically there are ways of turning it off entirely or selectively based on domain. Examples: DD-WRT: If you are using "dnsmasq" with DNS rebinding protection enabled, you can add this line to your router configuration file: rebind-domain-ok=/myunraid.net/ pfSense: If you are using pfSense internal DNS resolver service, you can add these Custom Option lines: server: private-domain: "myunraid.net" Ubiquiti USG router: you can add this configuration line: set service dns forwarding options rebind-domain-ok=/myunraid.net/ OpenDNS: Go to Settings -> Security and remove the checkbox next to "Suspicious Responses - Block internal IP addresses". It is an all-or-nothing setting. When all else fails, you may be able create an entry in your PC's hosts file to override external DNS and directly resolve your servers myunraid.net FQDN to its local IP address. Thanks I had tried taking everything out of the hosts file so no luck there. As non of my docker UIs are accessible either it wouldn't seem to be something wrong in the unraid UI settings and has to be an issue with the windows computer. Ironically enough it all started working as I was trying this and then 10 minutes stopped working again. Infuriating! Thanks again for trying to help.
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.