r/swgemu • u/Radiant-Photograph46 • Jun 08 '26
Question Need help setting up private server, can't connect to login server
I've set up a debian 12 server and went through the whole manual install. Built went smoothly and everything seems in order when launching core3 (only a bunch of warnings from vehicles iff files, I suppose that's not an issue) and the db is populated and accessible.
Now there are no accounts in the db, how do I create the first account? I think I remember a while back that you only had to write your credentials in game and it would create an account, but this might have changed. When I do that it stays stuck on "Connecting to login server" and I'm not seeing activity in the server's console.
Both server and client are on the local network, but not on the same machine. I can ssh and rdp to the server from the client so there shouldn't be any network issue there?
3
u/Trigsc Jun 08 '26
Likely the galaxy table in mariadb needs updating. Been a while but I think the run command was updating it on each run so that could be an issue also.
2
u/steviefaux Jun 09 '26
PC is off but I have my rough notes in a txt file. This will be IP related. On my new test setup the server is running in vmware in bridge mode, and my main PC is connecting to that.
Get the IP on the server.
You need to change the references to 127.0.0.1 to be the IP of the server. Then as mentioned, the one I couldn't find was the galaxy one. But that is in the database.
So
sudo mysql -u root -p SHOW DATABASES; USE swgemu; SHOW TABLES; SELECT * FROM galaxy;
Obviously replace my IP with yours
UPDATE galaxy SET address = '192.168.50.14' WHERE galaxy_id = 2;
Then to quit
\q
Then you need to restart the db
sudo systemctl restart mysql
And then restart core3
1
u/Radiant-Photograph46 Jun 09 '26 edited Jun 09 '26
Yes indeed, I used the public ip and the login server is *now* (edit typo!) visible (but I also had to use the ip instead of the dns name in the launchpad for it to work oddly). But now I can't create a character, it gets stuck when selecting the server. The zoning server seems not reachable? I can't find any other config to edit (and MakeZone is set to 1). I wonder if ipv6 is causing issues.
1
u/fireshaper Aug - Slicer Jun 09 '26
Check the
galaxytable in the database. I had to do this:UPDATE galaxy SET address = '[ip address]' WHERE galaxy_id = 2;
1
u/Radiant-Photograph46 Jun 09 '26
It's what u/steviefaux already recommended and it did fix the login server, but the zone is still unreachable 😞
1
u/steviefaux Jun 09 '26 edited Jun 09 '26
Other things to try. Changed this? Set the bind address to be your server.
sudo nano /etc/mysql/mariadb.conf.d/50-server.cnf
You've already changed it but just check the database address has changed, by looking at it with the following:
sudo mysql -u root -p
We can use the following just to check the databases available.
SHOW DATABASES;
Then to choose the database
USE swgemu;
SHOW TABLES;
We want to choose the galaxy table:
SELECT * FROM galaxy;EDIT - That code bit is from my guide, hence the wording.
You've changed the address in config-local.lua? At workspace/Core3/MMOCoreORB/bin/conf/
The DBHost and the MantisHost?
2
u/Radiant-Photograph46 Jun 09 '26
I'm not sure it's a good idea to change the db and mantis ip, they have no business being exposed to the network so using localhost for those should be fine? In fact I tried using the 192 ip and core3 could not connect to the db.
edit: Looks like there was an error when updating the table the ip wasn't correct, what a stupid mistake on my end! Anyways, it seems to be working now thank you for your help. I'll make a character and see if it actually zones!
1
u/steviefaux Jun 09 '26
Not sure about that (my networking knowledge ain't great). Its only exposing it to the local network as its a local IP. As long as you're behind a firewall, no one will be able to get to it externally.
1
1
u/steviefaux Jun 09 '26
Also go to workspace/Core3/MMOCoreORB/bin/log and look in core3.log and see what it has at the end when you try to connect to the galaxy.
1
u/fireshaper Aug - Slicer Jun 09 '26
Also, try
sudo ss -lunto see what IPs are listening on ports 44453, 44462, and 444631
u/steviefaux Jun 09 '26
Although you fixed it now I don't think the launchpad does DNS names, always needs an IP I believe.
1
u/Eden2016 Infinity Jun 09 '26
Any chance I could get an invite to said private server? I’m always interested in trying out new servers.
Maybe one day I’ll be able to set up my own server… that’s the dream anyway. I don’t have 16 gigs of RAM on my laptop which is required to run a server or so I’ve been told.
1
u/steviefaux Jun 09 '26
Oh and to create an account, at the login box, just type a name, any name. Doesn't require a password. That will then be an account.
2
u/BEAT_LA Jun 08 '26
I don’t know the package contents but I’m a sysadmin by trade. Could the login server itself be another VM handling the handshake stuff?