Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::General Support

Support::General Support Post all topics here having to do with errors while trying to connect to an EQEMu server but not about the setup/running of the Server itself.

Reply
 
Thread Tools Display Modes
  #1  
Old 06-17-2019, 07:43 AM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default New Server Issue

I just setup a brand new server on Ubuntu 19.04. It's working well now, except for one issue.

In Greater Faydark and PoKnowledge, the NPC's won't respond to my hails. Spamming the hails eventually gets them to reply with jibberish. (Squares and weird symbols.)

In Freeport, I'm able to get the Knights of Truth NPC's to respond just fine.

So I thought maybe it was an issue with PEQ quests in GFay and PoK, but then I attempted to add a buff NPC following the guide at http://www.eqemulator.org/forums/showthread.php?t=40898 and now my own NPC is acting like the ones in GFay and PoK.

I tried searching the forums for instances where NPC's wouldn't talk, and the only result I found was about Perl .dll files, which doesn't apply in my case.

Is this normal or is there a way to fix this without doing a full reinstall?

Edit: I also tried doing #questerrors after hailing like someone suggested in another thread, and no results were provided.

Any help would really be appreciated.
Reply With Quote
  #2  
Old 06-22-2019, 09:21 PM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

Well... I tried wiping out the machine and reinstalling the whole server from scratch.

On a brand new install, the NPC's in Kelethin (specifically the Ranger GM and people in that room) say nothing when hailed, and proceed to spit jibberish if I spam them with hails. Is this a Linux thing or is that just how EQEmu is for some reason?

Other issue I was having was I can connect to the server hosted locally just fine. But if I try to connect from another location or internet provider, it won't let me. (All ports are enabled and firewall is down.) At first the game would just freeze after picking the server and it would eventually give me a 1017 error. After tinkering with the server settings, I was able to get to character creation, but any outside connection gets kicked to server select when trying to login.

I'm starting to wonder if I'm having issues because Ubuntu 19.04 is too new or something.
Reply With Quote
  #3  
Old 06-23-2019, 05:15 PM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

Okay, one final update. I fixed both of my problems. Posting this in case someone else has any of these issues...

1.) Was a simple fix. Had to edit login.ini and change the IP address from 127.0.0. to 192.168.1. ...that allowed clients outside of my local network to actually login to the game.

2.) Rolling Ubuntu back to version 18.04 LTS fixed the quest/NPC responding to hails issue. I'm assuming that Perl or something is not working with 19.04 yet.

So if you're running an Ubuntu Linux server, go with 18.04 LTS for now and make sure to update your Login.ini file if people can't get onto your server from outside internet connections.
Reply With Quote
  #4  
Old 06-24-2019, 10:51 AM
Fluff
Fire Beetle
 
Join Date: Oct 2014
Location: Pacific Northwest
Posts: 28
Default

Thanks, I was having this same issue. Now that I rebuilt, it seems like login server is not building or something - as I keep getting sh: 1: ./loginserver: not found on a fresh install.
Reply With Quote
  #5  
Old 06-24-2019, 12:53 PM
Akkadius's Avatar
Akkadius
Administrator
 
Join Date: Feb 2009
Location: MN
Posts: 2,071
Default

There's always a chance that newer distributions break things and dependencies, we've gone through it many times. I would use Ubuntu 18.04 LTS in the meantime

I have some time off soon and I will be revisiting some of the installer stuff and running through a series of tests again.

As far as the loginserver, linux does not build the loginserver by default

You can install it however by invoking the following

Code:
perl eqemu_server.pl linux_login_server_setup
Reply With Quote
  #6  
Old 06-27-2019, 06:25 PM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

Quote:
Originally Posted by Akkadius View Post
There's always a chance that newer distributions break things and dependencies, we've gone through it many times. I would use Ubuntu 18.04 LTS in the meantime

I have some time off soon and I will be revisiting some of the installer stuff and running through a series of tests again.

As far as the loginserver, linux does not build the loginserver by default

You can install it however by invoking the following

Code:
perl eqemu_server.pl linux_login_server_setup
This may or may not be related to that... But I'm having an issue connecting to my server from outside of my own house. On my LAN, I can connect no problem.

Whenever I try to connect from an outside internet connection, I can get to the character selection screen, then the game freezes up and gives me the "You've been disconnected." message. I had thought I fixed this... Tested it by connecting via wifi hotspot on my phone and was able to get in. Still not able to connect from an outside wifi connection though.

I've followed every guide I could find by searching Google for results on this site, and I've changed every "host" / "IP" entry on my config file (whatever the Linux extension of that is, I'm not at home at the moment) and I've changed the IP in login.ini... I've tried using my external IP address, the network IP address of 192.168.1.167 and even 127.0.0.1... I even tried taking off the last digit of those IP addresses, like someone had suggested in previous posts.

I also turned off every Firewall on my network and computer, and set that computer as the DMZ machine in the router settings. (And did all of the port forwarding for EQEmu anyway.)

I have my server up and running great now on Ubuntu 18.04 LTS, but I can't connect to it from outside of my house. Which is a bummer, because I'd like to be able to play with a few friends too. Anyone have any other ideas of what might be wrong here?
Reply With Quote
  #7  
Old 06-27-2019, 07:34 PM
Huppy's Avatar
Huppy
Demi-God
 
Join Date: Oct 2010
Posts: 1,333
Default

If you are wishing to connect to your own private login server, from outside connections, you need get your external IP in there, (the one your ISP assigns you). If your ISP gives dynamic IP's that may change from time to time, it can be a pita, which you can get around by using a service like dyndns.

Code:
"world" : {
               "address" : "xxx.xxx.xxx.xxx",  <--- external IPv4 address (not lan or local)
	       "localaddress" : "192.168.1.167",
In your login.ini file :

Code:
local_network = 192.168.1. (leave the period, but exclude the last octet)
__________________
Hanging out at Antonica.World
Reply With Quote
  #8  
Old 06-27-2019, 09:54 PM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

Quote:
Originally Posted by Huppy View Post
If you are wishing to connect to your own private login server, from outside connections, you need get your external IP in there, (the one your ISP assigns you). If your ISP gives dynamic IP's that may change from time to time, it can be a pita, which you can get around by using a service like dyndns.

Code:
"world" : {
               "address" : "xxx.xxx.xxx.xxx",  <--- external IPv4 address (not lan or local)
	       "localaddress" : "192.168.1.167",
In your login.ini file :

Code:
local_network = 192.168.1. (leave the period, but exclude the last octet)
Okay, I ran that login server setup code from Akkadius and entered in the line you provided above. Now I'm getting this on my log...

Code:
[Error][Login Server] Config System Shutdown.
[Login Server] Log System Shutdown.
[Login Server] Logging System Init.eryserv: UP Loginserver: UP 			
[Login Server] Config System Init.
[Error] Config::Parse(), invalid parse token where = should be.
[Error] Database Initialization Failure.
[Login Server] Config System Shutdown.
[Login Server] Log System Shutdown.
[Login Server] Logging System Init.eryserv: UP Loginserver: UP 		
[Login Server] Config System Init.
[Error] Config::Parse(), invalid parse token where = should be.
[Error] Database Initialization Failure.
Before entering Akkadius' code, I was not getting the error or the "Loginserver: UP" confirmation.
Reply With Quote
  #9  
Old 06-27-2019, 10:08 PM
Huppy's Avatar
Huppy
Demi-God
 
Join Date: Oct 2010
Posts: 1,333
Default

Sorry whiteknight, I jump to conclusions and thought you would know what I meant, that world address entry has to go into your server config file. (eqemu_config.json)
__________________
Hanging out at Antonica.World
Reply With Quote
  #10  
Old 06-27-2019, 10:17 PM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

Quote:
Originally Posted by Huppy View Post
Sorry whiteknight, I jump to conclusions and thought you would know what I meant, that world address entry has to go into your server config file. (eqemu_config.json)
Oh yeah, I figured that out. I ran the code from Akkadius though, thinking my login server hadn't automatically installed on Linux. (Turns out it did though..) And that code wiped out my database settings in login.ini... Weird though, once I plugged the database info back in, it's not saying Loginserver: UP anymore... It's just Loginserver: and blank.

I added your code to the eqemu_config.json and now I just need to test it out and see if I can connect now.

eqemu_config.json looks like this now...

Code:
{
   "server" : {
      "chatserver" : {
         "host" : "192.168.1.167",
         "port" : "7778"
      },
      "database" : {
         "db" : "peq",
         "host" : "localhost",
         "password" : "password",
         "port" : "3306",
         "username" : "eqemu"
      },
      "mailserver" : {
         "host" : "192.168.1.167",
         "port" : "7778"
      },
      "qsdatabase" : {
         "db" : "peq",
         "host" : "localhost",
         "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" : "1",
            "password" : "",
            "port" : "5998"
         },
         "loginserver2" : {
            "account" : "",
            "host" : "external IP address",
            "password" : "",
            "port" : "5998"
         },
         "longname" : "Server Name",
         "shortname" : "server",
         "tcp" : {
            "ip" : "external IP address",
            "port" : "9001"
         },
         "telnet" : {
            "enabled" : "true",
            "ip" : "external IP address",
            "port" : "9000"
         }
      },
      "zones" : {
         "defaultstatus" : "0",
         "host" : "external IP address",
         "ports" : {
            "high" : "7400",
            "low" : "7000"
         }
      }
   }
}
and login.ini looks like this...

Code:
[database]
host = localhost
port = 3306
db = peq
user = eqemu
password = password
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5998
local_network = 192.168.1.
auto_create_accounts = TRUE

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = loginserver_server_accounts
world_registration_table = loginserver_world_server_registration
world_admin_registration_table = loginserver_server_admin_registration
world_server_type_table = loginserver_server_list_type
Does this all look right to allow an outside connection?
Reply With Quote
  #11  
Old 06-27-2019, 11:43 PM
Huppy's Avatar
Huppy
Demi-God
 
Join Date: Oct 2010
Posts: 1,333
Default

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. ?
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"
      },
      "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"
         }
      }
   }
}
__________________
Hanging out at Antonica.World
Reply With Quote
  #12  
Old 06-28-2019, 02:27 AM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

Quote:
Originally Posted by Huppy View Post
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?
Reply With Quote
  #13  
Old 06-28-2019, 07:04 AM
whiteknight33
Sarnak
 
Join Date: Aug 2016
Location: Ohio
Posts: 69
Default

I found the fix for this on another thread. If anyone else has this issue, keep the chat and mail server set to your external IP address and change this rule in your server rule_values from true to false:

Code:
Chat:EnableMailKeyIPVerification = true
Code:
Chat:EnableMailKeyIPVerification = false
Changing the above allowed both LAN and outside connections to use UCS and server mail.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 10:42 AM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3