Connection state changed: k_ESteamNetworkingConnectionState_Connecting

[wooolly]

I'm trying to replace my uage of Tugboat with Fishy Steamworks so that I can fully utilise Steam's offering. However, I'm having trouble getting a connection between my hosted server and my local client in Unity.

I've got the server listed on the Steam Game Server list just fine, and we're getting the details of the server fine (correct client ID, port number assigned by Edgegap), but when I go to connect, it changes state...
Connection state changed: k_ESteamNetworkingConnectionState_Connecting
but then doesn't proceed beyond that, and my server doesn't acknowledge any connection attempt.

I think it's something to do with ports, and Fishy Steamworks not using them correctly? As whenever I go to connect, it says
Local client is starting for FishySteamworks. Server IP is , port is 0.

But it's not 0, it's port 30999 (in that instance when I tested, but it can be any port Edgegap assigns).

Why is Fishy Steamworks struggling to recognise the port I'm assigning? I've checked in the inspector and the port is correct that I passed to StartConnection(SteamId, Port) as the inspector is displaying the correct Client Address and Port.

Perhaps it's a server issue, as again Fishy Steamworks struggles to identify the ports I'm using.
Local server is starting for FishySteamworks. Listening on port 0.

However, it's only Fishy Steamworks, as everything else is correctly identifying the ports I wish (and need) to use.

For instance, when starting steam, it seems to be initializing with the correct ports...
Initializing Steam Game Server API: (0, 30999, 32636, eServerModeAuthenticationAndSecure, 0.3.120)

[FirstGearGames]

This may have been an issue just discovered and resolved by Loden of Heathen. Let me know if release 4.1.1 fixes this for you; it's coming out in a moment.