Starfinder Playlist
Page 2 of 30 First 123412 ... Last
  1. #11
    After uninstall and reinstall, I updated and created a test campaign again. I downloaded Advanced Port Scanner to my host PC directly. Ran a port scan on my local IP address for port 1802 with the LAN test campaign open and it does not find Port 1802 open. If I open my FGC campaign and run the same scan, then it does find TCP 1802 open. I hope that helps.

  2. #12

    Connection issues - "acquiring files" stuck; player/GM log and campaign files

    Hello, two players have been trying to join a GM's game for the last two days. Both get stuck at "acquiring files" (we've let it run for 30+ minutes). We've gone through all available troubleshooting steps, including simultaneous full reinstalls. A friendly mod on discord tried joining the GM's campaign, and he managed to join with no problem. The two players have been able to join OTHER games (including a game that the GM said HIS friends were unable to join...). But never the specific game our GM is hosting.

    I've attached my player logs (player-console.log), my GM's log (gm-console.log), GM's campaign file (mythical_magic_mushrooms_quests.zip), and the log from my successful connection to another GM's game (success-console.log)

    Any help super appreciated; we're very excited to use FG (and I can't wait to find out what happens in the mythical magic mushroom quest...)
    .Sean
    Attached Files Attached Files

  3. #13
    I tried again just now, and the console.log looks different, including "unexpected command (DIESR) received on client while downloading". (attached)

    .Sean
    Attached Files Attached Files

  4. #14
    So I continually kept locking up. Before today, and last week we were at least able to connect and play. After the server lobby finally came back up. Every time people logged on or tried to log on, it would kick from matchmaker server. Eventually GM screen just locks up and doesn't respond, waited for over 10 minutes. Tried for over an hour before we decided to give up.



    Gm: I think the first attachment

    Players:
    https://pastebin.com/Reawmfz5
    Attached Files Attached Files
    Last edited by Copernicus219; March 29th, 2020 at 21:03.

  5. #15
    Quote Originally Posted by Hamidgeabee View Post
    I am having the same issues trying to use the cloud. I tried to do a LAN game and just have everyone use my public IP since I already have port 1802 forwarded in my router for FGC games. When I use the open port check tool that was recommended for troubleshooting connection issues on https://www.fantasygrounds.com/forum...faq=networking it says that the connection times out. If I open FGC, the connection is successful. I know the router and computer settings are correct since it can connect on FGC. I have also duplicated any setting for FGC in my Bitdefender and Windows Firewall for FGU. I am going to try uninstalling my FGU and reinstalling with a newer installer since mine was installed in late October. Maybe I have an older bug that didn't patch correctly. I'll keep you posted on the new install. I also deleted the AppData folders after I uninstalled.
    Verify windows firewall isn't blocking. Had to fix this today for someone.

  6. #16
    FWIW, all of our players are experiencing "Attempting resolved connection to server." error today. Campaign is started on server type cloud and server list public with a simple pw to access.

    Thanks... I know you all are jamming through this fix as fast as is possible.

    R

  7. #17
    New player here. Just purchased fantasygrounds yesterday, and I've gotten it up and running on my computer, but none of my players can join. They are stuck on the "Acquiring File List" screen, and they can't do anything else (and my computer slows down, sometimes making the computer not respond). I sent a PM with more details and the files. Any help is greatly appreciated.

  8. #18
    Hamidgeabee, did you switch to UDP instead of TCP when forwarding the port Unity uses UDP instead of TCP for port forwarding.

  9. #19
    Hosting Pathfinder 1e:

    Just attempted to connect:

    [3/30/2020 11:32:09 AM] Noble Connect [73616]: Received REFRESH SUCCESS RESPONSE [663c1c066826077fdbeda100] from 68.183.117.123:3478 at 192.168.1.69:62834
    [3/30/2020 11:32:39 AM] Noble Connect [103674]: Sending REFRESH REQUEST [d6c3b36d0e15c6730d873cf7] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:32:40 AM] Noble Connect [104073]: Sending REFRESH REQUEST [d6c3b36d0e15c6730d873cf7] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:32:40 AM] Noble Connect [104073]: Handle response from 68.183.117.123:3478 at 192.168.1.69:62834
    [3/30/2020 11:32:40 AM] Noble Connect [104073]: Received REFRESH SUCCESS RESPONSE [d6c3b36d0e15c6730d873cf7] from 68.183.117.123:3478 at 192.168.1.69:62834
    [3/30/2020 11:32:59 AM] [WARNING] Lost connection to matchmaking server : Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
    .
    [3/30/2020 11:33:06 AM] Noble Connect [130388]: Sending BIND INDICATION [38e8e67ede97dd7f173a2203] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:09 AM] Noble Connect [133674]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:09 AM] Noble Connect [133775]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:10 AM] Noble Connect [134398]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:11 AM] Noble Connect [135202]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:12 AM] Noble Connect [136027]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:13 AM] Noble Connect [137669]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:17 AM] Noble Connect [141058]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:23 AM] Noble Connect [147458]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:37 AM] Noble Connect [161092]: Sending REFRESH REQUEST [fcc1e92dd8f6c6d6bfb6bebd] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:39 AM] Noble Connect [163775]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:40 AM] Noble Connect [163875]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:40 AM] Noble Connect [164075]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:41 AM] Noble Connect [165215]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:43 AM] Noble Connect [166845]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:44 AM] Noble Connect [168446]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:48 AM] Noble Connect [172172]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:33:55 AM] Noble Connect [179290]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:34:03 AM] [WARNING] Noble Connect [187313]: Lost an allocation: 192.168.1.69
    [3/30/2020 11:34:03 AM] [<color="red">ERROR</color>] Noble Connect [187617]: Shutting down because of fatal error: Lost connection to relay server
    [3/30/2020 11:34:04 AM] Fatal network engine error occurred. [Lost connection to relay server]
    [3/30/2020 11:34:04 AM] [<color="red">ERROR</color>] Game server connection was lost. Please return to launcher, and start game again.
    [3/30/2020 11:34:08 AM] Noble Connect [192090]: Sending REFRESH REQUEST [9db86e735bc2d4961cabb214] from 192.168.1.69:62834 to 68.183.117.123:3478
    [3/30/2020 11:34:33 AM] [WARNING] Noble Connect [217690]: Lost an allocation: 192.168.1.69

  10. #20
    Any news on when Fantasy Grounds will be playable again?

    Could list the errors that started this weekend, but sure you know them all. In short: players cannot connect and it has been tested on multiple computers (real computers not Windows computers ) and on multiple networks.

    Same errors as the others on Noble connect, server timeout, program crashing, stuck on "acquiring files", randomly get access but then no characters to pick etc. etc. etc.

    Really hoping that you get to a stable version again, that then isn't being tampered with until after Corona is over so we can use our own backup (actually meeting people).

    Very best

    Jens

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
DICE PACKS BUNDLE

Log in

Log in