[DiscordArchive] Very frustrating, right?
[DiscordArchive] Very frustrating, right?
Original source
In realmlist.wtf I put my public IP address after port forwarding 8085 and 3724
rektbyfaith
07-12-2021, 10:17 PM #21Archived author: The Dot • Posted: 2021-07-12T22:17:39.738000+00:00
Original source
In realmlist.wtf I put my public IP address after port forwarding 8085 and 3724
Original source
Okay, give me a bit. Working on dinner and then I'll try that out.
rektbyfaith
07-12-2021, 10:17 PM #22Archived author: notScott • Posted: 2021-07-12T22:17:51.103000+00:00
Original source
Okay, give me a bit. Working on dinner and then I'll try that out.
Original source
Hopefully this helps, took me a few hours to get it working lol, but it was a relatively simple fix
rektbyfaith
07-12-2021, 10:17 PM #23Archived author: The Dot • Posted: 2021-07-12T22:17:51.204000+00:00
Original source
Hopefully this helps, took me a few hours to get it working lol, but it was a relatively simple fix
Original source
rektbyfaith
07-12-2021, 10:17 PM #24Archived author: The Dot • Posted: 2021-07-12T22:17:56.766000+00:00
Original source
Original source
Okay, following your messages, I set 'address' and 'localAddress' in SQL to the internal IP. Port forwarding is setup for 3724 and 8085 to the server machine. Realmlist.wtf pointing to a domain address that resolves to the external IP.
With that, I was able to connect multiple local LAN sessions and log in fine, but externally could not connect at all.
Next, I tried setting 'address' to my domain address to connect to and left 'localAddress' at the internal.
With that, I was able to connect multiple local LAN sessions and log in fine, but externally could not log in. Got the same issue with auth working, but not passing me to the world server for character selection (but only when I changed the realmlist on the client to the external IP).
Finally, 'address' set to the external IP, 'localAddress' at internal IP.
1 LAN PC can connect, other absolutely unable to connect. Both using the external IP in realmlist on the client. Swapping order of PCs, same result. Second one that tries to log in absolutely cannot connect at all.
![[Image: unknown.png?ex=690c8393&is=690b3213&hm=8...18c4b2a97&]](https://cdn.discordapp.com/attachments/535208956449128490/864284133512577044/unknown.png?ex=690c8393&is=690b3213&hm=863a76bc3d0554c04d2f5f552ca95e1d3c46278e9e6d69edf81ca5518c4b2a97&)
rektbyfaith
07-12-2021, 11:16 PM #25Archived author: notScott • Posted: 2021-07-12T23:16:35.661000+00:00
Original source
Okay, following your messages, I set 'address' and 'localAddress' in SQL to the internal IP. Port forwarding is setup for 3724 and 8085 to the server machine. Realmlist.wtf pointing to a domain address that resolves to the external IP.
With that, I was able to connect multiple local LAN sessions and log in fine, but externally could not connect at all.
Next, I tried setting 'address' to my domain address to connect to and left 'localAddress' at the internal.
With that, I was able to connect multiple local LAN sessions and log in fine, but externally could not log in. Got the same issue with auth working, but not passing me to the world server for character selection (but only when I changed the realmlist on the client to the external IP).
Finally, 'address' set to the external IP, 'localAddress' at internal IP.
1 LAN PC can connect, other absolutely unable to connect. Both using the external IP in realmlist on the client. Swapping order of PCs, same result. Second one that tries to log in absolutely cannot connect at all.
1 Guest(s)
1 Guest(s)