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
You have to use the latter one.
http://prntscr.com/1xyxhx2
I experienced this same UNetConnection Tick Connection TIMED OUT error when trying to set up a dedicated server for the game Satisfactory. Here's the solution I found:
Short answer: If the server you are connecting to is on your LAN, you cannot use a public IP and port to connect, you must use your local IP.
Long answer: I set up the server on dedicated server hardware, forwarded necessary ports to that IP, and set up a free DNS to point to my public IP (so I don't have to give every player my real IP address). Before telling my friends to try connecting to my server, I wanted to test it myself. I booted up the game on my desktop PC, typed in the DNS and port, and tried to connect. That gave me the error message. I pulled my hair out for hours trying to figure out why "my server was broken". In actuality, it was not broken, I just could not use my public IP (or my DNS) to connect to my own server. I tried using my local IP (192.168.1.128), and it connected with no problems. I instructed my friends to connect using my public IP or DNS and they could connect just fine.
This may not be the same cause/solution of the error message that you are experiencing, but this was the solution for me. Hope that helps.
my issue in particular turned out to be caused by the fact i was running the satisfactory from an HDD. even though it has pretty good transfer speeds, using an HDD for playing online is a no-go currently. the only solution for me was to move the game files to a new library located on my C:\ drive which is an NVME drive. hopefully as the game gets closer to 1.0 release, and as the code gets more optimized, thos issue will disappear. I say this becuase putting the game onto my NVME dropped the free space below 20%, which is not good.
Don't ask me why, but it solved my Dedicated Server connection issues I had on CentOS, Rocky OS and Ubuntu Server.
./FactoryServer -multihome={ip_address}