ASA Public IP Issue Reverse Proxy

Technical Support
,
1

OS Name/Version: Currently Windows 11 24H2 (Have tried on Windows Server 2019 and Ubuntu Server as well)

Product Name/Version: AMP Phobos V2.6.2 build 17/06/25

Problem Description:
I have had this issue since the ASE days, but im coming back into ASA to revive my clustering. I have a very specific issue and im wondering if there is any way to resolve this other than a workaround.

Lets start by saying that I have a very specific and custom reverse proxy that I create for each of my game servers. I have a Ubuntu Server VM VPS setup to do the public traffic routing to my game servers. I use NGINX to do the routing, and have created stream configs for each server in my cluster. The way I achieve my reverse proxy is setting up Tailscale on my VPS and my game server and route external IP traffic to my VPS through my Tailnet. Being that Tailscale by default is a mesh style VPN and does not do “route all” policies this works great for me since my VPS has a 1TB usage limit and my home network does not, which means typically I can download and update as much as I like and it goes through my local connection, and only game related connections come in and go out through my Tailnet.

The issue:
With Ark Survival Ascended and Ark Survival Evolved specifically, this method makes it so that my servers show up on the server lists just fine, but no one can connect to them (besides doing “open ip:port” command) UNLESS I engage my exit node on my VPS and force route all traffic while starting up my ASA cluster. Once the cluster is started and it has registered the WAN IP of my cluster being my VPS, anyone can join with no issues it seems that I can still join through the server list.

What this tells me:
The server list is capturing my home WAN IP and cannot route it, because the only path is through my VPSs IP.
This is very very likely not a AMP specific problem, however I am wondering if AMP can help me solve it.

Actions taken to resolve so far:
Ive tried many things in the past to resolve this including providing the launch flags to set Epic IP source which doesnt even work for ASA and only ASE to my understanding. This has been something ive just dealt with and left my route all to my VPS up, but I want to find out why this is happening and if there are any known solution to this.

2

I’m not aware of any way of telling the ASA server which public IP to report to the server list

3

I guess ill just keep doing as im doing, I thought it a long shot, but I do appreciate the reply. Realistically I have a 1TB a month bandwidth limit on my VPS and if my updates and server traffic go over that, I have a completely different issue on my hands, especially with how few players I think ill have.

On a different note, Greelan, you helped me a lot with your posts and setup instructions when ASA first came out, wanted you to know that I appreciate you.

Would you mind if I DM’d you my exact setup for my reverse proxy and you tell me if im stupid or not? Im in the planning phase of a full ark private server cluster now that Ragnarok is out, and want to make sure if there are gaps in my knowledge its pointed out. I understand if thats outside of the scope of your support though

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.