FG for Linux not connecting

[loftwyr]

I'm trying to connect to a friend's server, everyone else can connect to but I'm the only one on Linux. It says it's trying to connect and then just sits there until I cancel (I left it trying for 5 minutes once) it never changed. This is my latest try. I just updated to the latest version. I could connect before.

Console.log
[6/1/2022 6:04:44 PM] FGU: v4.2.1 FREE (2022-05-25)
[6/1/2022 6:04:44 PM] OS: Linux 5.15 Ubuntu 22.04 64bit
[6/1/2022 6:04:44 PM] GRAPHICS: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 : 3072
[6/1/2022 6:04:44 PM] UI SCALE: 1
[6/1/2022 6:04:44 PM] USER: loftwyr
[6/1/2022 6:04:44 PM] Launcher scene starting.
[6/1/2022 6:04:47 PM] Resolving named connection to server. [evanm]
[6/1/2022 6:04:47 PM] Attempting resolved connection to server. [104.248.118.207:54885, 2604:a880:400:d0::1968:1:50387]
[6/1/2022 6:04:59 PM] Network setup cancelled by user.
[6/1/2022 6:05:31 PM] NETWORK STATUS: [Error]
[6/1/2022 6:05:31 PM] Launcher scene exiting.

network.log
[6/1/2022 6:04:48 PM] Noble Connect [4178]: Session Candidate: SERVER_REFLEXIVE 174.88.48.191:41196 base: 192.168.50.82:41196 related: 192.168.50.82:41196 => SERVER_REFLEXIVE 99.236.90.203:53978
[6/1/2022 6:04:48 PM] Noble Connect [4178]: Nominated Pair: SERVER_REFLEXIVE 174.88.48.191:41196 base: 192.168.50.82:41196 related: 192.168.50.82:41196 => SERVER_REFLEXIVE 99.236.90.203:53978
[6/1/2022 6:04:48 PM] Noble Connect [4178]: Sending BIND REQUEST [cb025a753a72e5c9570008db] from 192.168.50.82:41196 to 99.236.90.203:53978
[6/1/2022 6:04:48 PM] Noble Connect [4202]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4202]: Received CHANNEL_BIND SUCCESS RESPONSE [56e02c6c9b7a929ed4cbd411] from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4203]: Handle response from 99.236.90.203:53978 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4203]: Received BIND SUCCESS RESPONSE [cb025a753a72e5c9570008db] from 99.236.90.203:53978 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4204]: Selected Pair: SERVER_REFLEXIVE 174.88.48.191:41196 base: 192.168.50.82:41196 related: 192.168.50.82:41196 => SERVER_REFLEXIVE 99.236.90.203:53978
[6/1/2022 6:04:48 PM] Noble Connect [4214]: Sending CHANNEL_BIND REQUEST [a598863195b003034b224d5b] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:48 PM] Noble Connect [4222]: Received BIND REQUEST [e21bc28831ee9f50435bab5f] from 99.236.90.203:53978 at 104.248.118.207:50760
[6/1/2022 6:04:48 PM] Noble Connect [4223]: Sending BIND SUCCESS_RESPONSE [e21bc28831ee9f50435bab5f] from 104.248.118.207:50760 to 99.236.90.203:53978
[6/1/2022 6:04:48 PM] Noble Connect [4235]: Handle response from 104.248.118.207:54885 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4235]: Received BIND SUCCESS RESPONSE [3343db2b4800f247730fbcec] from 104.248.118.207:54885 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4242]: Received BIND REQUEST [44ee15f90825d5d02785463a] from 104.248.118.207:54885 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4242]: Sending BIND SUCCESS_RESPONSE [44ee15f90825d5d02785463a] from 192.168.50.82:41196 to 104.248.118.207:54885
[6/1/2022 6:04:48 PM] Noble Connect [4242]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4242]: Received CHANNEL_BIND SUCCESS RESPONSE [a598863195b003034b224d5b] from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4255]: Sending CHANNEL_BIND REQUEST [c3f16c3eb7d096c6dfb5ced3] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:48 PM] Noble Connect [4281]: Received BIND REQUEST [68b95d226f4cbd578747faf2] from 104.248.118.207:54885 at 104.248.118.207:50760
[6/1/2022 6:04:48 PM] Noble Connect [4281]: Sending BIND SUCCESS_RESPONSE [68b95d226f4cbd578747faf2] from 104.248.118.207:50760 to 104.248.118.207:54885
[6/1/2022 6:04:48 PM] Noble Connect [4283]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4283]: Received CHANNEL_BIND SUCCESS RESPONSE [c3f16c3eb7d096c6dfb5ced3] from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4645]: Received BIND REQUEST [f1ee08569d10e86d71860090] from 99.236.90.203:53978 at 192.168.50.82:41196
[6/1/2022 6:04:48 PM] Noble Connect [4645]: Sending BIND SUCCESS_RESPONSE [f1ee08569d10e86d71860090] from 192.168.50.82:41196 to 99.236.90.203:53978
[2022-06-01 6:04:50 PM] Noble Connect [6122]: Sending CHANNEL_BIND REQUEST [0f509b5699b9fd543389fd98] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:50 PM] Noble Connect [6150]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:50 PM] Noble Connect [6150]: Received CHANNEL_BIND SUCCESS RESPONSE [0f509b5699b9fd543389fd98] from 104.248.118.207:3478 at 192.168.50.82:41196
[2022-06-01 6:04:50 PM] Noble Connect [6162]: Sending CHANNEL_BIND REQUEST [8a09ad6cede69c14c5430e5f] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:50 PM] Noble Connect [6190]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
...snip...
[2022-06-01 6:04:56 PM] Noble Connect [12283]: Sending CHANNEL_BIND REQUEST [f902e2b5e0157ac19a5a672a] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:56 PM] Noble Connect [12311]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:56 PM] Noble Connect [12311]: Received CHANNEL_BIND SUCCESS RESPONSE [f902e2b5e0157ac19a5a672a] from 104.248.118.207:3478 at 192.168.50.82:41196
[2022-06-01 6:04:58 PM] Noble Connect [14122]: Sending CHANNEL_BIND REQUEST [2508fe5d2902682e246ce685] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:58 PM] Noble Connect [14150]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:58 PM] Noble Connect [14150]: Received CHANNEL_BIND SUCCESS RESPONSE [2508fe5d2902682e246ce685] from 104.248.118.207:3478 at 192.168.50.82:41196
[2022-06-01 6:04:58 PM] Noble Connect [14162]: Sending CHANNEL_BIND REQUEST [52490387d539eb7aa0655612] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:58 PM] Noble Connect [14190]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:58 PM] Noble Connect [14190]: Received CHANNEL_BIND SUCCESS RESPONSE [52490387d539eb7aa0655612] from 104.248.118.207:3478 at 192.168.50.82:41196
[2022-06-01 6:04:58 PM] Noble Connect [14242]: Sending CHANNEL_BIND REQUEST [8e516bee284befae7d58caf0] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:58 PM] Noble Connect [14270]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:58 PM] Noble Connect [14270]: Received CHANNEL_BIND SUCCESS RESPONSE [8e516bee284befae7d58caf0] from 104.248.118.207:3478 at 192.168.50.82:41196
[2022-06-01 6:04:58 PM] Noble Connect [14283]: Sending CHANNEL_BIND REQUEST [cd9ae08702118b8bcd5e5953] from 192.168.50.82:41196 to 104.248.118.207:3478
[6/1/2022 6:04:58 PM] Noble Connect [14312]: Handle response from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:58 PM] Noble Connect [14312]: Received CHANNEL_BIND SUCCESS RESPONSE [cd9ae08702118b8bcd5e5953] from 104.248.118.207:3478 at 192.168.50.82:41196
[6/1/2022 6:04:59 PM] Noble Connect [15837]: Sending REFRESH REQUEST [872ad91ad47d237a458a29c8] from 192.168.50.82:41196 to 104.248.118.207:3478

What am I doing wrong?

[Trenloe]

Welcome to the FG forums. Please provide the full logs. Details on how to compile the logs can be found here: https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1242136781/How+to+Compile+Logs

[LordEntrails]

Make sure you are running the same minor version as the host. i.e. if the host is on 4.2.1, you also need to be on 4.2.x. If they are on 4.1.x and you are on 4.2.x (or vice versa) you will not be able to connect. The version is shown on the tp right corner of the launch screen. If that is not the issue, the full logs will help us point you in the right direction.

[loftwyr]

We were all on the same latest version. My full logs:

[Moon Wizard]

The logs you posted just show that the GM ("evanm") is not currently running a cloud game.

[6/1/2022 9:10:32 PM] Resolving named connection to server. [evanm]
[6/1/2022 9:10:32 PM] Cloud server with the requested name is not registered with the lobby server.

Please note that the logs are only available for the current session, plus the last session; where session means each time you start Fantasy Grounds.

Regards,
JPG

[Moon Wizard]

Also, have you tried connecting to any other FG games from your machine?
And, are other users able to connect to the GM's machine?

Regards,
JPG

[loftwyr]

Yes, all the other players could connect. I'll ask the GM to start up the server and get a fresh set of logs.

[loftwyr]

Fresh connection attempt for fresh logs

[loftwyr]

It's the same with every other server I try.

[Moon Wizard]

If everyone else can connect to the GM, and you are running into same issue connecting to any server, and we aren't hearing reports of any Linux connection issues; my guess is that something on your machine or network router is blocking the connection from completing.

We have seen similar issues in the past with certain network configurations, where machine or router filters/firewalls will block the connection if certain files transferred will trigger the block, or throttling will kick in due to the burst traffic in an initial connection.

Since this sort of networking issues are very unique to each machine and local network, we have created a wiki article to look into common scenarios.
https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1981349889/Network+Troubleshooting

Also, trying another machine on the same network would be useful.

Regards,
JPG

[loftwyr]

I have, my window laptop could connect. I'll check the wiki page