Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
External clients can't connect to realm. #381
This is a fresh install.
SO: Windows server 2008
When a client tries to connect using a modified gateway, the connection works, but they get a " Diablo 2 could not connect to realm" right after registering.
I can connect, create an account, create a character, and just play forever with no problems, I am using the same client version they are using, I am connecting using a gateway that points to my external IP.
All ports are opened and routed to the same IP which is the internal server IP, all config files have been modified to point to this internal IP, windows firewall is off.
D2GS Service is started.
It looks like some kind of routing problem but I have no idea how to fix it.
PVPGN PARTIAL LOG:
Apr 21 01:04:24 [debug] pvpgn::bnetd::ipbanlist_check: checking 188.8.131.52
I uploaded the conf files to my own website so it's easier to get them but not sure if the link will get removed since it's a ddns so I'm posting both the ddns and the IP:
Current Diablo 2 pvpgn conf files (DDNS):
Current Diablo 2 pvpgn conf files ( IP ):
I did forward all four ports to the ip of the server. And checked with yougetsignal that they are in fact open. El 21/4/2019 19:27, "HarpyWar" <email@example.com> escribió:…
Probably you did not setup port forwarding if you have a router. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#381 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJJHCCXD37IXNY6F3WDJKYTPRTS4RANCNFSM4HHK4UKA> .
I added my external IP address to realm.conf , clients now get a "no realms are available right now, please try again later".
And now this problem affects me too I can't join and I get that same error. ( I could join with the internal IP)
Port is still open:
open port finder
Use Current IP
Open Port 6113 is open on 184.108.40.206.
I was wrong, this file is responsible to a connection between pvpgn and d2cs, and it can be not exposed to the internet.
Ok I undone the changes to realm.conf which now has the internal server IP.
Screenshot from one of the clients:
I can connect to it with no problems using my public IP on the gateway from inside the network.
The server has its windows firewall off and all ports, literally all four of them have been routed and I have confirmed they are open.
The error shows up right after registering.
Ok, we tried again, and apparently, (before forwaring udp too ) they managed to join the realm but when they try to create a game they get the error " Failed to join game" then diablo 2 returns to lobby.
I believe they managed to connect to the realm because I set the translation from 192.168.1.20 to my public IP, but there's still something else missing.
Apr 22 13:15:03 [debug] pvpgn::bnetd::game_del_player: game "Asdasd" has ref=1, count=1; trying to remove player "PoblaPeres"
More PVPGN LOG:
Apr 22 13:23:12 [debug] pvpgn::trans_net: client is not in the correct network
pr 22 13:23:00 [info ] pvpgn::d2cs::on_client_charloginreq: got character Chingui(*PoblaPeres) login request
Do you mean
After removing the change I made to address_translation.conf I can no longer connect to the realm, so apparently, there's something going on with that.
If I comment out the translation I can't connect to realm.
Ok so I got it working.
I modified all entries related to diablo 2 on address translation and it worked ok.
This is how address_translation.conf looks like now:
@HarpyWar I made a pull request for this exact problem because I wasted hours. For me it happened on "public" VPS which didn't expose public IP directly on interface. I feel like address_translation.conf should be exposed more in the main README to bring more attention to it.
Yes I agree. I found out about address translation after reading a thread by joe schmoe and decided to give it a try. At least on this particular case it was absolutely needed to modify address translation config file in order to get everything working. @HarpyWar <https://github.com/HarpyWar> I made a pull request for this exact problem because I wasted hours. For me it happened on "public" VPS which didn't expose public IP directly on interface. I feel like address_translation.conf should be exposed more in the main README to bring more attention to it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#381 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJJHCCVFJYVWBUFSB4EPYYTPRYXB7ANCNFSM4HHK4UKA> .