[DiscordArchive] However, when I attempt to access the server on port `8085`, it works locally but not when hitting m
[DiscordArchive] However, when I attempt to access the server on port `8085`, it works locally but not when hitting m
Original source
However, when I attempt to access the server on port `8085`, it works locally but not when hitting my WAN address:
```
user@personal-wsl ~ $ telnet <isp_wan_ip> 8085
Trying <isp_wan_ip>...
^C
user@personal-wsl ~ $ telnet <server_lan_ip> 8085
Trying <server_lan_ip>...
Connected to <server_lan_ip>.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
```
I have port forwarding rules all working and I can access my server from outside my LAN when I change realmlist table to my WAN IP or hostname that resolves to WAN IP. I am unable to login to the realm when accessing it locally (auth still works for both WAN and LAN) when this is the case though. However, when I change my realmist address to my server LAN IP, I can connect to the realm from my LAN clients, but WAN clients cannot.
I don't know what I am doing wrong but I feel it's networking related, not specifically a bug or issue with AC but I can't figure it out...
As mentioned above, I've got split DNS configured instead of NAT reflection. Will a split DNS setup work? Does the game resolve the table address from a public DNS resolver or will it go to my internal DNS resolver to resolve it for LAN clients, and WAN clients resolve to my WAN IP? How can I troubleshoot this to make it work? Knowing that I have a DNS resolver on PfSense that returns my server LAN IP, and all WAN clients will resolve to the WAN address, does this mess with how the game resolves the address field?
rektbyfaith
01-14-2024, 05:18 AM #1Archived author: th3cookie • Posted: 2024-01-14T05:18:54.294000+00:00
Original source
However, when I attempt to access the server on port `8085`, it works locally but not when hitting my WAN address:
```
user@personal-wsl ~ $ telnet <isp_wan_ip> 8085
Trying <isp_wan_ip>...
^C
user@personal-wsl ~ $ telnet <server_lan_ip> 8085
Trying <server_lan_ip>...
Connected to <server_lan_ip>.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
```
I have port forwarding rules all working and I can access my server from outside my LAN when I change realmlist table to my WAN IP or hostname that resolves to WAN IP. I am unable to login to the realm when accessing it locally (auth still works for both WAN and LAN) when this is the case though. However, when I change my realmist address to my server LAN IP, I can connect to the realm from my LAN clients, but WAN clients cannot.
I don't know what I am doing wrong but I feel it's networking related, not specifically a bug or issue with AC but I can't figure it out...
As mentioned above, I've got split DNS configured instead of NAT reflection. Will a split DNS setup work? Does the game resolve the table address from a public DNS resolver or will it go to my internal DNS resolver to resolve it for LAN clients, and WAN clients resolve to my WAN IP? How can I troubleshoot this to make it work? Knowing that I have a DNS resolver on PfSense that returns my server LAN IP, and all WAN clients will resolve to the WAN address, does this mess with how the game resolves the address field?
Original source
I am running the docker-compose version of the app, inside a VM inside a hypervisor on a VLAN
rektbyfaith
01-14-2024, 05:22 AM #2Archived author: th3cookie • Posted: 2024-01-14T05:22:09.510000+00:00
Original source
I am running the docker-compose version of the app, inside a VM inside a hypervisor on a VLAN
Original source
i was having a similar issue by using a downloaded repack, if that is the case you will need to install everything yourself.
rektbyfaith
01-14-2024, 11:33 AM #3Archived author: Definit • Posted: 2024-01-14T11:33:03.362000+00:00
Original source
i was having a similar issue by using a downloaded repack, if that is the case you will need to install everything yourself.