Quote:
Originally Posted by Huppy
Try this. In windows, "localhost" usually resolves to the local IP (127.0.0.1), but I've read, in some flavours of linux, it may not. I always use the local IP anyways. Plus, not sure why you had dual login servers with same (external IP) ? Commonly it's used for emu public and a lan (or local). I'm not sure why you had an IP set for "zones" either. ?
|
Okay, that really cleaned things up a lot. I'm only having one issue now... With the UCS and mail server...
Code:
{
"server" : {
"chatserver" : {
"host" : "192.168.1.167",
"port" : "7778"
},
"database" : {
"db" : "peq",
"host" : "127.0.0.1",
"password" : "password",
"port" : "3306",
"username" : "eqemu"
},
"mailserver" : {
"host" : "192.168.1.167",
"port" : "7778"
If I set the "host" to be my external IP, the UCS and mail server works for connections outside of my LAN, but the UCS/mail server shows as being down for clients connected on the LAN.
If I set the "host" to be my network IP (as above) then I can use the UCS/mail server on my LAN, but it's down for outside connections.
Is there a way to do what you did with the world section and specify both the external and internal hosts in this instance?