Anyone ever gotten utorrent's WebUI to work?

Ilitirit

Well-Known Member
Joined
Sep 26, 2004
Messages
215
Reaction score
1
Location
.
I can get it to work if I use 127.0.0.1 but not if I use my external IP. Is it my router/firewall? Or maybe the ISP? Or is there something I need to configure?
 
Yeah I have been using it for about 2 months now.

1. It doesn't seem to work at all with Opera. I haven't gotten too far into checking out how to get it to work, if possible, though.

2. You have to forward ports on your router and then set uTorrent to use the forwarded ports. Also make sure your firewall is either off or has the same ports forwarded

3. I couldn't get it to work without setting a username/pass, so do that.

4. Luck :p
 
Yeah I have been using it for about 2 months now.

1. It doesn't seem to work at all with Opera. I haven't gotten too far into checking out how to get it to work, if possible, though.

2. You have to forward ports on your router and then set uTorrent to use the forwarded ports. Also make sure your firewall is either off or has the same ports forwarded

3. I couldn't get it to work without setting a username/pass, so do that.

4. Luck :p

I'm using Firefox 3.0 and IE 6/7, and my ports are forwarded and my firewall was disabled (during testing). Still can't get it to work even from the machine itself.

Could it be that the ISP is block port 8080?
 
I'm using Firefox 3.0 and IE 6/7, and my ports are forwarded and my firewall was disabled (during testing). Still can't get it to work even from the machine itself.

Could it be that the ISP is block port 8080?

Doubt it, that's a required HTTP port ;)
 
Doubt it, that's a required HTTP port ;)

My machine or router must be doing some fancy rerouting then. If I enter my external IP alone it gives me the router login page. Is that supposed to happen?
 
My machine or router must be doing some fancy rerouting then. If I enter my external IP alone it gives me the router login page. Is that supposed to happen?

I don't quite understand why you are trying to use a public IP address, it's dynamic in any case, not static.

Open cmd prompt and type ipconfig and press enter, look at your IP address of your computer (not the gateway, that's the router) and try to configure it that way.
 
If it works on 127.0.0.1 then it IS working fine.

If you get the router's web i/f on the "external IP" address then that's the address for your router and NOT for your pc. I presume you're testing this on your internal LAN when you get this. If you're getting the router's web admin when trying that IP address from the wider internet, then you'd better turn off "remote administration" on your router in a hurry! (hopefully you've changed the default admin pwd too...)

Your router will have a "public IP" on the interface that faces out to the Internet (you can determine what it is by logging into your router's web i/f and looking at the current connection details. This is more reliable than visiting, say, whatismyip.com or iplocatethis which give different addresses ... go figure).

I presume you really want to reach your utorrent web i/f from out on the internet. So as others have pointed out you need to

a) Find out what your router's real public IP address is. Note that this public IP will change if your ISP session is reset. Apparently Telkom no longer forces a reset every day but still, it's not going to stay the same for long. And when it DOES change then you're not going to be able to find out what it is if you're away from home. The only solution to that is to use something like the services of dyndns.org (my Netgear router has support for that built in - you choose a name e.g. myname.dyndns.org then whenever your router's public IP changes then it will update the dns database at dyndns.org with your new address. Your router is then always reachable at myname.dyndns.org).

b) Set up port forwarding on your router. Choose a port number (e.g. 8080 - usually 80 is reserved by the router for it's admin i/f but you can change that) and route all requests to that port to your pc's IP address. On some routers you can say that incoming port 8080 must be routed to your IP and a different port e.g. 80.
Note on port 80: if you've got IIS (or other web server) running that'll probably also grab port 80. Though if you've got a web server running then you're probably a developer and already know this ;) Also, Skype grabs port 80 as alternative for incoming connections. Anyway, make sure that the port on your pc that the request will get forwarded to is the same as set up in utorrent.

Hope this helps!
 
I don't quite understand why you are trying to use a public IP address, it's dynamic in any case, not static.

Open cmd prompt and type ipconfig and press enter, look at your IP address of your computer (not the gateway, that's the router) and try to configure it that way.

I want to access my home machine from work, but I'm testing from my home machine. I've got an email rule that returns my IP address whenever I send it a specially formatted email, so it doesn't matter that the IP is dynamic - it's easy enough to obtain.

Obviously I can't use the local IP of my machine to connect from a machine that's not on the LAN, that's why I need to use the external IP.
 
If it works on 127.0.0.1 then it IS working fine.

If you get the router's web i/f on the "external IP" address then that's the address for your router and NOT for your pc. I presume you're testing this on your internal LAN when you get this. If you're getting the router's web admin when trying that IP address from the wider internet, then you'd better turn off "remote administration" on your router in a hurry! (hopefully you've changed the default admin pwd too...)

Your router will have a "public IP" on the interface that faces out to the Internet (you can determine what it is by logging into your router's web i/f and looking at the current connection details. This is more reliable than visiting, say, whatismyip.com or iplocatethis which give different addresses ... go figure).

I presume you really want to reach your utorrent web i/f from out on the internet. So as others have pointed out you need to

a) Find out what your router's real public IP address is. Note that this public IP will change if your ISP session is reset. Apparently Telkom no longer forces a reset every day but still, it's not going to stay the same for long. And when it DOES change then you're not going to be able to find out what it is if you're away from home. The only solution to that is to use something like the services of dyndns.org (my Netgear router has support for that built in - you choose a name e.g. myname.dyndns.org then whenever your router's public IP changes then it will update the dns database at dyndns.org with your new address. Your router is then always reachable at myname.dyndns.org).

b) Set up port forwarding on your router. Choose a port number (e.g. 8080 - usually 80 is reserved by the router for it's admin i/f but you can change that) and route all requests to that port to your pc's IP address. On some routers you can say that incoming port 8080 must be routed to your IP and a different port e.g. 80.
Note on port 80: if you've got IIS (or other web server) running that'll probably also grab port 80. Though if you've got a web server running then you're probably a developer and already know this ;) Also, Skype grabs port 80 as alternative for incoming connections. Anyway, make sure that the port on your pc that the request will get forwarded to is the same as set up in utorrent.

Hope this helps!
I'm using http://checkip.dyndns.com/ to check my IP address. It sounds as if you're saying that what that is returning is actually the router's address. If that's the case then that's probably the cause of all the problems.
 
I'm using http://checkip.dyndns.com/ to check my IP address. It sounds as if you're saying that what that is returning is actually the router's address.

That is correct. Your router will have a "private IP" address for use on the internal LAN (on the so-called "private interface"), and another public IP address that is its address on the internet.
Your PC will not (typically) have a public IP address.
So, when you put the router's public IP address into your browser at the office, you need to have routing in place on the ROUTER so that it will relay the request to your PC on its internal, private IP address (and on the right port).

To determine your router's public IP address using checkip.dyndns.com is fine. If it gives you, say 41.241.76.66 then that's the router's public address and you'll enter "http://41.241.76.66" into your browser at work - or "http://41.241.76.89:8080" if you used port 8080 instead.
 
I figured out the problem. The IP address was correct but it the port was being forwarded to the wrong machine on the LAN.

Amateur mistake...
 
Top
Sign up to the MyBroadband newsletter
X