What ports to open

spidey1170 · #1 05-10-2018, 11:50 AM

I've read every post I could find, going back to 2004 or so using search engines, about which ports to open. My server runs and connects with no firewall running; however, when I enable the firewall, it gives me a 1017 error.

My system:

Code:

VPS
Debian 9 (updated & upgraded)
4GB RAM
ufw

The ports I've opened:

Code:

To                     Action   From
---------------------------------------
5998                 Allow    Anywhere
5999                 Allow    Anywhere
7000:7500/tcp   Allow    Anywhere
7000:7500/udp  Allow    Anywhere
7900:7999/tcp   Allow    Anywhere
7900:7999/udp  Allow    Anywhere
3306                 Allow    Anywhere
9001                 Allow    Anywhere

The last two were found in a post on these forums, I forget which one. I don't think I need them, but I'm grasping at straws here, now. It should be working, but I think I'm missing something between the login server and the game.

GRUMPY · #2 05-10-2018, 11:57 AM

5998
5999
7000-7500
7778 (chatserver on this ?)
9000-9001
Thats all you need. I just set all of them to both tcp/udp
You only need 3306 open if you're going to access your database remotely.

spidey1170 · #3 05-10-2018, 12:30 PM

Wow, okay, I enabled and disabled the firewall several times, like I had done yesterday, and deleted and readded the ports and now it's connecting. Huh... odd.

I'm not complaining one bit!

spidey1170 · #4 05-17-2018, 03:01 PM

Quote:

Originally Posted by GRUMPY

5998
5999
7000-7500
7778 (chatserver on this ?)
9000-9001
Thats all you need. I just set all of them to both tcp/udp
You only need 3306 open if you're going to access your database remotely.

For some odd reason, I can no longer see the server in the list, again. I didn't change any configuration files and tried to reboot my eqemu server (not the server itself) several times, with no help.

image · #5 05-18-2018, 03:22 PM

if you are talking about the eqemulator.org login it has a flaw in how it sends packets to the clients. The only way to circumvent is by using a tunnel for your UDP traffic or potentially using a VPN.

The login server eqemulator.org uses is ancient and Rogean needs to update to the new public LS that has been available for years.

spidey1170 · #6 05-18-2018, 03:27 PM

Quote:

Originally Posted by image

if you are talking about the eqemulator.org login it has a flaw in how it sends packets to the clients. The only way to circumvent is by using a tunnel for your UDP traffic or potentially using a VPN.

The login server eqemulator.org uses is ancient and Rogean needs to update to the new public LS that has been available for years.

It's my personal server that is on a VPS. It was there for a few days and then it disappeared.

image · #7 05-18-2018, 03:50 PM

oh lol..

in that case we need to see the login logs and world logs... it should give you more information there, if the world isn't connected to the login it won't be listed.

GRUMPY · #8 05-19-2018, 07:54 AM

Are you and your friend both in the same home, trying to connect ? On a Lan ?
Or is she trying to connect from another location ?
Aslo check the log file in the client logs folder and see what it says.

spidey1170 · #9 05-19-2018, 03:05 PM

Quote:

Originally Posted by GRUMPY

Are you and your friend both in the same home, trying to connect ? On a Lan ?
Or is she trying to connect from another location ?
Aslo check the log file in the client logs folder and see what it says.

She's halfway across the world. I just sent an email asking her to try it from her daughter's computer to troubleshoot their network; if it works from her daughter's computer, then we know it's her system, if not we can look at her router.

Is there anything I should look for in her router that would stop the traffic? I'll have to ask what kind she has, I suppose, to see if it has a default firewall that's blocking traffic.

Where are the client logs located, so I can walk her through it?

GRUMPY · #10 05-19-2018, 03:16 PM

Try this, just to for troubleshooting purposes :
Temporarily - put your server into the public Emu login server. If your friend can get on through
there, then you have no port or firewall problems.

GRUMPY · #11 05-19-2018, 05:23 PM

Just to clarify, (for private loginserver, outside connections).

If your friend can connect to any server on that Emu public server list that
supports your client version (like Titanium), then there is no issues on your
friend's end. If your friend can't connect to any server, problem is on their
end. (usually a firewall, which can also come from an antivirus program).

If your server is patched into the Emu public login server and your friend can
connect to it through there, then neither of you have any port or firewall
problems.
Ultimately, if absolutely nobody can connect to your server privately, or from
the Emu public login server, the problem is on your end.

Ruling all that out, then if the connecting problem is soley with your own
private login server, then the problem is more than likely within your server
configuration.
It would still let YOU in, because you're connecting from within your own lan
or network, regardless.

Then it's a matter of looking at the two common culprits, the login.ini file
and/or the eqemu_config.json file.

spidey1170 · #12 05-21-2018, 12:44 AM

Quote:

Originally Posted by GRUMPY

Just to clarify, (for private loginserver, outside connections).

If your friend can connect to any server on that Emu public server list that
supports your client version (like Titanium), then there is no issues on your
friend's end. If your friend can't connect to any server, problem is on their
end. (usually a firewall, which can also come from an antivirus program).

If your server is patched into the Emu public login server and your friend can
connect to it through there, then neither of you have any port or firewall
problems.
Ultimately, if absolutely nobody can connect to your server privately, or from
the Emu public login server, the problem is on your end.

Ruling all that out, then if the connecting problem is soley with your own
private login server, then the problem is more than likely within your server
configuration.
It would still let YOU in, because you're connecting from within your own lan
or network, regardless.

Then it's a matter of looking at the two common culprits, the login.ini file
and/or the eqemu_config.json file.

I actually connect outside my server. It's on a VPS and I'm 1 state and 1 country away.

Her daughter's system just crashed, so hopefully we can figure her system, or my server, out.

Scorpious2k · #13 05-19-2018, 09:44 PM

I might have missed it, but I haven't seen any discussion of port FORWARDING... through the router. All I saw mentioned was the firewall.

spidey1170 · #14 05-21-2018, 12:51 AM

Quote:

Originally Posted by Scorpious2k

I might have missed it, but I haven't seen any discussion of port FORWARDING... through the router. All I saw mentioned was the firewall.

My server is 24/7 on a VPS, Linux Debian 9 and ports are opened through UFW. The only router is her router, well, and mine, but my connection seems to work most of the time.

GRUMPY · #15 05-21-2018, 02:11 AM

Quote:

Originally Posted by spidey1170

My server is 24/7 on a VPS, Linux Debian 9 and ports are opened through UFW. The only router is her router, well, and mine, but my connection seems to work most of the time.

Ok, now I am a little more clear of your setup. Your server is hosted somewhere else
and "both" of you are using the same client. You can connect, and she can't.
So problem is not "server-side", it's on her end. Has she tried connecting to any of
the public servers ? Using: Host=login.eqemulator.net:5998 ?