Cant connect to anyone

[Ram My Rump]

Hi,

Recently as of today/yesterday (23/04/2020), I've been getting errors when attempting to connect to someone on Fantasy Grounds Unity. Normally I'm able to connect to my DM no worries, so theres no issue there, but now I can't connect to him, or anyone else who has a public game open. I asked my DM if he could connect to anyone else who has a public game open at the time and he could, and I could not.

When I connect to someone I get an error. I have the log of what happened:

[4/23/2020 7:17:35 PM] FGU v4.0.0 FREE (2020-04-17)
[4/23/2020 7:17:35 PM] Launcher scene starting.
[4/23/2020 7:36:42 PM] Resolving named connection to server. [cingrao]
[4/23/2020 7:36:42 PM] Attempting resolved connection to server. [68.183.117.123:54701]
[23/04/2020 7:36:42 PM] [<color="red">ERROR</color>] NETWORK: Noble Connect [1147917]: Fatal socket error: Fault
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowD elayedException () [0x00014] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at System.Net.Sockets.Socket.EndReceiveFrom (System.IAsyncResult asyncResult, System.Net.EndPoint& endPoint) [0x0003b] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at NobleConnect.Stun.Controller.AsyncReceive (System.IAsyncResult result) [0x00004] in <7a36d7bc4e4142a1b7353e0b7ebee2af>:0
[23/04/2020 7:36:42 PM] [<color="red">ERROR</color>] NETWORK: Noble Connect [1147934]: Fatal socket error: Fault
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowD elayedException () [0x00014] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at System.Net.Sockets.Socket.EndReceiveFrom (System.IAsyncResult asyncResult, System.Net.EndPoint& endPoint) [0x0003b] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at NobleConnect.Stun.Controller.AsyncReceive (System.IAsyncResult result) [0x00004] in <7a36d7bc4e4142a1b7353e0b7ebee2af>:0
[4/23/2020 7:36:46 PM] [<color="red">ERROR</color>] NETWORK: Noble Connect [1151010]: Shutting down because of a fatal error: Failed to connect to relay server
[4/23/2020 7:36:46 PM] Fatal network engine error occurred. [Failed to connect to relay server]


NETWORK LOG

I also have the network log here too



[4/23/2020 7:36:42 PM] Noble Connect [1147862]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147866]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147866]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147866]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147867]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147867]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147872]: Found host candidate: HOST ([2001:8004:c82:aca2:1448:214c:809a:b410]:58905)
[4/23/2020 7:36:42 PM] Noble Connect [1147872]: Found host candidate: HOST ([2001:8004:c82:aca2:5491:6756:872e:6e88]:58906)
[4/23/2020 7:36:42 PM] Noble Connect [1147872]: Found host candidate: HOST ([fe80::1448:214c:809a:b410%12]:58907)
[4/23/2020 7:36:42 PM] Noble Connect [1147872]: Found host candidate: HOST (172.20.10.8:58908)
[4/23/2020 7:36:42 PM] Noble Connect [1147872]: Found host candidate: HOST ([::1]:58909)
[4/23/2020 7:36:42 PM] Noble Connect [1147872]: Found host candidate: HOST (127.0.0.1:58910)
[4/23/2020 7:36:42 PM] Noble Connect [1147879]: Sending ALLOCATE REQUEST [9b89e32d22601b76f8320fe7] from [2001:8004:c82:aca2:1448:214c:809a:b410]:58905 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:42 PM] Noble Connect [1147884]: No free buffers, adding one
[4/23/2020 7:36:42 PM] Noble Connect [1147905]: Sending ALLOCATE REQUEST [81b0d94ade888c0d8aa20605] from [2001:8004:c82:aca2:5491:6756:872e:6e88]:58906 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:42 PM] Noble Connect [1147905]: No free buffers, adding one
[23/04/2020 7:36:42 PM] [ERROR] Noble Connect [1147917]: Fatal socket error: Fault
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowD elayedException () [0x00014] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at System.Net.Sockets.Socket.EndReceiveFrom (System.IAsyncResult asyncResult, System.Net.EndPoint& endPoint) [0x0003b] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at NobleConnect.Stun.Controller.AsyncReceive (System.IAsyncResult result) [0x00004] in <7a36d7bc4e4142a1b7353e0b7ebee2af>:0
[4/23/2020 7:36:42 PM] Noble Connect [1147926]: Sending ALLOCATE REQUEST [bb739b25339d29e8f2ae2611] from [fe80::1448:214c:809a:b410%12]:58907 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:42 PM] Noble Connect [1147926]: No free buffers, adding one
[23/04/2020 7:36:42 PM] [ERROR] Noble Connect [1147934]: Fatal socket error: Fault
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowD elayedException () [0x00014] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at System.Net.Sockets.Socket.EndReceiveFrom (System.IAsyncResult asyncResult, System.Net.EndPoint& endPoint) [0x0003b] in <ae22a4e8f83c41d69684ae7f557133d9>:0
at NobleConnect.Stun.Controller.AsyncReceive (System.IAsyncResult result) [0x00004] in <7a36d7bc4e4142a1b7353e0b7ebee2af>:0
[4/23/2020 7:36:42 PM] Noble Connect [1147947]: Sending ALLOCATE REQUEST [8e97c5ea86dc81a6dfba1e40] from 172.20.10.8:58908 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:42 PM] Noble Connect [1147947]: No free buffers, adding one
[4/23/2020 7:36:43 PM] Noble Connect [1147968]: Sending ALLOCATE REQUEST [04fb25ad3ad6b5a48fb5e788] from [::1]:58909 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:43 PM] Noble Connect [1147968]: No free buffers, adding one
[4/23/2020 7:36:43 PM] Noble Connect [1147989]: Sending ALLOCATE REQUEST [4ea80ba254c232ca1c95616f] from 127.0.0.1:58910 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:43 PM] Noble Connect [1147989]: No free buffers, adding one
[23/04/2020 7:36:43 PM] Noble Connect [1148079]: Sending ALLOCATE REQUEST [9b89e32d22601b76f8320fe7] from [2001:8004:c82:aca2:1448:214c:809a:b410]:58905 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148105]: Sending ALLOCATE REQUEST [81b0d94ade888c0d8aa20605] from [2001:8004:c82:aca2:5491:6756:872e:6e88]:58906 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148126]: Sending ALLOCATE REQUEST [bb739b25339d29e8f2ae2611] from [fe80::1448:214c:809a:b410%12]:58907 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148147]: Sending ALLOCATE REQUEST [8e97c5ea86dc81a6dfba1e40] from 172.20.10.8:58908 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148168]: Sending ALLOCATE REQUEST [04fb25ad3ad6b5a48fb5e788] from [::1]:58909 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148189]: Sending ALLOCATE REQUEST [4ea80ba254c232ca1c95616f] from 127.0.0.1:58910 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148479]: Sending ALLOCATE REQUEST [9b89e32d22601b76f8320fe7] from [2001:8004:c82:aca2:1448:214c:809a:b410]:58905 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148505]: Sending ALLOCATE REQUEST [81b0d94ade888c0d8aa20605] from [2001:8004:c82:aca2:5491:6756:872e:6e88]:58906 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148526]: Sending ALLOCATE REQUEST [bb739b25339d29e8f2ae2611] from [fe80::1448:214c:809a:b410%12]:58907 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148548]: Sending ALLOCATE REQUEST [8e97c5ea86dc81a6dfba1e40] from 172.20.10.8:58908 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148569]: Sending ALLOCATE REQUEST [04fb25ad3ad6b5a48fb5e788] from [::1]:58909 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:43 PM] Noble Connect [1148590]: Sending ALLOCATE REQUEST [4ea80ba254c232ca1c95616f] from 127.0.0.1:58910 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:44 PM] Noble Connect [1149280]: Sending ALLOCATE REQUEST [9b89e32d22601b76f8320fe7] from [2001:8004:c82:aca2:1448:214c:809a:b410]:58905 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:44 PM] Noble Connect [1149306]: Sending ALLOCATE REQUEST [81b0d94ade888c0d8aa20605] from [2001:8004:c82:aca2:5491:6756:872e:6e88]:58906 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:44 PM] Noble Connect [1149327]: Sending ALLOCATE REQUEST [bb739b25339d29e8f2ae2611] from [fe80::1448:214c:809a:b410%12]:58907 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:44 PM] Noble Connect [1149348]: Sending ALLOCATE REQUEST [8e97c5ea86dc81a6dfba1e40] from 172.20.10.8:58908 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:44 PM] Noble Connect [1149369]: Sending ALLOCATE REQUEST [04fb25ad3ad6b5a48fb5e788] from [::1]:58909 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[23/04/2020 7:36:44 PM] Noble Connect [1149390]: Sending ALLOCATE REQUEST [4ea80ba254c232ca1c95616f] from 127.0.0.1:58910 to [2001:8004:11d0:4e2a::368:4ab4]:3478
[4/23/2020 7:36:46 PM] [ERROR] Noble Connect [1151010]: Shutting down because of a fatal error: Failed to connect to relay server


Does anyone know what this issue is and how it is fixed? Thanks

[damned]

Can you try re-entering your username/password in settings?

[Ram My Rump]

I've tried restarting fantasy grounds about half a dozen times, re-entered my username and password every time.

Also, for extra clarification, I'm playing on a free account if that matters at all.

[Ram My Rump]

bump

[pollux]

It looks like your FGU client is having trouble connecting to the lobby server (aka the relay server in the logs). Some things to investigate:


Try again. The lobby server has actually be down for short periods recently. You said your DM could connect to another game while you were having trouble, so this seems unlikely... but make ABSOLUTELY sure you weren't just swept up in a transient outage of the lobby server.
Update Fantasy Grounds Unity and have your DM do the same. I'm not aware of a situation that would cause old clients to fail to reach the lobby server, but they're working on networking actively and if they change something in the beta they generally just require you be on the latest release and don't wory about backwards-compat.
Is YOUR internet in good shape? Reboot your router if in any doubt at all.
There are some ISPs that mess with connections. Comcast XFinity is known to be especially bad. Can you connect from a cell connection? I know many areas are self-isolating, but can you connect via a neighbors wifi? Do you have a VPN? Anything to connect from a different ISP or encapsulate the FGU traffic so your ISP can't break it.
Is your DM in cloud game mode or "lan" mode? I don't THINK this would prevent you from connecting to the lobby server, but depending on when the issue is happening it might be worth double-checking this.

[Ram My Rump]

It looks like your FGU client is having trouble connecting to the lobby server (aka the relay server in the logs). Some things to investigate:


Try again. The lobby server has actually be down for short periods recently. You said your DM could connect to another game while you were having trouble, so this seems unlikely... but make ABSOLUTELY sure you weren't just swept up in a transient outage of the lobby server.
Update Fantasy Grounds Unity and have your DM do the same. I'm not aware of a situation that would cause old clients to fail to reach the lobby server, but they're working on networking actively and if they change something in the beta they generally just require you be on the latest release and don't wory about backwards-compat.
Is YOUR internet in good shape? Reboot your router if in any doubt at all.
There are some ISPs that mess with connections. Comcast XFinity is known to be especially bad. Can you connect from a cell connection? I know many areas are self-isolating, but can you connect via a neighbors wifi? Do you have a VPN? Anything to connect from a different ISP or encapsulate the FGU traffic so your ISP can't break it.
Is your DM in cloud game mode or "lan" mode? I don't THINK this would prevent you from connecting to the lobby server, but depending on when the issue is happening it might be worth double-checking this.


1. I've been trying about once every hour or so to login over this whole period, no luck unfortunately. I originally thought it was that but it doesn't seem to be the case.

2. I've updated FGU and my DM did the same, he can connect and I still cant connect to any game at all, public or private.

3. I've tried switching between my home wifi and my phone wifi, both have been able to connect before as far as I remember. I've reset both and nothing unfortunately, still getting the same error message.

4. I'm with Telstra (I'm in Australia), and they're pretty decent most of the time, just a bit pricey but they're all that's around my area really. As I stated previously, I've tried on both my phone and home wifi. There's no neighbours wifi to connect to either. No VPNs either. Nothing as far as I can tell is stopping the connection.

5. Yeah, my DM has been putting the games on cloud mode the whole time.

[pollux]

If you've reproduced the issue at various times and from two internet providers (cell and home)... that brings me back to Damned advice about making sure your account credentials are in good shape, but you say you've done that too.

[Ram My Rump]

Yeah, I've logged out and in quite a few times, no luck.

It's an interesting problem to say the least.

[Sulimo]

Yeah, I've logged out and in quite a few times, no luck.

It's an interesting problem to say the least.

You could try the following:
Open a Command prompt and type (without the ") "tracert connect.noblewhale.com" and post the results. Guessing you are on Windows from the errors that were shown, however, if you are on macOS the command is "traceroute connect.noblewhale.com" from the Terminal.


I am not a dev, but it seems like something might be up with the networking stack from the log you posted.

Checking for newer Network Drivers for your network device can't hurt, check for any outstanding Windows Updates (what version of Windows are you on?).


If the above does not help, I would probably suggest uninstall/reinstall Fantasy Grounds fresh.

If you have any data you wish to save prior to uninstalling, click the Folder icon in the upper left corner of the launcher to see if there is anything you might want to save (custom modules, extensions, etc.). Otherwise, make sure you clear out any older data after uninstalling.

Download the latest installer to reinstall. (https://www.fantasygrounds.com/home/FantasyGroundsUnity.php)

[Ram My Rump]

I'm on Windows 10.

I've tried the command prompt, and these were the results:

Tracing route to connect.noblewhale.com [2001:8004:11d0:4e2a::368:4ab4]
over a maximum of 30 hops:

1 2 ms 3 ms 1 ms 2001:8004:1be0:6521:be30:d9ff:febd:aae8
2 * * * Request timed out.
3 27 ms 18 ms 24 ms 2001:8004:2c42:24:7:e1c0:0:1
4 23 ms 24 ms 24 ms 2001:8004:2c42:0:7:e1c0:0:a8d2
5 27 ms 21 ms 22 ms 2001:8004::7:e1c0:0:a
6 27 ms 27 ms 28 ms 2001:8004::7:e1c0:0:c
7 21 ms 26 ms 25 ms 2001:8004:11d0:4e2a::cb36:b5bd
8 25 ms 27 ms 20 ms 2001:8004:11d0:4e2a::cb32:bae
9 26 ms 36 ms 24 ms 2001:8004:11d0:4e2a::cb1b:b03a
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 56 ms 24 ms 29 ms 2001:8004:11d0:4e2a::96de:70e3
14 24 ms 27 ms 26 ms 2001:8004:11d0:4e2a::96de:70e6
15 32 ms 28 ms 28 ms 2001:8004:11d0:4e2a::345f:2549
16 25 ms 31 ms 32 ms 2001:8004:11d0:4e2a::36f0:c0fd
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 42 ms 28 ms 28 ms 2001:8004:11d0:4e2a::368:4ab4

Trace complete.

Ran it a few times but got roughly the same results.

I've tried seeing if there was any updates for my Network Drivers, couldn't find anything at all. Windows is all up to date.

I've reinstalled Fantasty Grounds Unity brand new and fresh, this seemed to do nothing as well.

[pollux]

I find it interesting that your tracert is using ipv6 addresses. Do you have ipv4 connectivity as well? As an experiment, if you disable ipv6 does it change things?

[Ram My Rump]

I've got no clue what those are

[pollux]

I've got no clue what those are

Probably not wise to mess with then, I'm not sure it would help and I could imagine a scenario where messing around with it kills your internet if you're not clear exactly what you're doing and why.

Your tracert is showing network address types that are uncommon in the US. I wonder if there's an issue when running on top of IPv6. I have no evidence to suggest that, and it's not trivial for me to test. If someone else has experienced IPv6 problems (or can confirm that it works with no problems), maybe they'll pipe up now that fact has been highlighted, though.

[Sulimo]

I doubt IPv6 is the issue, IPv4 vs. 6 really should not make that much difference.

I noticed the IPv6 addresses in his log (::1 is the local loop back for IPv6). He is in Australia, so not that unlikely he might be getting IPv6 from his ISP.

It looks like the tracert is completing (even though some of the hops are failing).

I haven’t really troubleshot IPv6, like Pollux mentioned, it is not all that common in the US yet.

I’m out of ideas, unless the issue is IPv6 for some odd reason, but I imagine there are quite a few users in AUS and they don’t seem to be having issues.

I’d let a dev respond when they have a chance, maybe the logs you posted will tell them something.

Best bet is to see the sticky post about what to provide them, and email support@ to get the info to them.

[pollux]

I doubt IPv6 is the issue, IPv4 vs. 6 really should not make that much difference.

This is a weird thing to say. It's incredibly common for applications that aren't tested on IPv6 to fail when used with it. Hard-coding invalid assumptions about IPv4 address-formatting has been like a national sport among US-based developers for years, and sadly people still do it today until they get caught out. One would HOPE that Smiteworks and/or their network library vendor is on top of IPv6 support and that it works fine, but it definitely CAN make a difference and frequently does in non-browser based applications that handle their own networking.

[Sulimo]

This is a weird thing to say. It's incredibly common for applications that aren't tested on IPv6 to fail when used with it. Hard-coding invalid assumptions about IPv4 address-formatting has been like a national sport among US-based developers for years, and sadly people still do it today until they get caught out. One would HOPE that Smiteworks and/or their network library vendor is on top of IPv6 support and that it works fine, but it definitely CAN make a difference and frequently does in non-browser based applications that handle their own networking.


There have been some other users posting screen shots with IPv6 addresses that were able to connect just fine, so it does work for some people. That is why I do not think that is the root cause here, but it is possible.

[pollux]

There have been some other users posting screen shots with IPv6 addresses that were able to connect just fine, so it does work for some people. That is why I do not think that is the root cause here, but it is possible.

Ah, I stand corrected. I hadn't seen those and thought you were making a general statement about IPv6 being pretty much like IPv4 and not likely to cause an issue. If you've seen others reporting success with IPv6, then you have more detailed info than I.

[Ram My Rump]

Bumping because this still isnt solved

[Moon Wizard]

I'm not sure what's causing the error, as that error is coming from inside the base .Net library used by our programming language and then into a network library we licensed.

I think the first question I would have to try and help was whether you have any special network setup or network security, and are you using a VPN?

Regards,
JPG

[Ram My Rump]

Im using a good old standard connection, using either my phone for wifi, my modem wifi, or just straight ethernet cable.'

I dont use VPNs

[Ram My Rump]

Bumping for visibility

[Ram My Rump]

Bump. Im still having the same issue. Been a week so far

[damned]

If you would like me to have a look at this remotely with you send me your email address by PM.

[Ram My Rump]

Yeah no worries