-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-local Player recieving 903, despite others not getting this error. #516
Comments
Would need more information here.
Wireshark logs would actually be super helpful here to see what their client is doing, but unless you know what you're doing there, the above might be enough to figure out the issue by itself. |
I have some idea on how to use wireshark, but I would not know what filters to use to make sure a lot of the "noise" isn't included. |
If this is the case, would need some wireshark logs to find out what is going on, or perhaps increase verbosity of the server logs in config.json if it's literally giving you nothing (I'll be honest I'm not sure which would help here, I would guess For Wireshark, it's just a case of booting it up, then scanning the network as the user is connecting, stop it, then sort by source/destination and look for your IP address to see what is being sent. I will admit I once had an issue where external users were being sent the local address, so I just changed the local address to be the same as the external address as I was running off a VPS, and that worked. Not sure if this would help here. |
I had him install Wireshark, but he is technologically illiterate, so I will have to walk him through it. |
Describe the bug
Exactly as described in the title.
Occasionally we can get them past the Patch screen, but he also gets Full Server errors... again, despite other players being able to play.
To reproduce
Fill in steps to reproduce the behavior, such as:
Game version(s) (choose one or more of the following):
BB
Server log output
Server outputs the following when the player attempts to connect, with no extra log output:
Additional context
None.
The text was updated successfully, but these errors were encountered: