Archived

This topic is now archived and is closed to further replies.

Lord Alderaan

Weird page after login

Recommended Posts

You login to the webui and you get a page resembling this:

ajaxproblem.png

This is an elusive problem that seems to appear when the index.html page does load but the retrieval of some of the additional files failed or was hampered. So far it has never been a problem of the webui itself.

[h]The currently known reasons for this problem are:[/h]

  • GZIP content filtered or unrecognized. Try: The legacy version of WebUI, or extract the .gz files in webui.zip and replace them with their extracted counterparts.
  • Corrupt download of webui.zip. Try: Redownloading webui.zip.
  • Browser or plugin playing up. Try: Different browser, disable all plugins, uninstall all plugins.
  • Software Firewall playing up. Try: Remaking rules, disabling firewall, uninstalling firewall.
  • Proxy or ISA server between you and your webui playing up. Try: This post, or this post, or the legacy version of WebUI, or (if possible) bypass the proxy/ISA server altogether.
  • Corrupt settings.dat. Try: Exit µTorrent, backup settings.dat from Start > Run > %appdata%\uTorrent, then delete settings.dat and settings.dat.old from there and restart µTorrent (you will need to reconfigure the settings).

[h]No go. What now?[/h]

To be honest if the above suggestions didn't help you we have little hope of solving the problem. However if you really want to try at least provide us with the following info so we can provide suggestions and/or at least give reasons why it will not work. Make sure you tried different browsers and machines on different locations first!:

1) First open µtorrent itself and open the logger tab. R-click in it and choose clear log, r-click again and choose Verbose Logging -> Log WebUI requests

2) Now go to one of the machines where you have the above problem.

3) If you use Firefox (on the machine where the webui is having this problem) go to Tools -> Error Console and press clear.

4) Now login to the webui.

Now make a new post here and write down:

  • The location of the problem machine(s) (friend/work/school/library/etc).
  • The firewall software (if any) you use on µtorrent machine and the problem machines.
  • The list of requests in the webui logger tab. (see below for example, you can select the lines and r-click -> Copy)
  • The list of errors in the Firefox Error Console. (you will have to r-click copy, past them one by one unfortunately, you can skip the 'zoom' and 'wrap' Declaration dropped errors.)
  • Any other info you think might be relevant.

This is an example of how a request list from the logger would look. This is how the list should look, your list is probably shorter.

[2008-12-09 10:50:08]  HTTP: IP 127.0.0.1: GET /gui/index.html
[2008-12-09 10:50:08] HTTP: IP 127.0.0.1: GET /gui/stable.css
[2008-12-09 10:50:08] HTTP: IP 127.0.0.1: GET /gui/mootools.js
[2008-12-09 10:50:08] HTTP: IP 127.0.0.1: GET /gui/main.css
[2008-12-09 10:50:08] HTTP: IP 127.0.0.1: GET /gui/images/snake.gif
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/images/ut.png
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/temp.js
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/images/mootools.png
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/images/tbar.png
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/images/zoom.png
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/images/toolbar.png
[2008-12-09 10:50:09] HTTP: IP 127.0.0.1: GET /gui/lang/en.js
[2008-12-09 10:50:11] HTTP: IP 127.0.0.1: GET /gui/mootools.js
[2008-12-09 10:50:12] HTTP: IP 127.0.0.1: GET /gui/utils.js
[2008-12-09 10:50:13] HTTP: IP 127.0.0.1: GET /gui/stable.js
[2008-12-09 10:50:13] HTTP: IP 127.0.0.1: GET /gui/webui.js
[2008-12-09 10:50:14] HTTP: IP 127.0.0.1: GET /gui/contextmenu.js
[2008-12-09 10:50:14] HTTP: IP 127.0.0.1: GET /gui/tabs.js
[2008-12-09 10:50:14] HTTP: IP 127.0.0.1: GET /gui/main.js
[2008-12-09 10:50:14] HTTP: IP 127.0.0.1: GET /gui/?token=2iHhboB9V9ql2bcVLlXpploHh9BGaG2e_k82f38e-l0Kq7weiZkaVVA_Pkk%3D&action=getsettings&list=1&t=1228816215768&
[2008-12-09 10:50:22] HTTP: IP 127.0.0.1: GET /gui/images/header.png
[2008-12-09 10:50:22] HTTP: IP 127.0.0.1: GET /gui/images/arrow.gif
[2008-12-09 10:50:22] HTTP: IP 127.0.0.1: GET /gui/images/ldbg.png
[2008-12-09 10:50:22] HTTP: IP 127.0.0.1: GET /gui/images/nextprev.png
[2008-12-09 10:50:22] HTTP: IP 127.0.0.1: GET /gui/images/tstatus.png

Related topics:

Webui corrupt/broken on remote host

Edit (Ultima, 2008-12-09): Added the note about GZIP content. By my guess, it's the most common yet overlooked reason.

Edit (Ultima, 2009-01-28): Added the note about corrupt webui.zip download. That seems to be another common one.

Edit (Ultima, 2009-02-18): Added the note about corrupt settings.dat. Less common, but always a fair last resort to clear it.

Share this post


Link to post
Share on other sites

Hi.

This problem popped up on my system from the moment I started using a ISA 2006 Proxy.

I compared my list of accessed files with the list in the post above and noticed that mootools.js wasn't loaded successfully. I logged all connections and noticed a 'compression error' on the request for mootools.js. Also browsing directly to the /gui/mootools.js file gave me a compression error in firefox.

After seeing this I disabled the HTTP compression setting that is available in ISA 2006. No success.

I did some googling and found this:

It is to do with HTTP compression. ISA disables compression by default for HTTP, whereas without ISA (or the Microsoft Firewall) running, compression is apparently turned on by default. This is why the website loaded properly when not running the firewall. Don't ask me why, it just works. We set compression on HTTP requests, so that ISA asks for compressed content when making requests to the internal network (remembering that we are single adapter here). Now everything is fine. Thanks for listening!

After reading this I added my internal network adapters to the HTTP compression configuration (request compressed data from and receive compressed data from).

And magically everything seems to work fine!

I hope this information can help someone.

Bert!

Share this post


Link to post
Share on other sites

Sorry, my english is a bit limited. Do you mean I should enable/disable something related to HTTP compression in the utorrent machine? May you explain better how or at least where to do it?

Regards

Share this post


Link to post
Share on other sites

Unless you're using an ISA proxy, then VMax's post is irrelevant for you. Have you tried the suggestions in the first post?

Share this post


Link to post
Share on other sites

I was having this issue on IE7 on the PC's at my work.

Machines with IE6 were not affected. (Unable to try Firefox due to IT restrictions)

I found that unchecking the option 'Use HTTP 1.1 through proxy connections' fixed this for me.

Share this post


Link to post
Share on other sites

Chances are, this may in part be due to the fact that µTorrent isn't respecting HTTP 1.0 requests. The problem is that HTTP 1.0 proxies do not support GZIPped content, but µTorrent doesn't recognize that, and keeps sending HTTP 1.1 responses with GZIPped content.

Essentially, unpacking the GZIP files should work around the problem as well. In the end, µTorrent still need to be fixed though.

Share this post


Link to post
Share on other sites

I have this problem in firefox only but is fixed by the following:

Tools>Options>Privacy>Show Cookies>

Find your webui domain and expand then delete the following cookies.

__utmb

__utmc

__utma

__utmz

Click close and ok.

Share this post


Link to post
Share on other sites

Using the latest v0.362 WIP release and clearing the cookies by following the readme fixed this issue for me. I tried going to back the v0.361 but no matter what I did I always had the same problem.

Share this post


Link to post
Share on other sites