so after further inspection somehow i can load modules in other campaigns, but could this be that it's a public connection?
Printable View
so after further inspection somehow i can load modules in other campaigns, but could this be that it's a public connection?
No, that has no bearing on the situation.
What OS are you and the DM using?
Was this issue resolved?
Any hint on how it was solved?
We're having what seems the exact same issue, and we run out of ideas to debug or fix the issue.
Until two weeks ago, everything worked fine, and no change to our environments for what we know.
Only one player, in two consecutive sessions, couldn't receive files. Or better, it would take 4-5 minutes to do anything, and the logs show how the file was received long after it was requested.
Same things for actions like throwing a dice.
The networks of both the GM and player works fine for other apps
The player tried several things:
- switch to a mobile hotspot from the broadband
- reinstall FGU
- clear the cache
- restart the router and the PC
- disable any antivirus and firewall
- also restarted the GM client several times
The network logs are full of errors. It seems the player's client would keep trying to reconnect, binding the channel, for no apparent reason.
The player logs for example:
And these are some examples of the GM's client:Code:[7/27/2022 9:15:21 PM] Noble Connect [15617]: Socket can not send [::1]:57331 -> [2a03:b0c0:2:f0::ea:c001]:3478
Tentativo di operazione del socket verso una rete non raggiungibile.
....
[7/27/2022 9:15:28 PM] Noble Connect [23340]: Received CREATE_PERMISSION ERROR RESPONSE [19ed8dd1cb886ae399d4cc1e] (401): Unauthorized
....
[7/27/2022 9:15:29 PM] Noble Connect [23816]: Bridge created for peer [[2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511, ] with local endpoint: [127.0.0.1:59269, [::1]:59270]
[7/27/2022 9:15:29 PM] Noble Connect [23830]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
[7/27/2022 9:15:29 PM] Noble Connect [23830]: Received CHANNEL_BIND SUCCESS RESPONSE [7930cc7c769996634a7eb307] from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
[7/27/2022 9:15:29 PM] Noble Connect [23830]: Sending CHANNEL_BIND REQUEST [7fb1dc3532925b88ef5b46c6] from [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:15:29 PM] Noble Connect [23871]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
[7/27/2022 9:15:29 PM] Noble Connect [23871]: Received CHANNEL_BIND SUCCESS RESPONSE [8315fbd065fbc9eef3a6d3e0] from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
[7/27/2022 9:15:29 PM] Noble Connect [23871]: Sending CHANNEL_BIND REQUEST [2fd0e5f48cb903f6f3591b45] from [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:15:29 PM] Noble Connect [23911]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
[7/27/2022 9:15:29 PM] Noble Connect [23911]: Received CHANNEL_BIND SUCCESS RESPONSE [9ebeda583c40e655d6c07469] from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
[7/27/2022 9:15:29 PM] Noble Connect [23912]: Sending CHANNEL_BIND REQUEST [3e173809efbb425add371d7f] from [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:15:29 PM] Noble Connect [23952]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328
Attachment 53774Code:[7/27/2022 9:15:29 PM] Noble Connect [1639426]: Sending CHANNEL_BIND REQUEST [7082309c07bc6c9fc21d3918] from [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:15:29 PM] Noble Connect [1639455]: Adding bridge for peer [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328 and
[7/27/2022 9:15:29 PM] Noble Connect [1639455]: Bridge endpoint: 127.0.0.1:59006
[7/27/2022 9:15:29 PM] Noble Connect [1639455]: Bridge endpoint: [::1]:55289
[7/27/2022 9:15:29 PM] Noble Connect [1639455]: Bridge created for peer [[2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328, ] with local endpoint: [127.0.0.1:59006, [::1]:55289]
[7/27/2022 9:15:29 PM] Noble Connect [1639457]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
[7/27/2022 9:15:29 PM] Noble Connect [1639457]: Received CHANNEL_BIND SUCCESS RESPONSE [7082309c07bc6c9fc21d3918] from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
[7/27/2022 9:15:29 PM] Noble Connect [1639803]: Socket receive operation timed out
[7/27/2022 9:15:29 PM] Noble Connect [1639804]: Socket receive operation timed out
[7/27/2022 9:15:29 PM] [ERROR] Noble Connect [1639804]: Fatal socket exception: Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
at System.Net.Sockets.Socket.ThrowIfDisposedAndClosed () [0x0001b] in <aa976c2104104b7ca9e1785715722c9d>:0
at System.Net.Sockets.Socket.ReceiveFrom (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags, System.Net.EndPoint& remoteEP) [0x00000] in <aa976c2104104b7ca9e1785715722c9d>:0
at NobleConnect.Peer.ReceiveFromApplication (NobleConnect.Bridge bridge, System.Net.Sockets.Socket socket, NobleConnect.PaddedBuffer buffer) [0x00031] in <3ab94fb3bd744147a17d5931f6012cb3>:0
[7/27/2022 9:15:29 PM] [ERROR] Noble Connect [1639804]: Fatal socket exception: Cannot access a disposed object.
Object name: 'System.Net.Sockets.Socket'.
at System.Net.Sockets.Socket.ThrowIfDisposedAndClosed () [0x0001b] in <aa976c2104104b7ca9e1785715722c9d>:0
at System.Net.Sockets.Socket.ReceiveFrom (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags, System.Net.EndPoint& remoteEP) [0x00000] in <aa976c2104104b7ca9e1785715722c9d>:0
at NobleConnect.Peer.ReceiveFromApplication (NobleConnect.Bridge bridge, System.Net.Sockets.Socket socket, NobleConnect.PaddedBuffer buffer) [0x00031] in <3ab94fb3bd744147a17d5931f6012cb3>:0
[7/27/2022 9:15:29 PM] Noble Connect [1639813]: No bridge found for peer: [2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:57328. This may happen during connection and disconnection, and is safe to ignore. If it happens at other times it may be a bug.
....
[7/27/2022 9:15:50 PM] Noble Connect [1660272]: Bridge endpoint: 127.0.0.1:58971
[7/27/2022 9:15:50 PM] Noble Connect [1660272]: Bridge endpoint: [::1]:52524
[7/27/2022 9:15:50 PM] Noble Connect [1660272]: Bridge created for peer [[2a01:e11:3008:8240:b8a0:7479:4bb2:c0ad]:62123, ] with local endpoint: [127.0.0.1:58971, [::1]:52524]
[7/27/2022 9:15:52 PM] Noble Connect [1662379]: Sending REFRESH REQUEST [db1ded795d749b080814e9cd] from [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:15:52 PM] Noble Connect [1662408]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
[7/27/2022 9:15:52 PM] Noble Connect [1662408]: Received REFRESH SUCCESS RESPONSE [db1ded795d749b080814e9cd] from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
[7/27/2022 9:15:59 PM] Noble Connect [1669383]: Sending BIND INDICATION [5991da756845644aed5cc1ed] from 192.168.1.4:57990 to 109.255.33.118:61130
[7/27/2022 9:16:07 PM] Noble Connect [1677408]: Sending REFRESH REQUEST [f1536b9eadb02f1e74027e48] from [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:16:07 PM] Noble Connect [1677437]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
[7/27/2022 9:16:07 PM] Noble Connect [1677437]: Received REFRESH SUCCESS RESPONSE [f1536b9eadb02f1e74027e48] from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
[7/27/2022 9:16:18 PM] Noble Connect [1688559]: Sending BIND INDICATION [ebd739868c6080a960c9ea82] from [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:16:22 PM] Noble Connect [1692438]: Sending REFRESH REQUEST [47d80cbe1a529e8e99228aa9] from [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511 to [2a03:b0c0:2:f0::ea:c001]:3478
[7/27/2022 9:16:22 PM] Noble Connect [1692467]: Handle response from [2a03:b0c0:2:f0::ea:c001]:3478 at [2001:9b1:40fd:ee00:6c6a:60d4:99d2:3f68]:54511
Attachment 53775
We have a network troubleshooting wiki page with suggestions for ideas on how to investigate these scenarios:
https://fantasygroundsunity.atlassia...roubleshooting
The network logs will not be that useful to resolve issues where only content is blocked.
* The lines from the player client network logs are standard when setting up the peer-to-peer connection. Though, they do indicate that the player or GM network routers are so restrictive that it's being forced to use relay servers.
* The lines from the GM log indicate that the connection appears to time out and get dropped; which would indicate that something is closing or blocking the connection in the middle.
This usually indicates that some security software or ISP security router setting is blocking content. It could also be some sort of ad filtering software, packet filtering (such as router SPI firewall), or VPN software as well.
Regards,
JPG
Thanks very much for this.
For future reference, we made many more tests and nothing worked.
Eventually, using a VPN on the player computer, seems to have resolved it.
We don't know the reason, but seems that there is some kind of issue between the connections of the GM in Sweden and the Player in Italy.