April 3, 201313 yr Until last week, I could type 'tower' into the address bar of Firefox, and it would go to the web management page of my unRAID server. Now, when I type 'tower', it fetches www.tower.com. If I enter tower:8080 it still fetches the unMenu page, tower:9000 fetches Squeezeboxserver, etc. tower is still in my hosts file, pointing to the ip address of myunRAID server. telnet tower, telnet tower:80, etc still go to the unRAID server. wget tower still fetches the unRAID page. Why won't Firefox oblige? What has changed and how do I change it back? I'm running Ubuntu.
April 3, 201313 yr https://support.mozilla.org/en-US/kb/search-web-address-bar?redirectlocale=en-US&redirectslug=Location+bar+search#w_domain-guessing
April 3, 201313 yr Other than the above (Which, more than likely is your best bet assuming that you don't ever just type "Google" or something into the address bar), have you tried adding a forward slash after the host name? http://tower/ like that.
April 7, 201313 yr Author Thank you both for your suggestions and time taken to reply! Other than the above (Which, more than likely is your best bet assuming that you don't ever just type "Google" or something into the address bar), have you tried adding a forward slash after the host name? http://tower/ like that. Yes, I'd tried inputting exactly that string and it still went to the tower.com site. https://support.mozilla.org/en-US/kb/search-web-address-bar?redirectlocale=en-US&redirectslug=Location+bar+search#w_domain-guessing Even with guessing turned off altogether it still went to tower.com. I'd deleted tower.com from my history and ensured that I had no bookmark for tower.com. I concluded that it must be a cookie doing this - I searched for all cookies from tower.com, and deleted them. I disallowed cookies from tower.com. It still went to tower.com! In the end I deleted all cookies and sanity was restored. I'm not completely au-fait with cookie processing, but it seems that there was a cookie in my system which didn't have the string 'tower' in its name, but which was directing all activity for tower on port 80 to tower.com. I have to believe that this is an abuse of the cookie system, and if I'd been able to detect which site had put the cookie there I would have lodged a complaint. I guess that if it happens again, I need to find the cookie file and, assuming that it is in plain text, search for the content 'tower.com'. Anyway, if anyone else comes across this weird behaviour, perhaps this thread will help them to resolve it more quickly than I was able to.
April 7, 201313 yr Cookies have nothing to do with DNS resolution. Did you have the array started? Is your server set as master browser under the samba section? Sent from my Nexus 7 using Tapatalk 2
April 7, 201313 yr You could also edit your "hosts" file to make sure this doesn't happen. Assuming you have a static IP set for unraid. Sent from my SGH-I727R using Tapatalk 2
April 7, 201313 yr also in //YOURSERVERIP/Settings/SMB, you should set Local Master to Yes.. Reboot you router and PC.
April 8, 201313 yr Author Cookies have nothing to do with DNS resolution. No, but something in one of the cookies was causing Firefox to redirect http://tower/ to http://www.tower.com/. At the same time, tower:9091 would, correctly, bring up the transmission management page from my unRAID server. Access from anything other than Firefox was working fine. Did you have the array started? Errr... yes, else "wget tower" wouldn't have worked, nor would tower:8082, tower:9091, tower:9000, tower:143 etc. But why should I need the array started in order to access the emhttp interface? The array is started via the emhttp interface. Is your server set as master browser under the samba section? Yes, but this isn't an smb problem, it's only affecting http:80 access.
April 8, 201313 yr Author You could also edit your "hosts" file to make sure this doesn't happen. Assuming you have a static IP set for unraid. I already have 10.2.0.100 tower in my hosts file. Are you suggesting that I add 10.2.0.100 www.tower.com tower.com?
April 20, 201313 yr same issue i ran into. read: http://lime-technology.com/forum/index.php?topic=26804.0
April 20, 201313 yr I've seen this issue from time-time. Rebooting the PC you're using has, in my experience, always resolved it. I suspect there's a way to resolve it without a reboot; but it happens infrequently enough that I always just reboot. One other thing I've noticed will sometimes work: Access the array with Windows Explorer [e.g. \\tower\disk1 ] ... then try the browser again. Not sure why that helps, but it sometimes does.
April 20, 201313 yr Author same issue i ran into. read: http://lime-technology.com/forum/index.php?topic=26804.0 Having scanned that thread, I don't believe it is the same issue at all! My problem only related to tower:80 from Firefox. wget tower (port 80 by default) worked fine. tower:8080 worked fine in Firefox.
April 21, 201313 yr Author Does a reboot of the PC resolve it? Nope. The only way I found to fix it was to delete all cookies. If it happens again, I will check promptly for newly loaded cookies.
Archived
This topic is now archived and is closed to further replies.