The server didn't respond. Retrying..
#1

Hello,
If I restart my server I cannot reconnect ingame, there are still the following messages:
Quote:

[11:10:11] The server is restarting..
[11:10:11] Connecting to 127.0.0.1:7777...
[11:10:24] The server didn't respond. Retrying..
[11:10:24] Connecting to 127.0.0.1:7777...
[11:10:34] The server didn't respond. Retrying..
[11:10:34] Connecting to 127.0.0.1:7777...
[11:10:44] The server didn't respond. Retrying..
[11:10:44] Connecting to 127.0.0.1:7777...
[11:10:54] The server didn't respond. Retrying..
[11:10:54] Connecting to 127.0.0.1:7777...
[11:11:04] The server didn't respond. Retrying..
[11:11:04] Connecting to 127.0.0.1:7777...
[11:11:15] The server didn't respond. Retrying..
[11:11:15] Connecting to 127.0.0.1:7777...
[11:11:25] The server didn't respond. Retrying..

If I go to the desktop and then back ingame, I am connected. If I don't go to desktop and back, I would reconnect unlimited times.
Quote:

[11:11:25] Connecting to 127.0.0.1:7777...
[11:11:25] Connected. Joining the game...

Server log:
Quote:

[02/03/13 11:10:34] Incoming connection: 127.0.0.1:61914
[02/03/13 11:10:44] Incoming connection: 127.0.0.1:61918
[02/03/13 11:10:54] Incoming connection: 127.0.0.1:61921
[02/03/13 11:11:05] Incoming connection: 127.0.0.1:61925
[02/03/13 11:11:15] Incoming connection: 127.0.0.1:61928
[02/03/13 11:11:25] Incoming connection: 127.0.0.1:61932

This bug is new in 0.3x. In 0.3e I had the problem that I was fake-banned, but in 0.3x I reconnect.

Greets
Reply
#2

0.3x probably has had its security protocols updated and tightened up and rightfully so. In order to avoid problems with more and more bad people trying to make bots and attack servers.

I think your issue can be lightened by restarting the server properly by using gmx as ****** pointed out when 0.3x first came into release candidate phase.

Good luck
Reply
#3

Experiencing the same problem when I restart my local server, I also heard about some getting random disconnects
Reply
#4

Confirmed.
You must close exe program, and reopen.
Reply
#5

I restart the server by clicking the "X" of the console.
Are there other opportunities? If I do /rcon exit the client is closed, that I have to restart the client.
Reply
#6

You're supposed to restart your server with the gmx command, not by closing the server console window. That's what causes this. If you gmx the server, you won't have this issue.
Reply
#7

Testing your script while scripting in 0.3x has become 60% slower due to this

I need to close the samp-server.exe PLUS my GTA : SA because that is FASTER than waiting for it to finally connect to the server, I hope a minor patch could be made for this :/ atleast ignore 127.0.0.1 it's a local server why would we cause harm to it

I was used to just close and re-open samp-server and bam instant reconnect just incase you did not understand me.

EDIT:
THANKS REALCOP I will test it
Reply
#8

Talking from experience, I'd rather spend a little bit more time testing (or implement testing as a development phase in the first place ) than spend countless time trying to get rid of malicious bots!
Reply
#9

Quote:
Originally Posted by RealCop228
Посмотреть сообщение
You're supposed to restart your server with the gmx command, not by closing the server console window. That's what causes this. If you gmx the server, you won't have this issue.
Okay, thanks. But that's a bit annoying, because then the server saves all data and that takes a long time.
Reply
#10

The GMX thing works perfect

Atrox95 define somewhere if its test or live then stop saving things when in test
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)