Jump to content

Can't access WebUI (invalid request)


MageLuingil

Recommended Posts

I've been running uTorrent v1.6.1 and the webUI interface version 0.315 for months, without a problem. This morning, I decided to try upgrading to the new version of webUI, 0.361 (the legacy version, of course). Installed it, tested it, it was working fine. Left it alone and went on to do other things.

Now, here's the odd part. This evening I went to check my torrents, and it wouldn't let me access the page. I got the message "invalid request" and couldn't do anything. I'm not missing the /gui/ (I'm browsing to http://localhost:2020/gui/ which was working this morning) and that is the correct port set in my properties.

When I try to connect to the page, I get these messages in my Logger tab:

[19:19:37] UPnP: Discovered new device: http://192.168.32.163:5431/uuid:0012-1739-9206020099dc/WANIPConnection:1

[19:19:39] UPnP: Port 53068 is already mapped. Not re-mapping.

[19:19:39] UPnP: Discovered new device: http://192.168.32.1:4444/wipconn

[19:19:40] HTTP: IP 127.0.0.1: Blocked: GET /gui/

[19:20:18] UPnP: ERROR -3 mapping port 53068 -> 192.168.32.100:53068

[19:21:26] HTTP: IP 127.0.0.1: Blocked: GET /gui/

[19:22:42] HTTP: IP 127.0.0.1: Blocked: GET /gui/

[19:37:27] HTTP: IP 127.0.0.1: Blocked: GET /gui/

[19:37:58] HTTP: IP 127.0.0.1: Blocked: GET /gui/

[19:38:43] HTTP: IP 192.168.32.100: Blocked: GET /gui/

[19:38:49] HTTP: IP 127.0.0.1: Blocked: GET /gui/

[19:40:38] UPnP: Port 53068 is already mapped. Not re-mapping.

[19:41:01] UPnP: ERROR -3 mapping port 53068 -> 192.168.32.100:53068

Any ideas? Thanks in advance for any help.

Link to comment
Share on other sites

Yeah as you see there's some... problems with webui.cookie between versions. Good news/bad news as usual with all things which change I suppose. However being able to see the webui is a large culmination of effort. And hopefully it will get more attention now that the TRAC is public for people to put in bugs/requests. Then again, alot of the functionality is determined by the backend... exported variables and such. So it's a catch-22, for more functionality people need to request it, it needs to make sense/be approved, and then coded into the client, for it to show up in the webui :P

It's not a big change when you update, but 1.8 has changed the layout of some things. Press F1 after the update, to get the new manual and take a look around. Then you should be able to clear NaN in the Preferences for WebUI. That should allow you to access from localhost/LAN again. :/ Why it happened, only the coders know, heh

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...