tovrin
05-16-2022, 10:53 PM
Let me say from the onset, I have found others with the same problem, but the solutions that I've found on the forum haven't worked for me. I'm kind of stumped.
When I log into my local LAN server (on a separate VM), I get no servers in the server list. I've installed the client on both my own PC and on the server itself and the same thing occurs. I'm using my own login server ... not the EQEMU login server.
My eqemu_config.json looks like this (edited to reflect edit below):
{
"server" : {
"chatserver" : {
"host" : "",
"port" : "7778"
},
"database" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "eqemu",
"port" : "3306",
"username" : "root"
},
"directories" : {
"opcodes" : "assets/opcodes/",
"patches" : "assets/patches/"
},
"files" : {
"mail_opcodes" : "assets/opcodes/mail_opcodes.conf",
"opcodes" : "assets/opcodes/opcodes.conf"
},
"mailserver" : {
"host" : "",
"port" : "7778"
},
"qsdatabase" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "eqemu",
"port" : "3306",
"username" : "root"
},
"world" : {
"key" : "<encryption key here>",
"loginserver1" : {
"account" : "",
"host" : "192.168.0.63",
"legacy" : "1",
"password" : "",
"port" : "5999"
},
"address" : "192.168.0.63",
"longname" : "Inn Mates EQ Server",
"shortname" : "Inn_Mates",
"tcp" : {
"ip" : "127.0.0.1",
"port" : "9001"
},
"telnet" : {
"enabled" : "true",
"ip" : "0.0.0.0",
"port" : "9000"
}
},
"zones" : {
"defaultstatus" : "0",
"ports" : {
"high" : "7400",
"low" : "7000"
}
}
}
}
My login.json looks like:
{
"account" : {
"auto_create_accounts" : true
},
"client_configuration" : {
"sod_opcodes" : "assets/opcodes/login_opcodes_sod.conf",
"sod_port" : 5999,
"titanium_opcodes" : "assets/opcodes/login_opcodes.conf",
"titanium_port" : 5998
},
"database" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "eqemu",
"port" : "3306",
"user" : "root"
},
"logging" : {
"dump_packets_in" : false,
"dump_packets_out" : false,
"trace" : false,
"world_trace" : false
},
"security" : {
"allow_password_login" : true,
"allow_token_login" : true,
"mode" : 14
},
"web_api" : {
"enabled" : true,
"port" : 6000
},
"worldservers" : {
"dev_test_servers_list_bottom" : false,
"reject_duplicate_servers" : false,
"show_player_count" : false,
"special_character_start_list_bottom" : false,
"unregistered_allowed" : true
}
}
I've tried a few things from several posts on the forum, including:
changing the specific IPs to 197.0.0.1 - no difference
inserting the HTTP settings - no difference
using port 5998 - no connection to my local login server
with and without localaddress - no difference
with and without account and password - no difference
As auto_create_accounts is set to true, and I can get past the login server to the server select screen, I assume I should be able to get to the world server without creating accounts. The login server gives me the message ...
[Login] [Info] New SoD+ client connection from [192.168.0.14:53364]
[Login] [Info] Attempting password based login [testaccount] login [local]
[Login] [Info] login [local] user [testaccount] Login succeeded
... so it looks ok. When look at the peq.login_account table, it's being populated correctly. However, the peq.accounts table is empty; I assume that table is only populated when I get past the server select screen?
The only thing that has me a little concerned is that I have two entries in the peq.login_world_server. I did change it on restarting the server. Is that going to be a problem?
I'm keeping this server purely local at the moment. I do plan on opening it up to friends eventually, but I want to make sure it's solo-friendly first ... and dungeons can be completed by two people or be at least challenging for a solo player.
But right now I need to beat this particular gremlin.
Any advice?
----------------------------------------------------------------------------------------------------
Edit 1: So, I rebuilt the server from scratch. Opened the ports on my router (though why that's required on an internal network server, I don't know). And the server appeared on the list (don't hold your breath yet).
After hitting PLAY EVERQUEST on hte client, I got this message:
[Login] [Error] Received User-to-World Response for [1] but could not find the client reference
Following a few threads, it suggested I change Legacy from 1 to 0. After that I no the server no longer appeared on the list.
The journey continues ....
When I log into my local LAN server (on a separate VM), I get no servers in the server list. I've installed the client on both my own PC and on the server itself and the same thing occurs. I'm using my own login server ... not the EQEMU login server.
My eqemu_config.json looks like this (edited to reflect edit below):
{
"server" : {
"chatserver" : {
"host" : "",
"port" : "7778"
},
"database" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "eqemu",
"port" : "3306",
"username" : "root"
},
"directories" : {
"opcodes" : "assets/opcodes/",
"patches" : "assets/patches/"
},
"files" : {
"mail_opcodes" : "assets/opcodes/mail_opcodes.conf",
"opcodes" : "assets/opcodes/opcodes.conf"
},
"mailserver" : {
"host" : "",
"port" : "7778"
},
"qsdatabase" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "eqemu",
"port" : "3306",
"username" : "root"
},
"world" : {
"key" : "<encryption key here>",
"loginserver1" : {
"account" : "",
"host" : "192.168.0.63",
"legacy" : "1",
"password" : "",
"port" : "5999"
},
"address" : "192.168.0.63",
"longname" : "Inn Mates EQ Server",
"shortname" : "Inn_Mates",
"tcp" : {
"ip" : "127.0.0.1",
"port" : "9001"
},
"telnet" : {
"enabled" : "true",
"ip" : "0.0.0.0",
"port" : "9000"
}
},
"zones" : {
"defaultstatus" : "0",
"ports" : {
"high" : "7400",
"low" : "7000"
}
}
}
}
My login.json looks like:
{
"account" : {
"auto_create_accounts" : true
},
"client_configuration" : {
"sod_opcodes" : "assets/opcodes/login_opcodes_sod.conf",
"sod_port" : 5999,
"titanium_opcodes" : "assets/opcodes/login_opcodes.conf",
"titanium_port" : 5998
},
"database" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "eqemu",
"port" : "3306",
"user" : "root"
},
"logging" : {
"dump_packets_in" : false,
"dump_packets_out" : false,
"trace" : false,
"world_trace" : false
},
"security" : {
"allow_password_login" : true,
"allow_token_login" : true,
"mode" : 14
},
"web_api" : {
"enabled" : true,
"port" : 6000
},
"worldservers" : {
"dev_test_servers_list_bottom" : false,
"reject_duplicate_servers" : false,
"show_player_count" : false,
"special_character_start_list_bottom" : false,
"unregistered_allowed" : true
}
}
I've tried a few things from several posts on the forum, including:
changing the specific IPs to 197.0.0.1 - no difference
inserting the HTTP settings - no difference
using port 5998 - no connection to my local login server
with and without localaddress - no difference
with and without account and password - no difference
As auto_create_accounts is set to true, and I can get past the login server to the server select screen, I assume I should be able to get to the world server without creating accounts. The login server gives me the message ...
[Login] [Info] New SoD+ client connection from [192.168.0.14:53364]
[Login] [Info] Attempting password based login [testaccount] login [local]
[Login] [Info] login [local] user [testaccount] Login succeeded
... so it looks ok. When look at the peq.login_account table, it's being populated correctly. However, the peq.accounts table is empty; I assume that table is only populated when I get past the server select screen?
The only thing that has me a little concerned is that I have two entries in the peq.login_world_server. I did change it on restarting the server. Is that going to be a problem?
I'm keeping this server purely local at the moment. I do plan on opening it up to friends eventually, but I want to make sure it's solo-friendly first ... and dungeons can be completed by two people or be at least challenging for a solo player.
But right now I need to beat this particular gremlin.
Any advice?
----------------------------------------------------------------------------------------------------
Edit 1: So, I rebuilt the server from scratch. Opened the ports on my router (though why that's required on an internal network server, I don't know). And the server appeared on the list (don't hold your breath yet).
After hitting PLAY EVERQUEST on hte client, I got this message:
[Login] [Error] Received User-to-World Response for [1] but could not find the client reference
Following a few threads, it suggested I change Legacy from 1 to 0. After that I no the server no longer appeared on the list.
The journey continues ....