[Смердокрыл]

Hey!

I've been fighting my router for a long time and finally, it seems, have been able to forward all the right ports and host my server using no-ip. At first, I was having problems with people not being able to connect to me at all, but I fixed that by making my LAN IP static, and switching the "WAN connection" setting in port forwarding from "INTERNET_ADSL_IP" to "INTERNET_ADSL_PPP", whatever that means.

Now, people are able to log in with their account names and passwords, but not further than the server selection window, where they get the "Connecting to game server..." box either forever, or closing after a couple of seconds. I presume that means they can connect to my authserver, but not to worldserver, even though canyouseeme.org can see both ports 3724 and 8085. 

Could it be because I'm not using bnetserver (and my worldserver says "Opening muxer thread from inproc://bnetmgr to tcp://127.0.0.1:1118" after loading)? If so, could I somehow not use bnetserver and still get it working?

I would appreciate any help!

[Barbz]

Look at the auth/realmlist table in your db if you're on 3.3.5a

[Смердокрыл]

53 minutes ago, Barbz said:

Look at the auth/realmlist table in your db if you're on 3.3.5a

I'm on cata, and I did, of course, edit the realmlist table

[Razmataz]

What core are you using? TrinityCore?

[Смердокрыл]

Just now, Razmataz said:

What core are you using? TrinityCore?

Yes, gitlab.com/trinitycore/TrinityCore_434/tree/4.3.4

[Razmataz]

Right, I've not been keeping up to date on the development of 4.3.4 but there seems to be a line

BnetServer.Address = 127.0.0.1

in your worldserver.conf. Try setting that to the IP address you have used in your realmlist table.

[Смердокрыл]

12 minutes ago, Razmataz said:

Right, I've not been keeping up to date on the development of 4.3.4 but there seems to be a line

BnetServer.Address = 127.0.0.1

in your worldserver.conf. Try setting that to the IP address you have used in your realmlist table.

You mean the hostname, or my LAN IP?

[Razmataz]

You should be setting it to the IP address that your hostname redirects to. That goes for the realmlist as well - it should be

id - Server Name - public IP address - public IP address - 255.255.255.0 - 8085 - icon - … … …

[Смердокрыл]

2 minutes ago, Razmataz said:

You should be setting it to the IP address that your hostname redirects to. That goes for the realmlist as well - it should be

id - Server Name - public IP address - public IP address - 255.255.255.0 - 8085 - icon - … … …

My hostname redirects to my external ip, which is dynamic, hence I have to use the no-ip client, which checks my external IP regularly and changes my hostname settings accordingly

[Razmataz]

Alright, in that case you might have to give it a go with your hostname rather than an IP address. I don't know how it might turn out.

[Смердокрыл]

1 minute ago, Razmataz said:

Alright, in that case you might have to give it a go with your hostname rather than an IP address. I don't know how it might turn out.

YAAAAAAAAAAAAAY!

I had to set both address and localAddress in the realmlist table, and BnetServer.Address in worldserver.conf to my hostname, and it works wonderfully!

Thank you

[Смердокрыл]

24 minutes ago, Смердокрыл said:

YAAAAAAAAAAAAAY!

I had to set both address and localAddress in the realmlist table, and BnetServer.Address in worldserver.conf to my hostname, and it works wonderfully!

Thank you

But then, after someone tried to relog, they were again unable to. It seems to only work properly when I write my external IP there, but it changes, and I really don't want to be re-writing it every five minutes. What should I do?

[Razmataz]

That's what I was afraid of.

If you're unable to get away with hostname (which, to be fully honest, I don't see why you shouldn't be able to), you might need to hardcode it. I'm not sure how you'd accomplish that.

Or, I might've given you wrong details and you need to adjust localAddress in the realmlist table and BnetServer.Address to 127.0.0.1? Frankly, I've never figured it out 100%.

[Смердокрыл]

2 hours ago, Razmataz said:

That's what I was afraid of.

If you're unable to get away with hostname (which, to be fully honest, I don't see why you shouldn't be able to), you might need to hardcode it. I'm not sure how you'd accomplish that.

Or, I might've given you wrong details and you need to adjust localAddress in the realmlist table and BnetServer.Address to 127.0.0.1? Frankly, I've never figured it out 100%.

I tried multiple ways and it only works if I set address and BnetServer.Address to my external IP. localAddress seems to be unrelated 

[Bhalandros]

If you're really desperate... LogMeIn Hamachi is AN option. Not the best for many people, but if it's a small number... The IP doesn't change, if that's the only problem.

[Смердокрыл]

1 hour ago, Bhalandros said:

If you're really desperate... LogMeIn Hamachi is AN option. Not the best for many people, but if it's a small number... The IP doesn't change, if that's the only problem.

The only reason I am bothering with this whole IP thing is to avoid using Hamach/Evolve/etc., because I'm fed up with them

[Смердокрыл]

There seems to be a solution, but I really don't understand what that guide says:

https://gitlab.com/trinitycore/TrinityCore_434/issues/126

[Amaroth]

On 17. 4. 2017 at 2:51 PM, Смердокрыл said:

Now, people are able to log in with their account names and passwords, but not further than the server selection window, where they get the "Connecting to game server..." box either forever, or closing after a couple of seconds. I presume that means they can connect to my authserver, but not to worldserver, even though canyouseeme.org can see both ports 3724 and 8085. 

I have encountred similiar sort of behavior on my server which is running on dedicated VPS-hosted server with Debian distribution. Sadly, I wasn't able to find real solution, friend of mine did, so I am unsure what was really going on. AFAIK security of OS was blocking connections sent from authserver to worldserver of some IP addresses (yes, this as problem only for some IPs), identifying them probably as malicious activity. Thats all I can tell you about this matter, sadly, but it can help you with finding correct direction what to look for. Check your antivirus/antimalware software, firewall (on both server mashine and router), those kinds of stuff. Maybe problem isn't with your IP/ports (yes, ports, PAT/NAT can be annoying things to deal with), but with your actual security solutions on your network.

[Razmataz]

There are details on the 'hosts' file here: https://support.rackspace.com/how-to/modify-your-hosts-file/

[Смердокрыл]

6 hours ago, Razmataz said:

There are details on the 'hosts' file here: https://support.rackspace.com/how-to/modify-your-hosts-file/

I know how to edit it, and I did. As I wrote there, my 'hosts' file is currently:

127.0.0.1                                   *hostname*
*my LAN IP (I made it static)*    *hostname*
*my default gateway*                *hostname*
*my external IP*                        *hostname*
 

To be perfectly honest, that guide is not an example of good structure or language. What the hell does

"wan client pc gets public ip for wow.myserver.org

server pc realmlist.address
wow.myserver.org"

mean?

Edited April 23, 2017 by Смердокрыл

[Razmataz]

I think they mean Wide Area Network, aka an external client outside of your network / LAN?

[Смердокрыл]

5 hours ago, Razmataz said:

I think they mean Wide Area Network, aka an external client outside of your network / LAN?

I know what wan means, but what do those three sentences mean overall?

[Razmataz]

I'm pretty sure they're saying that the field https://trinitycore.atlassian.net/wiki/display/tc/realmlist#realmlist-address should be set to "wow.myserver.org" but you've said that you've done that already and while it resolves one issue it introduces another.