Utorrent not interfacing with WebUI

[vandan]

Hey, there I think I've found a problem with Utorrent 2.0 Beta Build 16850.

It seems like if I access the WebUI version .0361 via my phone which is using Opera Mini Beta 5.

With the full WebUI the screen states that it is "Loading..." but the torrents labels all say "0" . It's hard to explain because it is a mini browser and I dont think it does javascript...tho nevertheless I've used it before with older builds of beta and its worked, in both mobile view and full web-like view.

So for good measures I downloaded the utorrent WebUI Mini and tried that and that gives me the display the total amount of torrents displayed is 0 of 0.

I dont know what it could be, but seems like utorrent is not transmitting the torrents. Let me know if you need more information. Thx

[Ultima]

You're probably running into an Opera Mini bug: if you have torrents that have non-ASCII characters (think Unicode, or characters in some other language), Opera Mini will fail to work properly because of a bug on their end (which affects any web application using regular expressions with non-ASCII strings). As you might notice, I reported the bug about half a year ago, and they still haven't fixed it (the bug was around for longer too -- I just never got around to reporting it to them for a while). If you run into a problem where the torrent list just won't load, please join me in that thread to confirm the bug report, because they don't seem to care much about it. A half a year wait for a bugfix is rather long for something as basic and integral to the web as JavaScript+Unicode+RegEx, so it's rather appalling that they're still ignoring the bug.

Also, this isn't to toot my own horn or anything, but honestly, the main WebUI simply isn't well-suited to use on small screens. You may have a better experience with a UI designed with small screens in mind, like µTorrent MiniUI (though it won't work either unless the Opera devs get their act together).

[vandan]

I dont know, but I only have one torrent in my current list that has a non-ascii character (it has a Registered Trademark symbol), but I've used the webui with Opera Mini 5 Beta from my phone with no issues, while that torrent was in the list with no issues many times before.

Also, I know about WebUI Mini, as in my earlier post I stated that this problem even arose when I tried using WebUI Mini. Although, the cool thing about Opera Mini 5 Beta is that both the full fledged WebUI and the WebUI Mini both worked on my phone.

[Ultima]

Try renaming the torrent in µTorrent to something without offending characters and see what happens in Opera Mini. If it works, then you are experiencing the bug I mentioned above; if not, then something else is indeed causing the problem. It can have worked before, but suddenly stop working because the bug I mentioned is most likely an Opera Mini server-side bug, not an Opera Mini client-side bug. That means that if they suddenly decide to change the server software one day, you can conceivably see a different rendering without ever having touched the Opera Mini installation on your phone.

[vandan]

Nope, that didnt work either.

The only things that have changed are my phone and the utorrent 2.0 beta build I'm using. The phone is virtually the same though as my last one, plus Opera Mini 5 Beta is a from a .jar .

[Ultima]

What does the µTorrent Logger tab show when you attempt to access WebUI from your phone? (Make sure you have WebUI request logging enabled)

[vandan]

Using the Mini WebUI

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/index.html

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/style.css

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/utility.js

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/utorrent.js

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/webui.js

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/pane.js

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/page.js

[2009-11-08 19:33:38] HTTP: IP 64.255.180.118: GET /gui/mini/html.js

[2009-11-08 19:33:39] HTTP: IP 64.255.180.118: GET /gui/mini/miniui.js

[2009-11-08 19:33:39] HTTP: IP 64.255.180.118: GET /gui/token.html

[2009-11-08 19:33:39] HTTP: IP 64.255.180.118: GET /gui/?token=ttoncWs_-AU8TnjegzR7fMJczH3SDrg-dxRgUmbccjaqiNZI7_NeiWNj90o=&action=add-url&s=&t=1257726819099

[2009-11-08 19:33:39] HTTP: IP 64.255.180.118: GET /gui/?token=ttoncWs_-AU8TnjegzR7fMJczH3SDrg-dxRgUmbccjaqiNZI7_NeiWNj90o=&action=getsettings&t=1257726819192

[2009-11-08 19:33:39] HTTP: IP 64.255.180.118: GET /gui/?token=ttoncWs_-AU8TnjegzR7fMJczH3SDrg-dxRgUmbccjaqiNZI7_NeiWNj90o=&list=1&cid=&t=1257726819291

Using the standard WebUI

[2009-11-08 19:36:14] HTTP: IP 64.255.180.118: GET /gui/?token=ttoncWs_-AU8TnjegzR7fMJczH3SDrg-dxRgUmbccjaqiNZI7_NeiWNj90o=&list=1&cid=&t=1257726974257

[2009-11-08 19:36:50] HTTP: IP 64.255.180.118: GET /gui/?token=ttoncWs_-AU8TnjegzR7fMJczH3SDrg-dxRgUmbccjaqiNZI7_NeiWNj90o=&list=1&cid=&t=1257727010136

[2009-11-08 19:36:50] HTTP: IP 64.255.180.118: GET /gui/

[2009-11-08 19:36:50] HTTP: IP 64.255.180.118: GET /gui/stable.css

[2009-11-08 19:36:50] HTTP: IP 64.255.180.118: GET /gui/favicon.ico

[2009-11-08 19:36:50] HTTP: IP 64.255.180.118: GET /gui/main.css

[2009-11-08 19:36:50] HTTP: IP 64.255.180.118: GET /gui/images/snake.gif

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/temp.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/lang/en.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/mootools.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/images/tbar.png

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/images/zoom.png

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/images/toolbar.png

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/utils.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/stable.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/webui.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/contextmenu.js

[2009-11-08 19:36:51] HTTP: IP 64.255.180.118: GET /gui/tabs.js

[2009-11-08 19:36:52] HTTP: IP 64.255.180.118: GET /gui/main.js

[2009-11-08 19:36:52] HTTP: IP 64.255.180.118: GET /gui/?token=XUb7hGMOGQ7dmSFbkf9_uv7nq67oIIS1Bni3Fykjn_MBGRbtwqPcBiJk90o=&action=getsettings&list=1&t=1257727011916

[Ultima]

Well, first things first, check the Opera Mini settings and make sure you aren't using mobile view.

At any rate, if you're seeing 0 for all counts in the labels/categories list, then that likely means mobile view isn't the problem -- the problem is that the torrent jobs list isn't being processed correctly, again because of Opera Mini's bug as mentioned above. Your logs clearly indicate that the UIs are both loading correctly and are correctly requesting the torrent jobs list from µTorrent, meaning that they're operating correctly to some degree. That they freeze afterwards is indication that something happened while the torrent jobs list was being processed.

Question: When µTorrent MiniUI stops loading, how does it look? Are the tabs and everything visible and clickable (like Settings or Add)? If so, then this is fairly concrete evidence that you are running into the Opera Mini bug.

Why is it still happening when you "fixed" the supposedly-offending torrent? Because there are likely other torrents in your list that are using characters that Opera Mini's regex engine isn't handling correctly (maybe accented characters, or something). If you still need more concrete evidence, then...

1. Exit µTorrent

2. Backup your settings directory (find %appdata% here)

3. Clear the settings directory

4. Start µTorrent, re-add torrents that you know for sure have only simple characters in their names

5. Try accessing WebUI from Opera Mini again

As an aside, I just tested Opera Mini with a torrent jobs list with non-offending characters. It works, and I must say, WebUI looks a lot nicer on Opera Mini than I had expected. There are usability issues, though -- like the fact that everything's squished, and that there are no scrollbars.

[vandan]

Well, when utorrent Mini stops loading it, the tabs are visible and click-able. It does display 0 of 0 at the bottom for the total torrents.

I'm not currently home but I will try the "backup and simple torrent procedure" when I get home. The WebUI does work in other browser tho, so you may be correct. I'll let you know.

Yes, the normal WebUI does look really nice on the Opera Mini 5 Beta. It is squished (tho your screen looks really good, my squishing is way worse than that), and you can see all the data. My phone is touch-screen so I can scroll, if I click on a torrent in the box and do a "short hold" then flick the list will scroll (but then again my phone was squished enough where it could only display 3 torrents at once). I dont know about normal phones, there might be a keypad combination tho. Normally, tho I just put my phone in Mobile View, and use that because I can then scroll an see all the data. I dont know why Mobile View doesnt work for you phone but I have no issues with it, it just displays everything in the WAP-like view instead of webpage view.

Edit: I tried it whence I got home and lo and behold looks like that cleared up the problem. So Ultima I suppose you are right, the WebUI is functioning correctly.

[Ultima]

Cool. Now that you've confirmed the bug, can you also voice a bit of your grief in Opera's forums? I would make another post there, but triple posting simply makes me look like an annoying nag more than anything. If more people join me, maybe they'll finally realize that it's not just one person experiencing this, and will have a stronger incentive to stop sitting on their hands and actually start fixing this annoying bug.

[vandan]

Wilco.

Also as of Dec 02 Opera Mini Beta 5 has been released...i dont know if the problem still exists as I have reinstalled my OS.