Port isn't saved.

[Wizardling]

G'day, in the last few betas of µTorrent the port I set is not saved and I have to reset it to the port I've opened in my router each time I run µTorrent.

I'm on a mid-2007 24" iMac running OSX 10.5.5. Current version of µTorrent is 0.9.0.2.

[thelittlefire]

Port # is stored in settings.dat . . . are you using NAT-PMP/UPnP ? Are you randomizing the port? How do you close uT/Mac

[Wizardling]

No, I've manually opened and forwarded a port in my router. I'm not randomising. Even weirder - just opened µTorrent to doublecheck I hadn't and this time it's port was zero *blink* Before it was like randomisation was stuck on. Now it's picking bad numbers.

As for quitting µTorrent - I just go Command-Q or uTorrent->Quit as per normal. I'm not sure what else I'd do :-)

In ~/Library/Application Support/uTorrent/settings.dat this is all I see when I open it in a text editor:

d10:.fileguard40:21827294C9267CA7640176FA8A8CC20FF7150D4430:bt.no_connect_to_services_list16:25,110,6666,666717:check_update_betai1e3:cid24:

[NoOneButMe]

Can you back your preferences up (both in App Support/uTorrent and ~/Library/Preferences/com.bittorrent.utorrent.plist) and see if you can reproduce the bug again?

[gigantoid]

I have the same problem. It will not save the port number. It also wouldn't recognize the port as being open. However after restarting it selected a port (20856) which it seems to remember but says connection status unavailable as it should. When changing to the open port it did not initially recognize it as being open. It all of a sudden started working.

I use transmission on this port without issues.

Also quitting takes a very long time.

[Wizardling]

Deleting my µTorrent's app support folder fixed this for me.

[alen1989]

Same problem here, and deleting App Support folder didn't fix it. But it seems that it has selected it'w own port (it's not randomizing, as it seems) and I just forwarded it. It works fine now, even if it doesn't let me set my own port

[TG]

@alen1989: are you on a G based Cpu?

If so it is a bug with the PowerPC binary.... it will get fixed soon.