System Error

[AaronzitoBr]

So,I'm trying to connect with the WAN IP on my VPS "164.68.110.164". On my Vbox/local PC it was just fine, but now I can't pass the "System Error" message while trying to login in the game.

I have changed the ips from ffaccount > worlds to:



ffdb1 > serverstatus to:



My Setup.ini Configuration:



TicketServer > Setup.ini:

TicketServerIP=164.68.110.164
TicketServerPort=7777

Then I have patched the LoginServer, MissionServer, WorldServer and ZoneServer with AKTools V1 (V2 and V3 can't connect anymore). I tried it with Aura Kingdom Server Patch from CGI too. Put my IP and clicked on PATCH. The put it on the folders on hxsy in VPS. My iptables are disabled too. I'm using CentOS 6.10.

My logs: Attachment 165971
Attachment 165970
Attachment 165969
Attachment 165968
Can anybody tell me what I'm doing wrong or help me via Discord/Skype? =(

My VPS will expire in 7 days (its a vps I was using to host another mmorpg server, but that is closed now). I'm trying to make it work so I can learn how to make it on VPS =(

[MentaL]

[sankeeye]

setup.ini need 127.0.0.1

GameDBIP=127.0.0.1
GameDB=ffdb1
GameDBUser=postgres
GameDBPassword=
Language=X
Locate=US
LogFile=Test.log
AccountDBIP=127.0.0.1
AccountDBName=ffaccount
AccountDBUser=postgres
AccountDBPW=
TicketServerIP=127.0.0.1
TicketServerPort=18624
BillingGatewayIP=127.0.0.1
BillingGatewayPort=5560
BillingGatewayPaymentIP=127.0.0.1
BillingGatewayPaymentPort=5560
BillingGatewayWorldIP=127.0.0.1
BillingGatewayWorldPort=5560
PlayerRoomWorldID=1010

and gatewayserver must be the ip of the vps

I also use one vps

[AaronzitoBr]

Solved!

Just changeg the ip from Setup.ini to 127.0.0.1 and leave the ext_Address with the public IP.
Them edit the version of WorldServer101 and 102, plus put the WAN IP on it again

[pierreninja]

Good evening, I am with the same mistake did the steps that the friend above did unsuccessfully can anyone help me?

[joaodoido1111]

same error

[3unni]

If you're still having this issue,please go back and check the numid or tb_user in the database as the ID may have changed for you. This will cause the error. Changing it back to match the ID in accounts will resolve this.

[ivanwinhk]

solved-