mr sharpoblunto

an http 502 error is typically related to an error with your connection to the server, possibly because of firewalls/intermediary proxies etc... Http 502 definition: 'The server was acting as a gateway or proxy and received an invalid response from the upstream server.' Are you sure you have entered the correct ip and port settings?

Quick update... I've got adding torrents from the phones filesystem working! I need to do some more testing/polishing but I should be able to release 1.70 in a few days EDIT: Actually I think I've got it all working now so I'm releasing early! If your phone supports filesystem access then you'll have a new option 'Add torrent file' in 1.7 which will allow you to browse your phones memory for .torrent files to upload.

Hi everybody, its been a long time but I've finally got around to getting my j2me dev environment back up and running! I've released the official build of 1.61 which fixes the problems people have been experiencing with 2.0.1. Also thanks to spootle for alerting me to the fix. I didn't fix it quite the same way that you did for various reasons but It's fixed now nonetheless It seems that 2.0.1 changed the way the token authentication system worked. Pre 2.0.1 if you didn't include a valid token the server would return an http 300 (which is in the API specification), however it now returns a 400 which caused a false server not found exception to be thrown. So it would be a good idea for whoever maintains the API docs to update this bit of info to save other devs some frustration. @Calleja I've played around with adding torrents from the phones filesystem but never quite got it working right. However its still on my todo list if I get time.

@Abhik the IP, username, and password are the IP of the PC running uTorrent, and the username and password you set for the webUI on that machine. It sounds like you are actually using your phone as a bittorrent client. uTorrent Mobile is NOT a BT client, its simply a means to remotely access uTorrent running on a PC somewhere. @villapark75 Thanks for the heads up, I wasn't aware that there were issues with 2.0.1, I'll look into getting a dev environment set up again in the near future and looking into the problem.

The proxy program won't help in your situation, it only helps if you are getting errors regarding invalid username/password. How long does it typically take to view the utorrent webui using the browser on your blackberry? the connection may be timing out.

@ndhaliwal Do you have a firewall thats blocking incoming connections to the webui, or perhaps a router port forwarding problem? Anyway in other news my new site is up. The version of utorrent mobile is the same and should download/install same as before, but if theres any problems, let me know. The proxy authentication tool is also now available for download (see first post in this thread) for people that are having issues with authentication (t3ra etc...). bear in mind that this won't fix any server not found errors, but rather issues where the username/password always seems to be incorrect even though you are sure you are using the correct details.

Hey, I've been away for a while and I've just rebuilt my PC so I have no dev environment set up as yet. I'm in the middle of building a new site to host my apps etc. but that should be ready soon. Anyway for the moment I can answer a few questions I've noticed a few people cannot access my site. This is because its currently hosted on godaddy which is blocked in china my new site will be hosted elsewhere and will not have this issue. @solnyshok ssl support is not on the cards at the moment. J2me and self signed ssl certificates don't play nicely. @ultima. I don't know for a fact but my old cell provider definately stripped the auth header on all of utorrent mobiles requests, I don't know the reason but I suspect that it was because it was an uncertified app. However my new provider does not strip the headers, so its obviously not totally standard practise. Anyway once I've got my new site up and running I'll publish the authentication proxy tool. @knw257 Its interesting that the token param is stripped. The mobile client should request token.html and extract the token, and from then on include that token in all requests. I've seen a few reports of people having issues with token auth, however it works fine for my so I'm not sure where the problem lies. Ultima do you think that clients could optionally include the token as a custom http header rather than as part of the request url if it does turn out that some providers strip the token from the request?

You should be able to run 1.60 without token authentication enabled. I tested this while writing the new version, but I'll double check. Let me know how it goes when you turn token auth on though anyway

What is up with these forums? I can't log in using firefox 3.5 and they seem to periodically forget that I want to be emailed when people reply to this thread... hence the long wait for my response. @jman 177 Do you have webUI token authentication turned on? (If you don't know what I'm talkinmg about its probably off as thats the default in 1.8.3) What html output (i.e whaen you view the html source for the page) do you get when you go to http://<utorrent webui address>/gui/token.html Also when does this error occur for you, all the time, or only after a certain period of time? @Wolfgan I've seen some other blackberry users report this issue, but to the best of my knowledge its a valid jar as it seems to work on other phones without issue. I don't know what exactly the problem is, but I'm downloading the blackberry emulator software to see if I can reproduce the problem

Just checked all the links, they all work for me Which link didn't work for you?

I got a new phone recently (Nokia 6120 classic) and so I've done a bit of work on uTorrent mobile, and finished work on version 1.6 (see the first post in this thread for the download link) The main feature in this version is support for the webUI token authentication system which is going to be enabled in future versions of uTorrent. This change ensures that uTorrent mobile will continue to work as future uTorrent versions are released. This feature is backwards compatible with existing uTorrent versions so don't worry about upgrading causing problems if you're running an older version of uTorrent. @Matt01 I tried adding support for SSL a long time ago, but there are serious issues with j2me apps connecting to https servers that use self signed certificates, so unfortunately it won't work over ssl. @j s - I typically I have only a few torrents running at a time, so I never even considered that someone would have 500+ torrents in the list (You must have a much higher monthly data cap than i do ). I'll keep the filtering feature in mind for any future work, but I'm probably not going to be able to do it any time soon.

You could try downloading the utorrent mobile zip file instead of downloading it directly from the site. (The download link on the utorrent mobile page), in the zip you'll find utorrent.jad and utorrent.jar (You'll need both files). I'm not sure of the process for installing from local files on your device, but on my phone I need to copy those files onto my phone, then go to applications then select utorrent.jad to install.

@atomicRabbit I finally got around to upgrading utorrent to 1.8.2 and webUI 0.361 on my server (I had been running 1.6.something with the 0.310 webUI for a couple of years now). and I can confirm that utorrentMobile 1.51 works fine for me. So I've fixed the spelling mistake you reported and put up a new version 1.52, try downloading that and see if it works. I confirmed that it downloaded and installed okay for me, but I don't have a Blackberry so I can't be sure if it will work out for you (though I may be getting one in the not too distant future...) The error message your getting on install seems pretty weird, there doesn't seem to be much google wisdom out there for it, perhaps someone with a bit more blackberry knowledge can shed some light on this? As for the other message with utorrent mobile 1.4 java.io.EOFException null. I really can't tell you why thats happening, it seems that your webUI is responding with data that should work. Perhaps theres some sort of network infrastructure issues at play somewhere... firewalls, proxies interfering etc... I guess you could ty running a packet sniffer like wireshark on your webUI machine and try using the mobile client and see if the http request actually arrives on the server or not. If you're technical enough to do that then that could be a useful next step.

@shiploo35 The ip should be the internet facing IP of your utorrent webui server, not the gprs ip of your telecom provider.

if you're behind a router you'll need to use your routers public ip address (not it's LAN ip address) then set up a port forwarding rule on your router to forward requests on the webui port to your utorrent machine. There's lots of guides on these forums on how to set up port forwarding for the webui.

@greenfort A little more detail as to the problem your experiencing would be useful. Otherwise I can't really offer any help.

You could set yourself up with a dynamic dns name with a service like dyndns.com, which will allow you to access your dynamic IP from an unchanging dns name. Theres a howto on their site here

thanks sndr I'll look into the refresh bug. Edit - Fixed the bug, released a new version, see the first post for details.

Okay, released version 1.5, this version includes settings for turning torrent list refreshing off and for toggling text wrapping, it also now shows the ETA of torrents being downloaded. @atomicrabbit Could you try entering the following url into the browser on your phone http://<ipAddress>:<port>/gui/?list=1 and send me the output from that. The particular error you're seeing is one I haven't seen before, but if the output from this url is weird it may shed some light on things.

@rocketsvm Sorry for the late reply, have been busy the last week or so. If you could send me the code for your fixed version of utf8Decode, or post it here that would be fantastic, also How did you get on setting up eclipse?

@rocketsvm Send me a PM if you want access to the subversion source repository for uTorrentMobile, if you've got a working dev environment set up then the changes you've requested should be pretty easy to implement. I don't have a lot of time at the moment to work on uTorrentMobile, but I try to fit it in around everything else "Also, there was a report about empty password not working. May be this is the reason:" Yeah that's definitely the reason, I never thought that people would run the webUI without a password that check could probably just be changed to look if the server field is empty, but allow a blank username/password.

Thanks rocketsvm, that sounds great! It would be quickest for me to implement these changes if you could post up your changes to getString(), to save me having to write and test the same thing. --Edit-- Okay, new version out. added support for cyrillic text in torrents, also added a partial workaround for people who frequently experience 401's when trying to access uTorrent via the mobile client when using the correct username/password. The other part of the workaround involves installing a helper windows service on the webUI host machine (I'm almost finished with this, theres just a few kinks to iron out before releasing it) For those who are interested in the technical details of the workaround, read on, otherwise go to the first post to get the new version! As I've mentioned previously, for some people (me included) the http Authorization headers seem to be being stripped from uTorrentMobile requests before they get to the webUI, resulting in 401's all the time. To work around this the 1.4 version of uTorrentMobile also includes a new http header X-j2me-auth, which contains the same information as the Authorization header. Now this is a custom header which gets ignored be the normal webUI, so if uTorrentMobile works for you now, 1.4 will continue to work fine. However if you have the 401 issue, I've been working on a proxy application which sits in front of the uTorrent WebUI and if it sees a X-j2me-auth header on a request and no Authorization header, it turns the X-j2me-auth header into an Authorization header, then passes it off to the webUI. This works perfectly as the custom header never gets stripped, so once the request arrives, we can see if the Auth header got stripped, and if it did, just add it straight back so that the webUI is none the wiser! This proxy application has been written in .NET and runs as a windows service so you wont even notice its running. I'm not going to release it yet, as theres a few rough edges to tidy up, however it mostly works (in fact I'm using it right now as I get the 401 issue all the time now), but if you really want it now, let me know. I'll post instructions on how to set it up etc. when I release it.

Okay, Is your dynamic IP accessible via the internet, i.e have you set up port forwarding on your router (assuming you have one) to map incoming connections for the routers IP to the machine which has UTorrent webUI running. Second thing, are you sure you set up webUI not to use a password, its probably not a good idea to have it accessible to the internet without a username/password. A good test to see if webUI is working properly is to try to access it from a computer outside your local network, i.e a PC at work/university/school etc. and see if you can access it there. If you can't access the webUI from an external PC, the uTorrent mobile client wont be able to access it either let me know how you get on :-)

Well I've been looking into the issue of periodic connection failures that I experience along with AtomicRabbit and some others. It appears that the problem is caused by authentication failure as http 401's are being returned. This is weird because the authentication process works some times and not others. (first a bit of background, utorrent webUI uses http basic authentication which works by attaching an Authorization header to the http request which contains your username/password base64 encoded) I ran a packet sniffer on my utorrent server and found the following, when running the app using the software phone emulator the Authorization header came through and the app authenticated ok. However when I loaded the app on my phone there was no Authorization header present on the request, even though I attached one as the request went out. I've concluded that somewhere along the way the authorization headers are being stripped from the utorrent request. This doesn't happen all the time for me (though it is at the moment) and by some of the responses I've seen in this thread, some people are unaffected, so it seems like it might be part of the cellular network infrastructure which is causing this stripping of the auth header. It may have something to do with the fact that unsigned j2me apps (such as utorrent mobile) have a user agent header of "Untrusted/1.0", I'm wondering if somewhere along the way untrusted apps have the auth headers stripped off (though the weird thing is is that its intermittent). I'm gong to have another look at it tonight and release a new version that details the errors of any failed connections, but I'm not sure if this issue is something that I can fix. UPDATE Okay, released a new version (see first post for download link), its functionally the same as 1.3.1, but includes some more details when errors occur. Try it out and if you have any problems let me know

@sndr Unfortunately the truncation of torrents that you're seeing on your phone seems to vary from device to device. My phone wraps the torrent names over multiple lines, and I suspect that other devices handle long text in a number of different ways. There's nothing I know of in j2me that defines or allows me to control this sort of behavior in the standard list control, so there's not too much I can do I'm afraid