Demo Player wants to join the game, loading screen is stuck on "acquiring file list"

[Jaesman151]

We are having this issue as well. I just downloaded updates, my DM has Unity ultimate monthly subscription, my settings have my account info. Using cloud public entered password etc. The Acquiring File List frame doesnt show any progress after 10+ minutes.

[Relampago]

Given the state of the Unity client I recommend that everyone press update before they launch their client and attempt to connect even the DM. I know i am just a neophyte here but this happened to us and cleared up yesterday after our clients updated yesterday. Good luck!

[LordEntrails]

Given the state of the Unity client I recommend that everyone press update before they launch their client and attempt to connect even the DM. I know i am just a neophyte here but this happened to us and cleared up yesterday after our clients updated yesterday. Good luck!

Very good advice. As of last night (for me) there had been 4 updates to FGU in less than 2 days.

Remember, this is beta software and is being updated frequently, so always update

[beurhou]

Hello ,

I have the same issue, i try all what you say but nothing happen. Do you have a solution please ? i have a session this night but we are blocked for the moment

Thx for your help

[Relampago]

Beurhou as recommended earlier in the thread paste your change.log file from the DM and one client with the issue.

[Moon Wizard]

Yes, please. I need to logs from both the GM and the player on any failed connections.

Regards,
JPG

[JulianS]

We had exactly the same issue. Demo account players were stuck on "acquiring file list" and couldn't join even though they were displayed as connected in the GM account. One exception: I (the GM) joined the session with another demo account from within the same wireless network. This worked without incident. The logs are below:


GM log:
[26.03.2020 23:11:24] Noble Connect [808614]: Sending REFRESH REQUEST [0c4423066d1ca600c4c9c137] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:11:24] Noble Connect [808640]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:11:24] Noble Connect [808640]: Received REFRESH SUCCESS RESPONSE [0c4423066d1ca600c4c9c137] from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:11:27] Noble Connect [811919]: Sending BIND INDICATION [745ba5c2be7b227815445a1f] from 192.168.178.31:56012 to 77.191.124.27:50474
[26.03.2020 23:11:54] Noble Connect [838615]: Sending REFRESH REQUEST [cbc94410c3a6893592ea5594] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:11:54] Noble Connect [838715]: Sending REFRESH REQUEST [cbc94410c3a6893592ea5594] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:11:54] Noble Connect [838715]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:11:54] Noble Connect [838715]: Received REFRESH SUCCESS RESPONSE [cbc94410c3a6893592ea5594] from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:11:54] Noble Connect [838741]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:12:02] Noble Connect [846206]: Sending BIND INDICATION [758bbdd9c3f6a4142d83f280] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:12:24] Noble Connect [868615]: Sending REFRESH REQUEST [53c399064b896d144f24a3fc] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:12:24] Noble Connect [868641]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:12:24] Noble Connect [868641]: Received REFRESH SUCCESS RESPONSE [53c399064b896d144f24a3fc] from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:12:54] Noble Connect [898616]: Sending REFRESH REQUEST [45e6a1ae910b53dfcbc72f80] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:12:54] Noble Connect [898641]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:12:54] Noble Connect [898641]: Received REFRESH SUCCESS RESPONSE [45e6a1ae910b53dfcbc72f80] from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:12:55] Noble Connect [899580]: Sending BIND INDICATION [a6024d20a82f37afd3384576] from 192.168.178.31:56012 to 192.168.178.37:58800
[26.03.2020 23:13:13] Noble Connect [917883]: Sending BIND INDICATION [77fe90db93d105144deec3d1] from 192.168.178.31:56012 to 77.191.124.27:50469
[26.03.2020 23:13:24] Noble Connect [928616]: Sending REFRESH REQUEST [90d9695f0efad004579fafae] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:13:24] Noble Connect [928644]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:13:24] Noble Connect [928644]: Received REFRESH SUCCESS RESPONSE [90d9695f0efad004579fafae] from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:13:24] Noble Connect [928719]: Sending BIND INDICATION [1f074caaf62d6b50f005a836] from 192.168.178.31:56012 to 77.191.124.27:50474
[26.03.2020 23:13:54] Noble Connect [958617]: Sending REFRESH REQUEST [ae148c5f56d86a73c0c13a87] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:13:54] Noble Connect [958642]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:13:54] Noble Connect [958642]: Received REFRESH SUCCESS RESPONSE [ae148c5f56d86a73c0c13a87] from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:13:58] Noble Connect [963006]: Sending BIND INDICATION [da290ed3eb6e919abd1492d4] from 192.168.178.31:56012 to 128.199.60.165:3478
[3/26/2020 11:14:17 PM] Campaign saved.
[26.03.2020 23:14:24] Noble Connect [988617]: Sending REFRESH REQUEST [a8d192ac3d8de6065063876f] from 192.168.178.31:56012 to 128.199.60.165:3478
[26.03.2020 23:14:24] Noble Connect [988643]: Handle response from 128.199.60.165:3478 at 192.168.178.31:56012
[26.03.2020 23:14:24] Noble Connect [988643]: Received REFRESH SUCCESS RESPONSE [a8d192ac3d8de6065063876f] from 128.199.60.165:3478 at 192.168.178.31:56012

Player log:
[26.03.2020 21:43:05] Noble Connect [367209]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:43:05] Noble Connect [367209]: Received REFRESH SUCCESS RESPONSE [d2a46f0c07ac76adabb8cbd9] from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:43:35] Noble Connect [397149]: Sending REFRESH REQUEST [62e92519349e88230e999fd2] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:43:35] Noble Connect [397249]: Sending REFRESH REQUEST [62e92519349e88230e999fd2] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:43:35] Noble Connect [397294]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:43:35] Noble Connect [397294]: Received REFRESH SUCCESS RESPONSE [62e92519349e88230e999fd2] from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:43:35] Noble Connect [397350]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:44:05] Noble Connect [427149]: Sending REFRESH REQUEST [4d7df081706797e0ffb72e36] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:44:05] Noble Connect [427201]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:44:05] Noble Connect [427201]: Received REFRESH SUCCESS RESPONSE [4d7df081706797e0ffb72e36] from 128.199.60.165:3478 at 192.168.1.15:55406
[3/26/2020 9:44:05 PM] Unexpected command (CHINR) received on client while downloading.
[3/26/2020 9:44:08 PM] Unexpected command (CHINR) received on client while downloading.
[26.03.2020 21:44:35] Noble Connect [457149]: Sending REFRESH REQUEST [06bc2bfcbd94e9f6f08556a5] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:44:35] Noble Connect [457227]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:44:35] Noble Connect [457227]: Received REFRESH SUCCESS RESPONSE [06bc2bfcbd94e9f6f08556a5] from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:44:56] Noble Connect [477573]: Sending BIND INDICATION [cb1ad94da86741882f34743b] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:44:59] Noble Connect [480935]: Sending BIND INDICATION [c5e7122a9d2cce80ff0ebfcb] from 192.168.1.15:55406 to 82.207.239.31:3131
[26.03.2020 21:45:05] Noble Connect [487150]: Sending REFRESH REQUEST [ff895868c7d60aad0195e2f5] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:45:05] Noble Connect [487235]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:45:05] Noble Connect [487235]: Received REFRESH SUCCESS RESPONSE [ff895868c7d60aad0195e2f5] from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:45:35] Noble Connect [517150]: Sending REFRESH REQUEST [d4ba0eabb1e77eddbf67e429] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:45:35] Noble Connect [517216]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:45:35] Noble Connect [517216]: Received REFRESH SUCCESS RESPONSE [d4ba0eabb1e77eddbf67e429] from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:46:05] Noble Connect [547163]: Sending REFRESH REQUEST [2e656170728eecd5eed4993f] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:46:05] Noble Connect [547231]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:46:05] Noble Connect [547231]: Received REFRESH SUCCESS RESPONSE [2e656170728eecd5eed4993f] from 128.199.60.165:3478 at 192.168.1.15:55406
[3/26/2020 9:46:22 PM] Unexpected command (CHINR) received on client while downloading.
[26.03.2020 21:46:35] Noble Connect [577163]: Sending REFRESH REQUEST [27eca30ea8682f6ffeb45c1b] from 192.168.1.15:55406 to 128.199.60.165:3478
[26.03.2020 21:46:35] Noble Connect [577232]: Handle response from 128.199.60.165:3478 at 192.168.1.15:55406
[26.03.2020 21:46:35] Noble Connect [577232]: Received REFRESH SUCCESS RESPONSE [27eca30ea8682f6ffeb45c1b] from 128.199.60.165:3478 at 192.168.1.15:55406

[Moon Wizard]

I just pushed a build today (about an hour ago) which should help reduce this sort of situation, while we continue to investigate the root cause.

Regards,
JPG

[horsburghn]

I had this exact same issue which I have managed to resolve as follows.

On my computer I had both the original and the Unity versions of Fantasy Grounds. I uninstalled the original version and then the Unity version connected without any issues at all. As a player I have no port forwarding. I run Zonealarm and, after accepting that Fantasy Grounds required internet access, it has worked fine.

Hope that this helps.

[Juzzinodda]

I'm facing this exact issue but it doesn't seem like a solution was found in this thread. Any advice. Thanks! Running Catalina with Ultimate and trying to connect demo players.