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
About API error the solution is open port 7777 in your modem firewal and pc firewall (dont need port fowarding) with TCP and UDP protocols (before 1.0 realease, dedicated server ask only for UDP, now is TCP too)
Making both configuration make the server work properly
Instead of releasing videos on YouTube, it would be better to release a quality product. The dedicated server has become worse than it was in early access. Server crashes with the impossibility of playing on it even after a restart - a brilliant release. This is not what I was waiting for all these years.
As many dedicated server experts are here:
My friend hosts a server on a spare PC. His IP changes daily.
Is there an easy and free way to set his IP fixed or can you use a session ID so that I do not have to enter the new IP every time?
Connect to the server, set it up or enter a password if it's already setup. EVERYONE connecting to the server must use the server manager to connect. They simply enter a CLIENT password and are able to join as a client.
In other words, the SERVER MANAGER menu feature handles certificates and accessing servers (such as Dedicated Servers). Trying to directly connect by simply adding the IP + Port in a Join Game option won't work for a vast majority of people.
apparently, when you start the server through a .bat file, it doesn't use FactoryServer.exe but instead launches FactoryServer-Win64-Shipping-Cmd.exe located in your server directory under Engine/Binaries/Win64.
For me, adding that particular executable in my Windows Firewall fixed the problem of not being able to reach my server.
I do not use the -multihome parameter or the 15000/15777 ports.