On the way of giving up. Requesting authentication - retrying - requesting...

[speaR]

Good evening guys, I'm having some realy bad issues with my server.

After 1 hour or a bit more it is nearly impossible to join our server.

The thing is like this:

Players getting to. Requesting authentication. This changes with retrying to autenthicate

.. After a time the message appears: you must be close to a rock or an ore to mine.

This is my basic.cfg

MinBandwidth=15360000;
MaxBandwidth=2147483647;
MaxMsgSend=512;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=256;
MinErrorToSendNear=0.029999999;
MinErrorToSend=0.0040000002;
MaxCustomFileSize=0;
Windowed=0;
adapter=-1;
3D_Performance=1;
Resolution_Bpp=32;
serverLongitude=9;
serverLatitude=51;
serverLongitudeAuto=9;
serverLatitudeAuto=51;

I'm ranning a dedi box on win 2008 server. Intel xeon server processor, 16gig ram and a 1 GB connection. Does anyone have an idea how to deal with this ?

Already tried to set down the slots to 40, a bit better but still annoying. The problem appears with 37 up to 50 players..

 

[cen]

MaxMsgSend=192;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=192;
MinErrorToSendNear=0.047000002;
MinErrorToSend=0.0040000002;
MaxCustomFileSize=0;
Windowed=0;
adapter=-1;
3D_Performance=1;
Resolution_W=800;
Resolution_H=600;
Resolution_Bpp=32;

[Defent]

I've found that removing:

MaxMsgSend=512;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=256;

Has increased performance and stability. Try that.

[speaR]

MaxMsgSend=192;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=192;
MinErrorToSendNear=0.047000002;
MinErrorToSend=0.0040000002;
MaxCustomFileSize=0;
Windowed=0;
adapter=-1;
3D_Performance=1;
Resolution_W=800;
Resolution_H=600;
Resolution_Bpp=32;

Should i replace my whole basic with this

MaxMsgSend=192;
MaxSizeGuaranteed=512;
MaxSizeNonguaranteed=192;
MinErrorToSendNear=0.047000002;
MinErrorToSend=0.0040000002;
MaxCustomFileSize=0;
Windowed=0;
adapter=-1;
3D_Performance=1;
Resolution_W=800;
Resolution_H=600;
Resolution_Bpp=32;

or just the ones which u gave me ?

 

and thanks for the fast answers :-)

[cen]

Replace the entire basic.cfg with what I pasted.

[Vindomire]

are you using the right EXE??? is it a dedicated server? i know i had this issue with my test server on my home PC because the .bat file pointed to the wrong .exe so the server was starting an old version of beta instead of newest.

[speaR]

yes I do. Not using the beta exe anymore

[Nicko Godsun]

a file within your pbo is messed up.. i had same problem.. when installing infistar reread the instructions.. it says "or" so either use top or bottom

[speaR]

still having the problems..

[Defent]

Open config.cfg

 

Delete

requiredSecureId = 2;

and comment out or delete

//regularCheck = "{}";

I got these suggetions from MGT and they seem to have stopped some of the authentication issues. 

Among other things, I also tweaked my basic.cfg to this:

 

 

Note that maxbandwith is set for a 1gb connection. Going above that is sort of over-kill. Especially since you probably have a 1gb connection at most.

MinBandwidth=1097152;
MaxBandwidth=1073741824;
MinErrorToSendNear=0.049999997;
MinErrorToSend=0.0029999993;
MaxCustomFileSize=0;
Windowed=0;
adapter=-1;
3D_Performance=1;
Resolution_Bpp=32;
Resolution_W=800;
Resolution_H=600;

And cleared the character_data table when the steam patch came.

[speaR]

ok thank you ! I'll try this stuff out. If it won't work after that.. Could i messed up something in my server pbo or in my mission file what causes this ?

[cen]

[iNFO] Server admins should add requiredSecureId = 2; to their server.cfg to prevent uid spoofing.

 

Why should that be removed when epoch devs suggest it?

[Defent]

I don't recommend removing it, I just suggest that removing it may have solved some of the authentication issues.  

[ekroemer]

Now on one of our servers we're getting this problem, too.

 

The interesting thing is: in the 2 cases I saw this today the players died, and couldn't reconnect from the lobby into the game.

When I set their character to alive, they joined instantly (during the "requesting authentication" - "retrying to autenthicate" loop.

 

Problems with creation of a new character? Why would this be?

 

Edit: player load is not the problem, only 2 people on the server at that time, normally running smoothly with 30.

 

Edit2: Found it: A DB trigger to update Plotpole-ID had pointed to another DB (copy&Paste error ;-), thus preventing new characters from being created.

[Ped]

I get this problem fairly often on Survival Servers. Figured it's the host and not the server or client. This issue always happens immediately following a server restart. The first player to try logging in will have a full authenticate cycle and time out. It usually goes through fine on the second try, just click ok in the lobby to rejoin.