each time my friend attempts to join my server, he keeps getting stuck on “start”. i’ve confirmed my mods aren’t broken because other friends of mine were able to join no problem. it’s weird, i hope someone can solve my problem. i don’t know if this is a client or server error so i’m putting it in both.
Hi Frail! Sorry for the delay in a response, when this issue happens does your friend have any error codes showing in the command window that comes up with BeamMP? If not do you know if this friend can join other servers?
If they can’t join any other servers then it could mean that their computer is blocking incoming or outgoing traffic from BeamNG/BeamMP. Ask them to check their firewall settings and ensure that all BeamNG and BeamMP Processes are allowed through.
1 Like
Hello my friend. We found out the issue, he had no storage left to download the mods. We resolved the issue 
1 Like
My friend is stuck on the “Start” screen as well when joining my modded server (Using AssettoHosing). He’s pre installed all the mods, messed with his firewall and all the other port related things but he’s still getting stuck on “Start”
When he preinstalled the mods did he preinstall them in the normal mod folder or did he install them on the BeamMP mod folder.
There’s a different mod folder?
Yes, anything installed in the normal, single player, mod folder needs to be disabled or you are going to get the stuck on start issue. BeamMP can’t run unless it is the only enabled clientside mod.
To install mods to BeamMP they go in ummm
Shoot, one second, sorry I’m not at my main computer
C>Users>Appdata>Roaming. . …uhhh. . .BeamMP>Resources? Or something similar. . .
C:\Users<User>\AppData\BeamMP-Launcher\Resources
That’s the one hahaha
C:\Users\<User>\AppData\Roaming\BeamMP-Launcher\Resources
thats the one 
He’s still getting stuck on start when loading into the server even after doing all that
Also in the launcher it says failed to close socket. Any more ways to fix that?
I wouldn’t worry about “failed to close socket”.
You could try renaming your beamNG userfolder and try with a clean beamNG: