einniv Posted March 9, 2018 Report Share Posted March 9, 2018 To avoid confusion this issue is related to accessing the Web UI over a local LAN. When I posted this in troubleshooting there was confusion with people thinking I was talking about accessing it over the internet. Devices on a local LAN have a device name/computer name. These names can be used to access services on the device. Examples might be file browsing, or a web server (e.g. http://TheServer), or a subsonic music server (e.g. http://TheServer:4040/index.view), or an Emby media server (http://TheServer:8096/web/dashboard.html), and until a recent update , uTorrent (e.g. http://TheServer:9091/gui/). Now uTorrent no longer responds when using the computer name, giving a 400 error. Using the IP address works fine as before (e.g. http://192.168.0.51:9091/gui/). If I'm actually on the server localhost works and so does the loopback address 127.0.0.1, but not the device name, locally or over the LAN. This has previously been working for a few years. All other services (as listed above) continue to work with the device name just fine. This isn't a huge deal but I would prefer to be able to use the device name rather than IP address if possible. Edited to add: I noticed in the change log for the last release "– Sanity check Host header on HTTP requests" among other changes to the Web UI . Wondering if it is related to this. Link to comment Share on other sites More sharing options...
gugugugu Posted April 29, 2018 Report Share Posted April 29, 2018 I'm having exactly the same problem on 3.5.3 build43916 On computer running uTorrent I can connect to webUI via "192.168.1.10:8080", "localhost:8080", and "127.0.0.1:8080", but NOT "http://computername.local:8080", On diff. conputer, same LAN i can ONLY connect via "192.168.1.10:8080" Link to comment Share on other sites More sharing options...
KewlRobd Posted May 22, 2018 Report Share Posted May 22, 2018 I have a work around for this which I posted about in this thread. Link to comment Share on other sites More sharing options...
norti Posted June 23, 2018 Report Share Posted June 23, 2018 At last this bug is fixed in the latest μTorrent 3.5.4 Beta (build 44488)! http://utclient.utorrent.com/offers/beta_release_notes/release_notes.html Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.