View Single Post
  #3  
Old 06-20-2020, 04:45 AM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Unhappy Update

Okay, so I reinstalled Debian 10 and started over from scratch, going right for EQEmu as the first thing I installed.

This time, the server installed properly and found most of the things it needed. I can even get the server to launch with login, like before. Problem is, the .json files have been updated, and I can't get my server to appear in the server selection window now.

Below are my .json files as they appeared on Fedora 31, when they were working on an older release of EQEmu:


eqemu_config.json
Quote:
"server" : {
"chatserver" : {
"host" : "(public IP)",
"port" : "7778"
},
"database" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "(hidden password)",
"port" : "3306",
"username" : "eqemu"
},
"mailserver" : {
"host" : "(public IP)",
"port" : "7778"
},
"qsdatabase" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "(hidden password)",
"port" : "3306",
"username" : "eqemu"
},
"webinterface" : {
"port" : "9081"
},
"world" : {
"address" : "(public IP)",
"localaddress" : "192.168.1.167",
"http" : {
"enabled" : "true",
"mimefile" : "mime.types",
"port" : "9080"
},
"key" : "3sdTns1nd1LuThaF3StX2tzb3ITS5Hx",
"loginserver1" : {
"account" : "",
"host" : "(public IP)",
"legacy" : "1",
"password" : "",
"port" : "5998"
},
"loginserver2" : {
"account" : "",
"host" : "192.168.1.167",
"legacy" : "0",
"password" : "",
"port" : "5998"
},
"longname" : "Cloud Gray",
"shortname" : "cloud",
"tcp" : {
"ip" : "127.0.0.1",
"port" : "9001"
},
"telnet" : {
"enabled" : "true",
"ip" : "127.0.0.1",
"port" : "9000"
}
},
"zones" : {
"defaultstatus" : "0",
"ports" : {
"high" : "7400",
"low" : "7000"
}
}
}
}
login.json
Quote:
{
"database": {
"host": "127.0.0.1",
"port": "3306",
"db": "peq",
"user": "eqemu",
"password": "(hidden password)"
},
"general": {
"reject_duplicate_servers": false,
"auto_create_accounts": true,
"trace": true,
"world_trace": false,
"dump_packets_in": false,
"dump_packets_out": false,
"listen_port": 5998,
"web_api_port": 6000
},
"web_api": {
"enabled": false,
"port": 6000
},
"security": {
"mode": 14,
"unregistered_allowed": true,
"allow_password_login": true,
"allow_token_login": false
},
"Titanium": {
"port": 5998,
"opcodes": "login_opcodes.conf"
},
"SoD": {
"port": 5999,
"opcodes": "login_opcodes_sod.conf"
}
}
Now it might seem pretty self-explanatory to just add the categories that are new/missing in the newer default .json files (like pointing the opcodes to their new directories) and... I've tried that. I even tried editing the new .json files with all of my old information.

For some reason, I can't get my server to appear in the server selection screen now. So either Debian 10 has some kind of weird incompatibility (which it seems to run fine) or I'm botching something on my end with these .json files, I assume.

I'd really appreciate it if someone could get me going in the right direction here. I've tried changing between my public IP, internal IP, and localhost/127.0.0.1 and no combination of IP addresses seems to make it appear. Thank you.
Reply With Quote