Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::Windows Servers

Support::Windows Servers Support forum for Windows EQEMu users.

Reply
 
Thread Tools Display Modes
  #1  
Old 09-25-2019, 05:58 PM
ThermalLobster
Fire Beetle
 
Join Date: Sep 2019
Posts: 6
Question Help with Akka's PEQ installer

Okay so hoping for some guidance or help with getting Akka's up and running.

1. Using fresh install of Windows 10 Pro x64 on IP 192.168.1.15
2. Direct connect to Netgear Nighthawk R7800 Router
2. Ran Akka's PEQ Installer
3. Fresh install of Titanium EQ on EQ Emu server, hard wired windows 10 machine and wireless laptop.
4. EQEmu installed to C:\eqemuserver
5. EQ Titanium installed to C:\Program Files (x86)\Sony\EverQuest
6. Have tried to connect on all 3 machines, all 3 machines just sit at "connecting....." then tell me they can't reach the server

Tried multiple configurations of login.ini and eqemu_config.json using "localhost", "127.0.0.1", and "192.168.1.15"

eqhosts.ini file has been tried with "localhost", "127.0.0.1", and "192.168.1.15" on port 5998

no matter what I try I cannot get my eqclient to see the login server, just sits at "trying to connect"

screen shot of EQEmu screens below



Here's my current eqhost.ini

Code:
[LoginServer]
Host=192.168.1.15:5998

Here's my eqemu_config.json

Code:
{
     "server" : {
          "chatserver" : {
               "host" : "192.168.1.15",
               "port" : "7778"
          },
          "database" : {
               "db" : "peq",
               "host" : "192.168.1.15",
               "password" : "eqemu",
               "port" : "3306",
               "username" : "root"
          },
          "mailserver" : {
               "host" : "192.168.1.15",
               "port" : "7778"
          },
          "qsdatabase" : {
               "db" : "peq",
               "host" : "192.168.1.15",
               "password" : "eqemu",
               "port" : "3306",
               "username" : "root"
          },
          "webinterface" : {
               "port" : "9081"
          },
          "world" : {
               "http" : {
                    "enabled" : "true",
                    "mimefile" : "mime.types",
                    "port" : "9080"
               },
               "key" : "aMBdjbMEsWYjCt5BFbeG4x6wb0UjNVi",
               "loginserver1" : {
                    "account" : "XXXXXXX",
                    "host" : "login.eqemulator.net",
                    "legacy" : "1",
                    "password" : "XXXXXXX",
                    "port" : "5998"
               },
               "loginserver2" : {
                    "account" : "",
                    "host" : "192.168.1.15",
                    "password" : "",
                    "port" : "5998"
               },
               "longname" : "XXXXXXXXX",
               "shortname" : "XXX",
               "tcp" : {
                    "ip" : "192.168.1.15",
                    "port" : "9001"
               },
               "telnet" : {
                    "enabled" : "true",
                    "ip" : "0.0.0.0",
                    "port" : "9000"
               }
          },
          "zones" : {
               "defaultstatus" : "0",
               "ports" : {
                    "high" : "7400",
                    "low" : "7000"
               }
          }
     }
}
Here's my Login file

Code:
[database]
host = 192.168.1.15
port = 3306
db = peq
user = root
password = eqemu
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
I've tried installing Akka's on 2 separate machines and get the same result after running the installer.

Basically trying to set this up to use locally over LAN and also have my brother login from his house externally.

At this point i'd settle for it just working over local LAN, I have forwarded the required ports in my router but that's moot if I can't even login locally.

Please let me know if theres any further information I can provide to get this issue resolved and thank you all in advance for any advice.

And yes, I've been pouring over the Wiki, the GitHub page, and scouring forums and youtube for anything related to Akka's PEQ installer for help to no avail.
Reply With Quote
  #2  
Old 09-25-2019, 08:05 PM
ThermalLobster
Fire Beetle
 
Join Date: Sep 2019
Posts: 6
Default

So done some more troubleshooting and now i'm seeing when I launch t_start_with_loginserver

Code:
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
[WorldServer] [Info] Connected to Loginserver: [192.168.1.15:5998]
by changing the loginserver 1 host from "login.eqemulator.net" to "192.168.1.15"

however now i'm getting this error on the world server window

Code:
[Login Server] New world server connection from 192.168.1.15:58881
[Error] Handle_NewLSInfo error, remote address was null, defaulting to stream address 192.168.1.15.
[Error] World tried to login but there already exists a server that has that name.
Clients still cannot connect to Eqemu on local lan
Reply With Quote
  #3  
Old 09-25-2019, 08:06 PM
Akkadius's Avatar
Akkadius
Administrator
 
Join Date: Feb 2009
Location: MN
Posts: 2,071
Default

Looks like you're using the old Loginserver, we literally just pushed out a major overhaul of the Loginserver recently and the binaries were not updated until today

We need to get things updated to reflect but you can check out the changelog for details and if you want follow up in #support-server in Discord
Reply With Quote
  #4  
Old 09-25-2019, 08:11 PM
ThermalLobster
Fire Beetle
 
Join Date: Sep 2019
Posts: 6
Default

Quote:
Originally Posted by Akkadius View Post
Looks like you're using the old Loginserver, we literally just pushed out a major overhaul of the Loginserver recently and the binaries were not updated until today

We need to get things updated to reflect but you can check out the changelog for details and if you want follow up in #support-server in Discord
Must be my luck, I literally downloaded your Installer like 4 days ago and started trying to get this running.
Reply With Quote
  #5  
Old 09-25-2019, 09:01 PM
ThermalLobster
Fire Beetle
 
Join Date: Sep 2019
Posts: 6
Default

is there a reason the installer is fetching unstable binaries?

Code:
[Update] Fetching Latest Windows Binaries (unstable) from Appveyor...
Reply With Quote
  #6  
Old 09-26-2019, 12:09 AM
Uleat's Avatar
Uleat
Developer
 
Join Date: Apr 2012
Location: North Carolina
Posts: 2,815
Default

You need context for that log entry.

Did you attempt to update your binaries? Or did this occur during the normal boot-up process?

(Or, something completely different?)
__________________
Uleat of Bertoxxulous

Compilin' Dirty
Reply With Quote
  #7  
Old 09-26-2019, 07:32 AM
ThermalLobster
Fire Beetle
 
Join Date: Sep 2019
Posts: 6
Default

Quote:
Originally Posted by Uleat View Post
You need context for that log entry.

Did you attempt to update your binaries? Or did this occur during the normal boot-up process?

(Or, something completely different?)
wiped everything and started from scratch. that log is from the installer.
Reply With Quote
  #8  
Old 09-26-2019, 07:27 PM
Uleat's Avatar
Uleat
Developer
 
Join Date: Apr 2012
Location: North Carolina
Posts: 2,815
Default

We've been on that standard since at least 8/22/2016 - since before the eqemu_server.pl file name was changed.


'Unstable' just means the lastest build.

Stable binaries can suffer from the same bugs that Unstable do.

The real problem with Stable binaries comes from the matching of EQEmu code to PEQ daily dumps.

Stable binaries tend to lag behind current and can actually be incompatible with a newly installed database.

It's most likely this is the reason we are pulling from the 'Unstable' build archive.
__________________
Uleat of Bertoxxulous

Compilin' Dirty
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 09:06 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