New Server Issue

[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. ?

{
   "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"
      },
      "qsdatabase" : {
         "db" : "peq",
         "host" : "127.0.0.1",
         "password" : "password",
         "port" : "3306",
         "username" : "eqemu"
      },
      "webinterface" : {
         "port" : "9081"
      },
      "world" : {
         "address" : "external IP address",
	 "localaddress" : "192.168.1.167",
         "http" : {
            "enabled" : "true",
            "mimefile" : "mime.types",
            "port" : "9080"
         },
         "key" : "long string",
         "loginserver1" : {
            "account" : "",
            "host" : "external IP address",
            "legacy" : "0",
            "password" : "",
            "port" : "5998"
         },
         "loginserver2" : {
            "account" : "",
            "host" : "192.168.1.167",
			"legacy" : "0",
            "password" : "",
            "port" : "5998"
         },
         "longname" : "Server Name",
         "shortname" : "server",
         "tcp" : {
            "ip" : "192.168.1.167",
            "port" : "9001"
         },
         "telnet" : {
            "enabled" : "true",
            "ip" : "192.168.1.167",
            "port" : "9000"
         }
      },
      "zones" : {
         "defaultstatus" : "0",
         "ports" : {
            "high" : "7400",
            "low" : "7000"
         }
      }
   }
}

[whiteknight33]

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...

{
   "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?