How to fix "Failed to connect to server"

[cdelorme]

So I decided to update an old project.

The server is running fine, the map and char servers connect, the chat and login servers connect.

It took a while, but I finally have a client I can launch.

When I try to connect to the server the login server shows the logs:

    login     | [Status]: Request for connection of record (ip: 172.16.24.1)
    login     | [Notice]: Authentication accepted (account: record, id: 2000000, ip: 172.16.24.1)
    login     | [Status]: Connection of the account 'record' accepted.
    login     | [Info]: Closed connection from '172.16.24.1'.

The client takes a moment then says "Failed to connect to server".

Very clearly it connected, since it was even able to create an account when I used the `_M/_F` name format.

I have no further insight as to what is going wrong.

I am using the 20180621A client, configured and hexed as documented.

Anyone have any clue what step(s) I am missing to get a working client/server pair?

[sader1992]

make sure the packet version is current

make sure the ports are open

make sure the ip of each program

like this

conf/import/char_conf.txt
login_ip: 127.0.0.1
char_ip: public_ip
conf/import/map_conf.txt
char_ip: 127.0.0.1
map_ip: public_ip

make sure to check your clientinfo xml file

check your subnet config

 

and

Edited October 14, 2019 by sader1992

[chatterboy]

2 hours ago, cdelorme said:

So I decided to update an old project.

The server is running fine, the map and char servers connect, the chat and login servers connect.

It took a while, but I finally have a client I can launch.

When I try to connect to the server the login server shows the logs:

    login     | [Status]: Request for connection of record (ip: 172.16.24.1)
    login     | [Notice]: Authentication accepted (account: record, id: 2000000, ip: 172.16.24.1)
    login     | [Status]: Connection of the account 'record' accepted.
    login     | [Info]: Closed connection from '172.16.24.1'.

The client takes a moment then says "Failed to connect to server".

Very clearly it connected, since it was even able to create an account when I used the `_M/_F` name format.

I have no further insight as to what is going wrong.

I am using the 20180621A client, configured and hexed as documented.

Anyone have any clue what step(s) I am missing to get a working client/server pair?

i think rathena is the default up-to 2018-06-20 packet, try to change it then recompile... or use my ragEXE ^_^

2018-06-20eRagexeRE_patched.exe

Edited October 14, 2019 by chatterboy

[cdelorme]

I did search the community, and triple checked at least 3 pages worth of suggestions before posting.

I think it's safe to rule out connection problems that may be the result of IP's, subnets, firewalls, etc...

I did consider the subnet since I created a virtual network `172.16.24.0/28`

I tried overriding `conf/subnet_rathena.conf` with these lines:

    subnet: 255.255.255.240:172.16.24.1:172.16.24.1
    subnet: 255.0.0.0:127.0.0.1:127.0.0.1

This changed nothing.

I have thoroughly tested the networking of the project.

I even have an extended version that loads up two character servers and multiple map servers.

I can ping the docker containers by IP from my host machine.

The client was able to create an account.

This means it established a persistent TCP connection, sent a packet, and the login server processed it.

Every subsequent attempt also shows a log message saying the connection was successfully authenticated.

I fail to see how that would occur if the IP or subnet configuration was invalid.

I compiled with the 20180621 packetver, since it gets used via numerical comparison I am assuming adding the letter suffix won't help.

I read that the `<version>55</version>` inside the `sclientinfo.xml` is no longer used, so that would be unrelated correct?

Regarding compatible versions, where is the latest supported documented?

• In a September discussion someone suggested using 2018-06-21a.
• This discussion says 20180621 and older back in January.
• Another discussion in January saying it is better to use 2018-06-21.
• In March a discussion specifically claiming 2018-06-21a is the recommended compatible client.
• This discussion mentions support for the 20180621aRE client in April.
• Another discussion mentions 20180621a is supported in April.
• The documentation for zackdreaver's translation lists 20180621a as compatible.

I didn't just pick 2018-06-21a for no reason, there was plenty of evidence to suggest it was compatible.

However, I am happy to switch to the 2018-06-20 version if that is truly the latest compatible version.

[chatterboy]

i tried to download that 2018-06-21aRagexe i think its infected. in a few seconds after download it its auto delete 

i download it from here >> http://nemo.herc.ws/downloads/2018-06-21aRagexe/ that's why its better use 2018-06-20eRagexeRE ^_^

Edited October 14, 2019 by chatterboy

[cdelorme]

I didn't use nemo.herc.ws because they don't have the RE version listed in their downloads page, meaning they don't have a copy.

I found two locations with a download for 2018-06-21a:
https://drive.google.com/file/d/16VhFbvirHAmiQbiUde7oLE1XPcu1DSsi/view

https://mega.nz/#!Zcdk2C4L!z9SkS36VGhJWAaxD9cRf1sVhgC9I6gMm0k6Cld-lYOQ

I also found a link for 2018-06-20e from this discussion:

After recompiling the 2018-06-21a client is working.

I am checking to see how the wrong version got used, but I believe my issue is resolved.
Thank you for your help.

 

Edit: Confirmed, my mistake was in the docker-compose syntax; it provides environment variables that get passed, but only to the running container, not to a build.  As a result it was using the old default in the Dockerfile that I had not updated.  To correct it I had to add ARG properties and shift the parameter in the docker-compose file.  Mostly adding this for self reflection.