Please help with private Loginserver on public IP
I have my server up and running with the latest Linux source (Ubuntu 17.04), using the https://github.com/EQEmu/Server#server-installs (using server_source_bots).
I can use the public login server without any problems. Server shows up, I can login and play. Now I wan't to setup a private loginserver, just in case the public is down. I was able to build the loginserver, note without adding any crypto libs, they don't seem to be needed any longer. I can login into my private loginserver and it creates accounts in the database, if auto_create_accounts set to true. Problem: I don't see my server on the selection list, if using the private loginserver. I tried Titanium Client and ROF2, the server list is empty. EQemu is running on a dedicated server in a datacenter, with the server ip 136.243.xxx.xxx. All ports are open tcp and udp, no firewall. Please help. eqemu_config.xm Code:
/home/eqemu/server # cat eqemu_config.xml login.ini Code:
cat login.ini database Code:
select ServerID,ServerLongName,ServerShortName,ServerListTypeID,ServerLastIPAddr,ServerAdminID,ServerTrusted from tblWorldServerRegistration; Code:
select * from tblServerAdminRegistration; emtpy server list... Code:
Login Server] New SoD client connection from 178.202.xx.xx:55296 |
Quote:
<host>127.0.0.1</host> That will only work on a server that's on the same box as your client. If your server is hosted elsewhere, then the IP's need to point there. "136.243.xxx.xxx" |
Thank you for your answer. I tried it,no progress.
I now have (with the correct IP) this in my eqemu_config.xml: Code:
<loginserver2> Funny thing is, if I trace the MySQL(MariaDB) selects, there is never a single selection on "tblWorldServerRegistration" or "tblServerAdminRegistration". |
Assuming that BOTH your database and server are on that remote host, look at these edits in RED (both config files)
I am also going to assume you have the tbl login tables in your database and you've set a user/pass in the tblworldregistration table ? Code:
/home/eqemu/server # cat eqemu_config.xml Code:
cat login.ini |
Thank you again. But still no progress. If I login, I see the following SQL's executed and not more:
Code:
[Login Server] New SoD client connection from 178.202.xx.xx:57446 Edit: I found an old backup from 04.2016, replaced the binaries and the Server shows up. Because of incompatible databases, it stops after that. For me it looks like a code issue and I can't work it out (I'm not a coder). |
I can tell you with my own experience, I haven't been able to get a dual login for public/lan to work with any code/binaries past
April 14th,(2017). The public login works fine, but the second lan login won't connect to world with current source binaries. I don't worry too much about it, I don't mind using the public login for myself, I never see it go down too much over one year. |
Got it working now. I tried to understand the source code and found the error.
As mentioned in the changelog, you need the new "<legacy>1</legacy>" setting only for the public "official" Loginserver from EQEmu, which is using the old netcode. Quote:
But if you look closer at the code, you see that this is wrong. If there is no "legacy" setting, it defaults to 1 or TRUE. But the private loginserver use the new netcode, so it need to be 0 or FALSE. So to make it work, just add the following line to your eqemu_config.xml, inside the private loginserver section: Code:
<legacy>0</legacy> |
NICE FIND Thalix :) Thank You !
|
Just to add something, the <localaddress>192.168.x.x</localaddress> has to be enabled and specified. I had to do this to get
dual login for lan to work and let me past character screen. Wasn't something I had to do before, but all works great now. |
All times are GMT -4. The time now is 04:27 PM. |
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.