Once i edited the cfg I was unable to see the Server Name in the SOTF Dedicated Hosts list. What could I be doing wrong? I've troubleshot with the following steps: - Rebooted the server - checked the .cfg file to see if the changes were there - created a new save of the .cfg to overwrite the existing .cfg I may not be editing the .cfg correctly? These are the steps I took: - changed the permissions to 777 on the .cfg file - edited the .cfg file -CTRL+X to commit the changes.
Those steps sound correct. If the server name doesn't show up my first suggestion would be to restart the docker container. Don't do the docker run command again, just restart using `docker restart sotf` after making the edits. Let me know if you manage with it and what the problem was, it may help other users too. And enjoy SOTF, such an awesome game.
@@neofxone Thanks! Just following up to say that my issues was network related. I hadn't set up the network gateway for my VPC so ... :D Yea. Haha XD Soooo ... I'm fixing that now. I'll report back to let you know if there are any additional configuration changes I had to make on my VPC to allow the EC2 to reach out to the internet. :3 Also, this is a great video.
@@neofxone Ok! Final solution was pretty complex, but basically within AWS we have VCP (virtual private cloud) which holds your EC2 and other assets. In order for this to work, we need to create an Internet Gateway which allows the EC2 within the VCP to connect to the outside world. In addition to opening ports within the EC2, we also need to open ports within the Security Group of the EC2. The security group, the Subnet, the Internet Gateway all have to be connected to the VCP hosting the EC2. Once those ports are open within the Security Group, as well as the Unbuntu server, SOTF can be properly attached and runs great!! :D Anyway, I really hope this helps someone! I love your tutorial so much I may make one explaining the whole process from the ground up! :D
I get this DSE [Self-Tests] [Networking] UDP GamePort [8766] is closed. Please fix and restart. #DSE [Self-Tests] [Networking] UDP QueryPort [27016] is closed. Please fix and restart. #DSE [Self-Tests] [Networking] UDP BlobSyncPort [9700] is closed. Please fix and restart. But I opened them all before running the docker
@@neofxone Hi, yeah i managed to figure that out. Is there any other ports that need opening as I'm getting cannot connect to steam public IP 0.0.0.0? is there any Steam ports that need opening
Hey thanks for your comment and welcome to the channel! Great suggestion on the video, thanks. For now: To start and stop, you can just run the usual `docker run` and `docker stop` commands. To ensure it starts when your system starts up, set the docker containers to restart always. The flag is included in the video description. To start docker with system startup, do `systemctl enable docker`. That will keep the server up.
@@neofxone ok honestly that basically answers everything I need 8 ended up getting portainer so that's helping with the start stopping thing without having to go into cli
@@neofxone so for run or stop, it keeps saying i dont have permission "Error response from daemon: pull access denied for sotf, repository does not exist or may require 'docker login': denied: requested access to the resource is denied."
@@neofxone I ended up using the wiki on the sotf GitHub page and after a but of an issue with docker-compose not installing i got it up and running... I think.
after sudo docker attach sotf i dont get no update state nothing happens am i doing something wrong?
You'll have to check the docker logs
how can I put a save from a peer to peer server to the dedecatet
Hey no idea but I searched it online and there are ways to copy the files over 👍
@@neofxone good thanks
Once i edited the cfg I was unable to see the Server Name in the SOTF Dedicated Hosts list. What could I be doing wrong? I've troubleshot with the following steps:
- Rebooted the server
- checked the .cfg file to see if the changes were there
- created a new save of the .cfg to overwrite the existing .cfg
I may not be editing the .cfg correctly? These are the steps I took:
- changed the permissions to 777 on the .cfg file
- edited the .cfg file
-CTRL+X to commit the changes.
Those steps sound correct. If the server name doesn't show up my first suggestion would be to restart the docker container. Don't do the docker run command again, just restart using `docker restart sotf` after making the edits.
Let me know if you manage with it and what the problem was, it may help other users too.
And enjoy SOTF, such an awesome game.
@@neofxone Thanks! Just following up to say that my issues was network related. I hadn't set up the network gateway for my VPC so ... :D Yea. Haha XD Soooo ... I'm fixing that now. I'll report back to let you know if there are any additional configuration changes I had to make on my VPC to allow the EC2 to reach out to the internet. :3
Also, this is a great video.
@@neofxone Ok! Final solution was pretty complex, but basically within AWS we have VCP (virtual private cloud) which holds your EC2 and other assets. In order for this to work, we need to create an Internet Gateway which allows the EC2 within the VCP to connect to the outside world.
In addition to opening ports within the EC2, we also need to open ports within the Security Group of the EC2. The security group, the Subnet, the Internet Gateway all have to be connected to the VCP hosting the EC2. Once those ports are open within the Security Group, as well as the Unbuntu server, SOTF can be properly attached and runs great!! :D
Anyway, I really hope this helps someone! I love your tutorial so much I may make one explaining the whole process from the ground up! :D
was soll ich tuen bei der Meldung "#DSE [Self-Tests] Please restart the server."
It can be the skip network tests config that needs to be set to true
@@neofxone hat sich schon erledigt aber danke
@@therealifebasti Great, glad to hear you managed with it. What was wrong with it? If you post here, someone could find it useful, please 🙏❤
@@neofxone ich musste "LanOnly" zu "true" setzten, dan einfach portweiterleitung und fertig
@@therealifebasti I'm glad the "LanOnly" setting resolved it for you ❤👍
I get this
DSE [Self-Tests] [Networking] UDP GamePort [8766] is closed. Please fix and restart.
#DSE [Self-Tests] [Networking] UDP QueryPort [27016] is closed. Please fix and restart.
#DSE [Self-Tests] [Networking] UDP BlobSyncPort [9700] is closed. Please fix and restart.
But I opened them all before running the docker
You have to open the ports on your firewall or turn off the self testing option.
@@neofxone Where is the self testing option?
@@Andy-Perry Hi, in the config, you can set `SkipNetworkAccessibilityTest` to "true"
Set the "SkipNetworkAccessibilityTest" config/setting
@@neofxone Hi, yeah i managed to figure that out. Is there any other ports that need opening as I'm getting cannot connect to steam public IP 0.0.0.0? is there any Steam ports that need opening
Do they have an install for Proxmox?
Hi, no idea. Does it support running a Docker image?
could we get a tutorial on how to stop the server, restart it, startup with systemd etc? this is assuming people know how to run docker with cli
Hey thanks for your comment and welcome to the channel!
Great suggestion on the video, thanks.
For now: To start and stop, you can just run the usual `docker run` and `docker stop` commands. To ensure it starts when your system starts up, set the docker containers to restart always. The flag is included in the video description. To start docker with system startup, do `systemctl enable docker`. That will keep the server up.
@@neofxone ok honestly that basically answers everything I need 8 ended up getting portainer so that's helping with the start stopping thing without having to go into cli
@@neofxone so for run or stop, it keeps saying i dont have permission "Error response from daemon: pull access denied for sotf, repository does not exist or may require 'docker login': denied: requested access to the resource is denied."
@@Laihoistheman Have you tried `sudo docker stop` ?
@@neofxone I ended up using the wiki on the sotf GitHub page and after a but of an issue with docker-compose not installing i got it up and running... I think.
Good one! git pull shouldn't be neccessary though...
Yeah like I mention git pull is not necessary unless you want to use docker compose or see how the code works