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
did u put up the firewall rule for the steam itself? TCP 27015,27036 and UDP 8211,27015,27031-27036 those are the ones that i use on the VPC Firewall rules
Besides working around the initial launch issues.
Open ports using ufw: "sudo ufw allow 8211"
Testing on the host machine, launching with defaults works.
Testing in a VM on the host machine and connecting using the host OS, launching with defaults works.
Testing with a different port on the host machine, doesn't work.
Testing with a password on the host machine, doesn't work. (game lacks a password input...)
Issues repeat in a VM.
Gonna have to wait on an actual fix and proper in game support. Right now it's locked to default settings and it's not worth wasting your time with the password issue.
You can fix this by making a new user and rerunning the setup.
sudo adduser username
sudo usermod -aG sudo username
su - username
and then follow the guide.
I followed this guide and it didn't work originally
https://www.youtube.com/watch?v=0TjFLk_lP6c&ab_channel=A1RM4X
However I realised that just before you execute /usr/games/steamcmd +login anonymous +app_update 2394010 validate +quit
You want to execute mkdir ./steam
For whatever reason there is a difference between the states now vs when this video was made, but it doesn't seem to create the ./steam folder where you will (in the next step) make your sdk links.
I had Signal 11 issues before making this adjustment- running fine since making it. Hope this helps someone!
I added 2 more firewall rules, one to allow inbound and the other to allow outbound TCP and UDP connections for port 8211. I then ran the server without arguments and was able to finally connect to the server.
https://tech.palworldgame.com/dedicated-server-guide
Same problem here, I use the docker way to run server, but I can't find any "steam" or "pal" file in my ubuntu system.
my saved document is still empty, where are the saved file?
which gets rid of the steamclient.so problem. The usual steamclient.so: cannot open shared object file: No such file.... will come up but thats fine
"The given workaround was:
ln -s /home/your_user/.local/share/Steam/steamcmd/linux64/steamclient.so /home/your_user/.steam/sdk64/
ln -s /home/your_user/.local/share/Steam/steamcmd/linux32/steamclient.so /home/your_user/.steam/sdk32/
For me, it was:
mkdir /home/your_user/.steam/sdk64/
mkdir /home/your_user/.steam/sdk32/
ln -s /home/your_user/.steam/steamcmd/linux64/steamclient.so /home/your_user/.steam/sdk64/
ln -s /home/your_user/.steam/steamcmd/linux32/steamclient.so /home/your_user/.steam/sdk32/
https://developer.valvesoftware.com/wiki/Counter-Strike_2/Dedicated_Servers"
the same how to fix it?
have linux ubuntu