-
March 26th, 2020, 04:17 #1
- Join Date
- Dec 2017
- Posts
- 2
Can't connect to campaign, but everyone in my group can
Everyone in my group can connect to the campaign in FG Unity, except me. I'm getting the error " Authorization failed: The host is running an unauthorized copy, or authorization server is down" even after putting in the proper pasword. I've tried allowing FG through the firewall. Here is the error in my console log in my app data folder. Any ideas as to how to fix this so I can connect?
-
March 26th, 2020, 07:03 #2
Have you entered your forum username and password in the FGU settings?
Problems? See; How to Report Issues, Bugs & Problems
On Licensing & Distributing Community Content
Community Contributions: Gemstones, 5E Quick Ref Decal, Adventure Module Creation, Dungeon Trinkets, Balance Disturbed, Dungeon Room Descriptions
Note, I am not a SmiteWorks employee or representative, I'm just a user like you.
-
March 26th, 2020, 09:06 #3
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,561
@mcsherman18,
In the future, if you can copy and paste your log information directly into your post, it would help me decode it quicker. Also, I can not see the full text of the error without a copy and paste, so I'm not sure what the exact error is for your case.
From what I can guess and look up online, it looks like perhaps you have the proxy setting turned on for your Internet, but no proxy server specified. Again, I'm just guessing based on what I can see.
You can try these steps to try and fix: (They may be different for different versions of Windows. I'm running Windows 10.)
1. Type "Internet Options" in your Windows bar, and open the Internet Options Control Panel.
2. Click Connections tab
3. Click LAN Settings
4. Uncheck the box for "Use a proxy server for your LAN" if it is checked.
5. Click OK twice to save.
Regards,
JPG
-
April 1st, 2020, 03:33 #4
-
April 27th, 2020, 03:53 #5
- Join Date
- Apr 2020
- Posts
- 2
I am having the same issue as OP. Everyone else in my party can connect to the game when it's open except for me. I'm using a 2019 MacBook Air, and I've been able to use Roll20 without any problems for years. This is my first time trying to use FGU. I believe everything is installed correctly and I update FGU every time I've started it. Here is a copy of the error logs if anyone can make sense of it?
There is a password, and I've entered it correctly. When I try to join the game, it says "no way dude, not without a password!" so I enter the password and hit retry. Then I get the ERROR Noble Connect and "no local endpoint". Is this a Mac thing? Or something with my network? Any help would be immensely appreciated.
(went over the character limit, so I cut the log lines before the errors)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: No free buffers, adding one
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (127.0.0.1:62708) => HOST (10.0.0.8:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (127.0.0.1:62708) => HOST (127.0.0.1:63379)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (192.168.7.59:52762) => HOST (10.0.0.8:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (192.168.7.59:52762) => HOST (127.0.0.1:63379)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (127.0.0.1:62708) => SERVER_REFLEXIVE (67.244.139.177:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (192.168.7.59:52762) => SERVER_REFLEXIVE (67.244.139.177:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (127.0.0.1:62708) => RELAYED (68.183.117.123:59773)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: HOST (192.168.7.59:52762) => RELAYED (68.183.117.123:59773)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: RELAYED (68.183.117.123:60440 => 192.168.7.59:52762) => HOST (10.0.0.8:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: RELAYED (68.183.117.123:60440 => 192.168.7.59:52762) => HOST (127.0.0.1:63379)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: RELAYED (68.183.117.123:60440 => 192.168.7.59:52762) => SERVER_REFLEXIVE (67.244.139.177:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26555]: Local Candidate: RELAYED (68.183.117.123:60440 => 192.168.7.59:52762) => RELAYED (68.183.117.123:59773)
[4/26/2020 10:38:14 PM] Noble Connect [26568]: Handle response from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26568]: Received CHANNEL_BIND SUCCESS RESPONSE [2e548dbc562b76af59a2277e] from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26574]: Handle response from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26574]: Received CHANNEL_BIND SUCCESS RESPONSE [822d26b8d210618a49b82381] from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26576]: Handle response from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26576]: Received CHANNEL_BIND SUCCESS RESPONSE [c3df71ba96e1e3d91621786e] from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26576]: Sending BIND REQUEST [d994bd7c3d71f38cfd816c0a] from 127.0.0.1:62708 to 10.0.0.8:63378
[4/26/2020 10:38:14 PM] Noble Connect [26576]: Handle response from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26576]: Received CHANNEL_BIND SUCCESS RESPONSE [8d491e9d4a8e8eaf21d8d3c5] from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26596]: Sending BIND REQUEST [b62a7b1a67c6aaec963b90fd] from 127.0.0.1:62708 to 127.0.0.1:63379
[4/26/2020 10:38:14 PM] Noble Connect [26616]: Sending BIND REQUEST [33519e78d6da787bd1b9df37] from 192.168.7.59:52762 to 10.0.0.8:63378
[4/26/2020 10:38:14 PM] Noble Connect [26636]: Sending BIND REQUEST [3e3796a53a2b5f9f74eda962] from 192.168.7.59:52762 to 127.0.0.1:63379
[4/26/2020 10:38:14 PM] Noble Connect [26656]: Sending BIND REQUEST [d75e4d775f604ee9c8d75ae0] from 127.0.0.1:62708 to 67.244.139.177:63378
[4/26/2020 10:38:14 PM] Noble Connect [26676]: Sending BIND REQUEST [ebf4b1fa71f04f584685b418] from 192.168.7.59:52762 to 67.244.139.177:63378
[4/26/2020 10:38:14 PM] Noble Connect [26696]: Sending BIND REQUEST [d5e4b9a4f61cb28fb36f6f05] from 127.0.0.1:62708 to 68.183.117.123:59773
[4/26/2020 10:38:14 PM] Noble Connect [26717]: Sending BIND REQUEST [1035d8b2e96f21384cc1f3cf] from 192.168.7.59:52762 to 68.183.117.123:59773
[4/26/2020 10:38:14 PM] Noble Connect [26736]: Received BIND REQUEST [f7a1bc237e459e387b51a0be] from 67.244.139.177:63378 at 68.183.117.123:3478
[4/26/2020 10:38:14 PM] Noble Connect [26736]: Sending BIND SUCCESS_RESPONSE [f7a1bc237e459e387b51a0be] from 192.168.7.59:52762 to 67.244.139.177:63378
[4/26/2020 10:38:14 PM] Noble Connect [26737]: Sending BIND REQUEST [92db9adfde1650bafe3bdff3] from 192.168.7.59:52762 to 67.244.139.177:63378
[4/26/2020 10:38:14 PM] Noble Connect [26737]: Handle response from 67.244.139.177:63378 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26737]: Received BIND SUCCESS RESPONSE [ebf4b1fa71f04f584685b418] from 67.244.139.177:63378 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26738]: Session Candidate: HOST (192.168.7.59:52762) => SERVER_REFLEXIVE (67.244.139.177:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26738]: Selected Pair: HOST (192.168.7.59:52762) => SERVER_REFLEXIVE (67.244.139.177:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26738]: Sending BIND REQUEST [43a55c5ed9c39ca3cc0b1878] from 192.168.7.59:52762 to 67.244.139.177:63378
[4/26/2020 10:38:14 PM] Noble Connect [26801]: Handle response from 67.244.139.177:63378 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26801]: Received BIND SUCCESS RESPONSE [43a55c5ed9c39ca3cc0b1878] from 67.244.139.177:63378 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26801]: Connecting via route: HOST (192.168.7.59:52762) => SERVER_REFLEXIVE (67.244.139.177:63378)
[4/26/2020 10:38:14 PM] Noble Connect [26807]: Handle response from 67.244.139.177:63378 at 68.183.117.123:3478
[4/26/2020 10:38:14 PM] Noble Connect [26807]: Received BIND SUCCESS RESPONSE [92db9adfde1650bafe3bdff3] from 67.244.139.177:63378 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26808]: Received BIND REQUEST [8d246e45e794ff34eac9e4df] from 68.183.117.123:59773 at 68.183.117.123:3478
[4/26/2020 10:38:14 PM] Noble Connect [26808]: Sending BIND SUCCESS_RESPONSE [8d246e45e794ff34eac9e4df] from 192.168.7.59:52762 to 68.183.117.123:59773
[4/26/2020 10:38:14 PM] Noble Connect [26809]: Received BIND REQUEST [dc534394d4a78449b4929564] from 68.183.117.123:59773 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26809]: Sending BIND SUCCESS_RESPONSE [dc534394d4a78449b4929564] from 192.168.7.59:52762 to 68.183.117.123:59773
[4/26/2020 10:38:14 PM] Noble Connect [26809]: Handle response from 68.183.117.123:59773 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26809]: Received BIND SUCCESS RESPONSE [1035d8b2e96f21384cc1f3cf] from 68.183.117.123:59773 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26813]: Adding bridge for peer 67.244.139.177:63378 with client end point: 127.0.0.1:52817
[4/26/2020 10:38:14 PM] Noble Connect [26848]: Received BIND REQUEST [6c53738ef2abc39f99ebff71] from 67.244.139.177:63378 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [26848]: Sending BIND SUCCESS_RESPONSE [6c53738ef2abc39f99ebff71] from 192.168.7.59:52762 to 67.244.139.177:63378
[4/26/2020 10:38:14 PM] Noble Connect [27022]: Sending REFRESH REQUEST [37a9935f788fa63a4ad7f1f8] from 192.168.7.59:52762 to 68.183.117.123:3478
[4/26/2020 10:38:14 PM] [ERROR] Noble Connect [27024]: No local endpoint
[4/26/2020 10:38:14 PM] [ERROR] Noble Connect [27032]: No local endpoint
[4/26/2020 10:38:14 PM] Noble Connect [27040]: Handle response from 68.183.117.123:3478 at 192.168.7.59:52762
[4/26/2020 10:38:14 PM] Noble Connect [27040]: Received REFRESH SUCCESS RESPONSE [37a9935f788fa63a4ad7f1f8] from 68.183.117.123:3478 at 192.168.7.59:52762
-
April 30th, 2020, 01:42 #6
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,561
I'm not familiar with that error message; but it's being returned by the network library we use to facilitate network connections.
Are you using any VPNs by any chance? (for work or otherwise)
Regards,
JPG
-
April 30th, 2020, 16:48 #7
- Join Date
- Apr 2020
- Posts
- 2
Hey, thanks for the reply Moon Wizard.
I was not using any VPNs, just a vanilla WiFi connection to a cable router/modem (RCN ISP, Eero equipment) I was using a 2019 MacBook Air, which is my personal computer so I don't use it for work at all.
I have since installed FGU on my wife's laptop and I've been able to connect using that. Unfortunately, it is a 6-year old Vizio PC, so it tends to overheat when running FGU. We're on the same network using the same router etc. so I didn't know if this was a Mac issue? I'd still prefer to be able to use my computer, but at least the older Windows PC is working as a stopgap.
-
May 1st, 2020, 07:54 #8
Supreme Deity
- Join Date
- Mar 2007
- Posts
- 20,561
Thanks for the additional details, indiebass. You never know which details are the ones that might lead to figuring out an issue. I've forwarded the additional detail to the developer that provides the network library to see if they have any ideas.
Regards,
JPG
-
May 6th, 2020, 03:01 #9
- Join Date
- Mar 2020
- Posts
- 5
I've got the same issue, but this didn't work for me. Nothing has as of yet worked (My OP is in another thread) no matter what I've tried. I'm going to repost here my issue and pray for help.
[5/5/2020 7:58:14 PM] FGU v4.0.0 ULTIMATE (2020-04-23)
[5/5/2020 7:58:14 PM] Launcher scene starting.
[5/5/2020 7:58:28 PM] Resolving named connection to server. [Siriomir]
[5/5/2020 7:58:28 PM] Attempting resolved connection to server. [167.99.162.76:59688]
[5/5/2020 7:58:32 PM] Attempting authorization. [Washu - DIRECT]
[5/5/2020 7:58:32 PM] Authorization failed: The host has protected the session with a password. Please retry with correct password.
[5/5/2020 7:59:13 PM] Resolving named connection to server. [Siriomir]
[5/5/2020 7:59:13 PM] Attempting resolved connection to server. [167.99.162.76:59688]
[5/5/2020 7:59:16 PM] Attempting authorization. [Washu - DIRECT]
It only ever rarely gets past this point. BUT I can (and do) connect to any non-passworded server and have no issue whatsoever. My host (Siriomir) has no issue with anyone else connecting to him either, just me.
-
May 7th, 2020, 05:58 #10
- Join Date
- Apr 2020
- Posts
- 4
Players can't join my game I'm hosting with my Ultimate license. Everything has been working fine, my players seem to just get stuck at Attempting resolved connection to server.
Edit: Wanted to add that all of us are fully updated to v4.0.0, advanced security is turned off, the port has been forwarded from FGC.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks