Newfound connection issue.

[Dracul JOSHI]

So, we were playing over fantasy grounds a few times. Now our DM has asked us to switch to the TEST version so that he can use the dynamic lighting. And it worked for everybody but me. When I try to connect to the campaign, it gets stuck at 'Attemtping resolved connection to server'. Usually the password prompt for the campaign should be popping up at this point.

Just to make sure, I double checked that my anti-virus wasn't suddenly blocking the program.

From what I can glance off the logs, the problem appears to be that the socket can't send.

[21/04/2021 03:44:54] Noble Connect [297044]: Sending BIND REQUEST [2f49bc4677d0329d7dcd551f] from [::1]:49767 to [2604:a880:2:d1::19f:9001]:65230
[21/04/2021 03:44:54] Noble Connect [297044]: Socket can not send [::1]:49767 -> [2604:a880:2:d1::19f:9001]:65230
The requested address is not valid in its context.
(AddressNotAvailable - 10049)
[21/04/2021 03:44:54] Noble Connect [297064]: Sending BIND REQUEST [e27aaa247e79620c6449f820] from 127.0.0.1:49768 to 64.227.88.38:64412
[21/04/2021 03:44:54] Noble Connect [297064]: Socket can not send 127.0.0.1:49768 -> 64.227.88.38:64412
A socket operation was attempted to an unreachable network.
(NetworkUnreachable - 10051)

I have tried re-starting the computer, reinstalling the program, updating and most other regular troubleshooting. So any advice here would be appreciated. I can't check the router settings till tomorrow though.

Oh, ehm...
Windows 10
128GB RAM
NVidia GTX 1080
[TEST] v4.1.0 FREE (2021-04-13)

[Moon Wizard]

When reporting connection issues; please include both the GM and player logs, as we need both to determine which side (host/player) is having challenges. The networking engine has not changed between Test and Live (only network message format); so if Live worked, then Test should work.

Since all the other players are able to connect except you, I would guess that some sort of security program or router setting is killing the connection. This is backed up by this entry in the network.log:
[4/21/2021 3:45:04 AM] Noble Connect [306223]: Socket receive operation was interrupted, likely due to the socket being closed

Make sure to check your firewall settings on your machine, as well as your router settings and any Internet provide "advanced settings". Usually in that order.
If it was working on Live, but now fails in Test; then most likely security software on your machine recognizes the new build as a new program, and has assigned new rules for network access.

Regards,
JPG

[LordEntrails]

Note that since the hash values for test and live might be (probably are) different, your security software might block the new (test) version since it is different than the rule you created back when you were on Live. In short, delete and re-create any exceptions and whitelists you have and see if that works.

[Dracul JOSHI]

Nothing's working.

Last idea I have is directly forwarding the port, maybe? Anybody have the port fantasy grounds uses in TEST mode?

[Dracul JOSHI]

So, I just got the logs form my dm (attached assuming I can figure out how to and it appears my connection get there... just doesn't get resolved.



4/27/2021 6:20:07 PM] Noble Connect [4403977]: Received BIND REQUEST [83e5e4433edf7b12eadd9cd8] from 81.221.223.98:32963 at 161.35.236.97:59959
[4/27/2021 6:20:07 PM] Noble Connect [4403977]: Sending BIND SUCCESS_RESPONSE [83e5e4433edf7b12eadd9cd8] from 161.35.236.97:59959 to 81.221.223.98:32963
...
[4/27/2021 6:20:07 PM] Noble Connect [4403977]: No bridge found for peer: 81.221.223.98:32963. This may happen during connection and disconnection, and is safe to ignore. If it happens at other times it may be a bug.
[4/27/2021 6:20:07 PM] Noble Connect [4403978]: No bridge found for peer: 81.221.223.98:32963. This may happen during connection and disconnection, and is safe to ignore. If it happens at other times it may be a bug.
[4/27/2021 6:20:07 PM] Noble Connect [4404483]: No bridge found for peer: 81.221.223.98:32963. This may happen during connection and disconnection, and is safe to ignore. If it happens at other times it may be a bug.

again, it works fine on LIVE... and I checked my router and antivirus multiple times, they aren't blocking ****... at least they aren't told to.

[LordEntrails]

Did you delete your security rules and create new ones?

Did your GM check to see if their ISP offers Advanced Security?

[Dracul JOSHI]

I checked my security rules, they are the same and after switching back to live for testing purposes, I was immediately able to connect to some random. No idea why it ain't working on Test.

[damned]

Be aware that Test uses a different EXE file with the same name but different signature/size. AV that requires whitelisting of the app will need a separate whitelist for TEST too. I know its been said before but it really is worth checking or double-checking.

[LordEntrails]

Hence why I said delete and re-create your security rules. Don't just check that they are there, Delete and re-create. You will have to do this everytime you switch between Live and Test.

[Dracul JOSHI]

It's not that. Aside from the fact that it would block the knock if it was that, I also have checked several times. It looks like it's some difference in the networking codebase of the two compilations. Of course I can't debug this without access to both sourcecodes, but that's not happening and it's unlikely that an update will fix this until tuesday if the responses in this forum is any indication.

I still appreciate the attempt though.... it just sucks to lose a good DnD group to the switch to a program that just refuses to work the way the DM insists it to.

P.S.: It would have helped if you could at least run two installations of this thing side by side with settings for each.

As a software designer, I think something went very wrong on the low level design of the software, trying to get as many top level features running as quickly as possible.

[Moon Wizard]

I'm not sure if I'm following what you're saying completely. You mention something about two separate code bases.

Are you running two different versions, and trying to connect them together?

Regards,
JPG

[Jiminimonka]

It's not that. Aside from the fact that it would block the knock if it was that, I also have checked several times. It looks like it's some difference in the networking codebase of the two compilations. Of course I can't debug this without access to both sourcecodes, but that's not happening and it's unlikely that an update will fix this until tuesday if the responses in this forum is any indication.

I still appreciate the attempt though.... it just sucks to lose a good DnD group to the switch to a program that just refuses to work the way the DM insists it to.

P.S.: It would have helped if you could at least run two installations of this thing side by side with settings for each.

As a software designer, I think something went very wrong on the low level design of the software, trying to get as many top level features running as quickly as possible.

If everyone else is connecting but not you, then it's mostly likely something on your side. Have you asked the DM to provide his FGU logs so you can upload them too as Moon Wizard asked at the top of this thread? Without both logs (yours and the DMs at the time you cant connect) its hard to track down the issue.

EDIT: if this is 4.1 TEST this thread should be moved to the correct section on the forum.

[Dracul JOSHI]

Alright! We managed to resolve the issue last minute!

The solution: Using a server-side VPN. Apparently it was an ISP-located block. Using Windscribe right now because it's free. Though a friendly warning, you may need to switch off the TCP socket cancelling that's build-in. just hit settings, go to connections and switch the "Kill TCP sockets after connection" switch off.

Bonus: I can use about 6-8GB of Geolocked Netflix content a month.

P.S.: I appreciate the attempt at helping me, but your recurring "check the antivirus setting" after it was clear that the knock was passing were not very helpfull.

[Dracul JOSHI]

I did in the 5th post on the first page. That's how I knew the Knock got through but the socket got blocked. (I pointed out the relevant section in the code section)
I just didn't know how to get around that by myself, so I was happy a friend recommended using a VPN for it.