gugugugu

Established Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About gugugugu

  • Rank
    Member
  1. WebUI Not Reachable USing Computer Name

    Awesome, thanks very much for detailing your setup! Agree on nginx being a bit overkill for this little niche setup, so am gonna give https://traefik.io/ a go. Also, Very much agree on this!
  2. WebUI Not Reachable USing Computer Name

    Excellent! Mind sharing your recommendations for software?
  3. WebUI Not Reachable USing Computer Name

    Nope. Someone, somewhere blamed a security "fix" in the most recent uTorrent update (http://blog.utorrent.com/releases/). This bug also affects connectors like the Firefox extension "uTorrent Connector". In preferences for that extension I used to have "host: computername.local" but that stopped working. Using "host:192.168.1.10" works, which is the same for WebUI connectivity.
  4. WebUI Not Reachable USing Computer Name

    Perhaps, but I've tested with https://github.com/psychowood/ng-torrent-ui which gives the exact same issues.
  5. WebUI Not Reachable USing Computer Name

    Just upgraded to 3.5.3 build v44996 and experiencing the following: Before upgrading, i could reach uTorrent WebUI: - on LAN via http://computername.local:8080/gui - on LAN via http://192.168.1.10:8080/gui - from outside via http://homeip.net:8080/gui (ports forwarded) After upgrading: - LAN via http://computername.local:8080/gui NOW shows an empty page (nothing in Source View) - on LAN via http://192.168.1.10:8080/gui STILL WORKS - from outside via http://homeip.net:8080/gui (ports forwarded) NOW shows an empty page What the hell kind of network confusion is going on here?