Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Um, kinda hard when you don't tell us what error you are getting. We need the exact text, or a screenshot, please.
It's in the title.
"Connect To Server Failed: Not Running The App"
Verbatim what it says.
This is for a client / server environment. If you are trying to host co-op sessions I got no clue.
on each client.
Ok, I think I know the answer for some of you on this one;
Most people whom are attempting to connect to their locally hosted dedicated server via their wan address, are connecting from within the same local network over the in game server list. This can be a problem. The problem is that your router needs to be capable of "hairpining" nat connections. A hairpin connection is where you make a request on the wan for your network, it forwards it to the appropriate internal IP. The problem occurs when the traffic is sent back to
your client machine through the router the server doesnt get a nat address from the router, it receives the local IP for the client machine. So the server attempts to use the local IP to return requests and the client gets confused. Its not expecting a response on the local network, its expecting one over your internet wan thus the connection fails.
TL;DR
EXAMPLE:
If --->
Your server IP in your network is 192.168.2.3
Your client machine is on the same network with an IP of 192.168.2.4
Your WAN address is 256.90.155.34
And --->
You have properly port forwarded your external traffic in your router to your server's IP of 192.168.2.3 (port 30000 and 30004 both TCP&UDP)
Then your router and/or your ISP's service must be able to "hairpin" traffic back in to your network otherwise an internal attempt to connect through the in-game server list (the address it will use is 256.90.155.34:30000) will fail.
Why this is happening:
When your client machine makes the request to your server from the WAN then the address delivered to the server should be as a machine that made a request from the internet, but thats not what is happening. What is happening is your router is recognizing the request as an internal address instead of forwarding an internet address. This means that when your server responds, it is responding to 192.168.2.4 instead of 256.90.155.34.
The proper way to test:
1.) Open your Empyrion client and type in your servers local IP (192.168.2.3:30000) if it works continue, if not then this is the issue you should look up "Cant connect to empyrion dedicated server locally"
2.) Use an external network (like ask a friend to test it from their house.) If it works your good, if not the you should search "Cant connect to empyrion over the internet but can access it locally"
3.) Try to connect through the server list in game. If this doesnt work, its probably due to the fact your network is not capable of properly hairpinning all traffic. DO NOT MAKE ADJUSTMENTS TO SETTINGS ON YOUR SERVER IF THIS FAILS. ITS A NETWORK ISSUE NOT A SERVER ISSUE.
Take-Away:
In the event your network cannot hairpin but you will be running your server from the same network you will be playing from then you must manually type in your IP address and port into the blank provided in the server list in game to play.