GUI not loading in chrome

[Fatila]

Odd error, started happening out of nowhere some months ago, used to work fine. Google chrome is the only browser I can't load the gui of sabnzbd in, works fine in all others. Using either localhost or my IP returns: "Oops! This link appears broken. Page not found - connection failure" I can see the favicon for a second before this happens though. Any ideas?

[switch]

If you press F5 to refresh the page a few times does it eventually appear?
What about trying http://[::1]:8080/sabnzbd/ and http://127.0.0.1:8080/sabnzbd/

[Fatila]

The ipv6 address works, bizarre. Must be an odd chrome bug.

Thanks.

[FoxForceFive]

I have this same error, just started tonight.

The GUI works fine in Firefox & IE but wont work in Chrome.

I'm currently using IE Tab Classic extension as a workaround but it's not really a proper solution.

[shypike]

Our viewpoint is that if SABnzbd works in Firefox and IE
but not in Chrome, this is a Chrome issue.
The HTML and Javascript we use is fairly conservative.
Chrome is a moving target anyway: it's in Beta and is auto-updated.
Problems may come and go.

[FoxForceFive]

That's fair enough, it make sense anyway.

I just wanted to make sure there wasnt an obvious change I could make to correct this.

I'll go pester people the Chrome dev's now then!

Cheers for the quick response.

[Nelchael]

Sorry to gravedig, but this topic was among the first few google search results for my problem.  I had these issues on Mac OS X 10.6 running Chrome 5.0.375.125.

Chrome appears to have some weird caching issues.  I had the same problem... wouldn't work with [::1], localhost, 127.0.0.1, etc.

I flushed DNS, made more localhost entries (localme, etc.) in hosts file, all to no avail.

I restarted Chrome, tried the URL two more times, and it suddenly worked.

If you're having this problem with Chrome, but FF/Safari/IE work fine:

• Try http://[::1]:8080/sabnzbd/ and http://127.0.0.1:8080/sabnzbd/
• Refresh several times
• Try restarting Chrome
• Try a few more refreshes and a manual cache flush within chrome

For what it's worth, it took a while for my SABnzbd Chrome Extension to begin working, even after I was able to access the URL within Chrome.

Edit: Also, answered in these topics, but I didn't see any reference to cache issues in them:
http://forums.sabnzbd.org/http://forums ... 435#p31435
http://forums.sabnzbd.org/index.php?topic=4273.0

[Pyrepenol]

Since this is the thread that came up when I went troubleshooting I'll bump this too. Worked fine in any other browser but loaded in chrome without any dynamic information at all (queue, past dl's, etc.).

Restarting chrome fixed it, but of course I had to spend half an hour trying to fix it beforehand.