mattastrophe

After poking and prodding at squid on the router and restarting the unraid box, things seem to be cooperating. I am disappointed because I still don't exactly understand what happened or how to reliably reproduce this issue, but I will consider this resolved for now. I will edit or reply later if I can reproduce it and/or come up with more info in the future in case this happens to anyone else with the same odd configuration. Most likely, though, it was the result of something silly I did, as I had more or less assumed in my original post. Regardless, thanks for the quick response, @trurl!

Disabling the proxy and reverse proxy on the router now allows for me to access the router by its DNS entry, but trying to access any other device or server while the unraid server is off returns this from a page displayed by pfSense: Potential DNS Rebind attack detected, see http://en.wikipedia.org/wiki/DNS_rebinding Try accessing the router by IP address instead of by hostname. I will also check on the pfSense forums now that this seems to potentially related to pfSense and squid, but still don't know why this only started after adding unraid to the mix.

It is a fairly fresh install of unraid (a few days old with the only major changes being that I set up some docker containers, but those got turned off). However, when I turned off the server, I am seeing my reverse proxy server from pfSense (which I had forgotten about) say in the browser when trying to visit wap.myhome.net that: The following error was encountered while trying to retrieve the URL: http://wap.myhome.net/ Connection to 192.168.10.70 failed. The system returned: (60) Operation timed out The remote host or network may be down. Please try the request again. Your cache administrator is N/A. where the IP address shown is for the unraid server, and is NOT the correct IP in the DNS entry for the server at the url above. So then it seems that somehow squid is deciding to send all local http and https traffic to the unraid server...? This seems like I need to look more into what's going on with squid now, but definitely still appreciate any pointers or info if there is something I should be specifically checking or adjusting. Thanks for the response! edit: The above error is the same for any other site on my domain but shows the exact same IP (.70) with whatever URL I had typed but I used that as an example. So for wap it should be .5, wap2 should be .6, etc...

Hello, As the title describes, if I try to visit a local website (such as the page for my router, any of my WAPs, or server on another machine) using the local DNS entry, it always shows the login page for unraid instead, now that I have setup unraid and put it on my network. Following is some more info, as well as what I tried after looking through any forum posts that seemed remotely related: First, I would like to say that I am new to unraid (this is also my first post!). I have used freenas and truenas in the past, so this seems like a fairly straightforward transition for the most part, with a few small hiccups I have already tackled or am still working through, this being one of them. I currently am using PfSense for my router, and this is also running DNS, DHCP, and some other services for my local network. I have DNS entries for most or all of the systems on my network that have webUI's. It used to be that typing the address in the browser would pull up their page. Now, all addresses on my subdomain, even ones without actual DNS entries, show the unraid page. To protect the identities of the innocent, I have changed the names of the domain and each server for this post, but examples are as follows: router.myhome.net, wap.myhome.net, tower.myhome.net, as well as tower.local all go to the unraid webUI in the browser. Nslookup, however, shows the correct IP for all of these entries, and putting the IP address in the browser also goes to the correct page. Also of note is that if I go to doesnotexist.myhome.net, which is not a real server or DNS entry, it also shows the unraid webUI. Also interestingly enough, even when I change the TLD setting in unraid to myhome.net, tower.local still works. Probably unrelated and a separate issue, but also I am noticing that if I have the TLD set to myhome.net and access the webui from tower.myhome.net, some of the UI seems broken, such as the device information on the main page does not show at all, but it has the correct number of rows. I have tried changing the local TLD in the unraid webUI management page from local to myhome.net, I have set SSL to yes, and to no, and have turned off docker and vm services to see if it could have been related to those. I am sure this is probably something simple that I am overlooking, but am currently scratching my head about this one. Unraid is 6.11.5, pfSense is 2.6.0-RELEASE. Thank you in advance for your help!