How to Set Up an Enshrouded Server

Creating your own server in Counter-Strike 2 is not just a great way to customize the gameplay to your needs and play with your circle of friends. It’s a whole world of opportunities for enthusiasts and administrators. Your own server opens unlimited horizons for creativity and control: you set the rules, choose the maps, adjust game parameters such as speed, weapon damage, or round economy, and ensure a stable connection with low ping without random players. It’s an ideal platform for cozy evening games with colleagues, organizing amateur tournaments, or simply honing your skills in a controlled arena. You become the full owner of your virtual space. In this article, we will cover all stages of creating and setting up a CS2 server from scratch in as much detail as possible, taking into account all potential pitfalls. We will go through the process from selecting a provider and configuring the operating system to the moment when you and your friends are already battling on a freshly deployed server. If you carefully follow each step of the instructions, even a complete beginner who has never administered a Linux server before will be able to manage the setup. Which VPS to Choose? One of the most important questions for anyone thinking about creating their own game server is choosing a reliable provider. Stability, low ping, uninterrupted uptime, and responsive technical support are key factors for comfortable and hassle-free gameplay. Hosting a CS2 server on a home computer comes with risks: a dynamic IP address, unstable connection, high ping for players from other regions, and the need to keep the PC running 24/7. Ordering a virtual server (VPS) solves all these problems by providing powerful and stable hardware in a professional data center. For our CS2 server, we will choose a VDS from Hostman with the following configuration: CPU 2 x 3.3 GHz, RAM 4 GB, NVMe 80 GB; 1 IPv4. This setup is sufficient for comfortable gameplay with friends, roughly 8–10 people. If you’re thinking about something bigger, such as a public server with regular activity of 20+ players or running complex mods with many plugins (e.g., MetaMod, SourceMod), it’s worth considering a more expensive, high-performance plan with extra resources. With Hostman, you can easily scale your setup, so you can start small and upgrade your virtual server configuration at any time with just a few clicks. The system that will run the server is Ubuntu 24.04 LTS (Noble Numbat). This is a stable and popular distribution version, ensuring compatibility and a wealth of ready-made instructions available online. Server Preparation First, connect to your server via SSH; more details can be found in our article. To create the server, we need to install Docker and Docker Compose. To do this: Update APT packages: sudo apt update Install supporting packages: sudo apt install curl software-properties-common ca-certificates apt-transport-https -y curl: a tool for transferring data and working with URLs; software-properties-common: provides scripts for software management; ca-certificates: necessary for secure data transfer and certificate validation; apt-transport-https: allows working with repositories that transmit data via HTTPS. Import the GPG key: wget -O- https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor | sudo tee /etc/apt/keyrings/docker.gpg > /dev/null Add the Docker repository: echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu jammy stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null Update APT package indexes again: sudo apt update Install Docker: sudo apt install docker-ce -y Check that Docker is running correctly: sudo systemctl status docker This command will show Docker’s status, indicating that it is active and running. Great! Docker has been successfully installed. Deploying the CS2 Server This stage can be conditionally divided into two parts: obtaining a special key from Steam and directly configuring the server container. Obtaining the SRCDS Token (Game Server Login Token, GSLT) For your server to be legal and fully functional, it needs a unique key for authentication on the Steam network. Without this token, the server will be considered anonymous and severely limited in its functionality (marked as “pirate,” with some features disabled). Steam account requirements: The account must not have bans (VAC or Game Ban) in any game. The account must not be restricted (Community Ban), for example, unable to add friends or trade. The account must have a verified mobile number linked (Steam Guard). CS2 must be added to the library on the account (any purchase in the Steam store over $5 also removes this restriction). Maximum number of tokens that can be created on one account: 1000. Step-by-step instructions: Log in to Steam in your browser. Go to the official Game Server Management page. At the bottom of the page, find the form Create New Game Server Login Token. In the App ID field, enter 730. This is the unique identifier for Counter-Strike 2 in Steam. In the Memo field, you can enter any reminder for yourself (e.g., “My CS2 server on Hostman”). Click the Create button. The system will provide a long string of letters and numbers which is your token. Copy it and save it in a secure location (for example, in a file on your computer). You will need this token in the next step. This token is the password to access your server from your account. Do not publish it publicly or share it with third parties. Server Configuration and Launch Now let’s return to our server terminal. We will use a ready-made solution in the form of a Docker container, which significantly simplifies the process of installing and updating the game server. Check Docker Compose installation. Modern versions of Docker already include the Compose plugin. Let’s check: sudo docker -v && sudo docker compose version The output should show the versions of Docker and Docker Compose, confirming they are ready to use. Create a working directory. It’s best to store all server configuration files in a separate folder for organization: mkdir cs2server && cd cs2server Download the docker-compose.yml configuration file. Instead of creating the file manually, we’ll use a ready-made example from a popular repository. Download it directly to the server: wget https://raw.githubusercontent.com/joedwards32/CS2/refs/heads/main/examples/docker-compose.yml Create the .env configuration file. This is the most important file, containing all sensitive data and your server settings.  nano .env In the text editor, insert the following parameters, replacing generated_token_earlier with the GSLT token you obtained in the previous section: # Mandatory parameters SRCDS_TOKEN=generated_token_earlier # Password for RCON (remote server management) CS2_RCONPW=Your_Complex_Password_1 # Password for connecting to the server (leave empty for public server) CS2_PW= # Your server’s name as players will see it in the server list CS2_SERVERNAME=My Cool CS2 Server # Password for GOTV (spectator mode) TV_PW=Your_Complex_Password_2 # Additional settings (can be configured later) CS2_PORT=27015 CS2_TV_PORT=27020 CS2_IP=0.0.0.0 CS2_MAXPLAYERS=10 CS2_MAP=de_dust2 CS2_GAMETYPE=0 CS2_GAMEMODE=1 After filling in the values, press Ctrl+O to save the file, Enter to confirm, and Ctrl+X to exit the nano editor. (Optional) Perform basic docker-compose.yml configuration. Open the file to quickly review or modify some parameters: nano docker-compose.yml You’ll see the file structure. Here you can directly change parameters such as: CS2_SERVERNAME: the server name visible to players. CS2_RCONPW: password for remote management via RCON. CS2_PW: password to connect to the server. Leave empty for a public server: "". TV_PW: password for spectators on GOTV. ./cs2/csgo:/home/steam/cs2-dedicated/csgo: connects your server’s configuration folder to the container folder, ensuring settings persist after updates. After reviewing and making any changes, save the file (Ctrl+O, Enter, Ctrl+X). Run the container: sudo docker compose up -d The -d flag means “detached,” so the container will run in the background while you can continue working in the terminal. Monitor the launch process. The server will not start instantly. Docker will first download the CS2 server image, then initialize it and load game files. This may take a significant amount of time (tens of minutes) because the game files are large. Monitor the process with the following commands: General container status: sudo docker compose ps View real-time logs (very useful for tracking progress): sudo docker compose logs -f To exit log monitoring, press Ctrl+C. View only the latest log entries: sudo docker compose logs The logs will show how the server downloads and updates CS2. Completion and successful launch are indicated by a line like: [S_API] SteamNETSockets startup successful and the absence of errors. Do not interrupt the process or shut down the server until loading is complete. Wait for the readiness message. If you see a successful launch message in the logs, your CS2 server is now running and is likely visible in the public server list in the game. Next, we move on to testing and fine-tuning it. Did you know? Hostman got you covered with servers with big amounts of storage for every project! Check our VPS Storage and start deploying now! Connecting to the Server and Basic Management Now we can join our own server. Enable the Developer Console. Go to CS2 settings → Game → Advanced Settings and click Enable Developer Console. Find the public IP address of your VPS. It’s listed in your Hostman control panel on the server Dashboard. Open the console in the game (using the ~ key on your keyboard, below Esc). Enter the connection command. The standard CS2 port is 27015. For example: connect 123.123.123.123 Replace 123.123.123.123 with your server’s real IP address. If you set a server password (CS2_PW), enter: password your_server_password before running the connect command. Once connected, you can start playing on your personal server. Conclusion As you can see, the process of creating your own Counter-Strike 2 game server, though it may seem complex at first, becomes quite manageable with a clear step-by-step guide. Successfully launching a game server is important but only the first step in creating a stable and engaging gaming environment. Further work should focus on comprehensive optimization and configuration of all server systems. The foundation of stable operation is a well-configured server file setup. These settings determine all aspects of functionality, from network parameters and game rules to security and performance. Detailed configuration ensures reliable and predictable server operation. To expand functionality, you should implement modular platforms like MetaMod and SourceMod. These systems allow integration of a wide range of plugins, providing enhanced moderation, analytics, and game management capabilities. Special attention should be paid to designing a balanced map rotation cycle, which directly affects player retention. Properly configured map rotation maintains long-term community interest. Equally important is implementing a thoughtful administration system with clearly defined access rights. This ensures rapid response to incidents and minimizes operational risks. A key element of professional project positioning is integrating a domain name. Using a custom domain instead of an IP address increases brand recognition, simplifies user access, and builds trust. The domain becomes part of corporate identity and integrates easily into marketing materials. Implementing these measures comprehensively allows you to create a full-featured, reliable, and scalable gaming product, ready for your target audience and future development.

Valheim is a game that transports players to a vast fantasy world inspired by Norse mythology and Viking culture. Valheim combines elements of survival, exploration, and building. Its multiplayer mode has made it especially popular.  Pros: Atmosphere and immersion Interesting co-op gameplay Dynamically generated map Cons: There is no real plot — the goal is to survive, explore the world, and defeat bosses. The graphics, although cozy, noticeably lag behind modern projects and can still heavily load the graphics card. The building system is inferior, for example, to that implemented in Enshrouded. The combat system quickly becomes repetitive due to its monotony. Hosting a Valheim dedicated server is an excellent way to create a persistent world where you and your friends can play anytime. Setting up a dedicated server requires some basic knowledge of networking, Linux, and Docker. Preparing the VM Recommended requirements for a Valheim server: CPU: 4 RAM: 8 GB Disk: 20 GB Network: from 50 Mbit/s (the main factor is the server response latency (ping), ideally up to 50) Valheim server ports: 2456 — Game traffic 2457 — Steam Matchmaking The focus is on single-core performance, so even 4 cores are more than enough. Minimum requirements for CPU and RAM: 2 cores and 4 GB of RAM. We will create a cloud server in Hostman with the following parameters: OS: Ubuntu 24.04 CPU: 4 × 3.3 GHz RAM: 8 GB NVMe: 80 GB Connect to the server via SSH. You can get the login and password in the cloud server control panel under the Access tab. Next, update the packages and install Docker: apt update && apt upgrade -y curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh Create a directory to store the server files and navigate into it: mkdir /opt/valheim && cd /opt/valheim Launching the Valheim Server As a ready-made Docker image, we will use the project lloesche/valheim-server-docker. Create a compose.yaml file with the following content: services: valheim: image: ghcr.io/lloesche/valheim-server restart: always stop_grace_period: 2m cap_add: - sys_nice volumes: - ./server/config:/config - ./server/data:/opt/valheim ports: - 2456:2456/udp - 2457:2457/udp environment: - SERVER_NAME=HostmanServer - WORLD_NAME=skyrim - SERVER_PASS=secrett SERVER_PASS must be at least 6 characters long. SERVER_NAME must be at least 5 characters long (no special characters). To start the server: docker compose up -d Check status: docker compose ps Check logs: docker compose logs -f The first startup will take approximately 5–15 minutes, because the Valheim server needs to download the files and latest updates from Steam (about 3.2 GB). Make sure ports 2456 and 2457 are not blocked by a firewall and are accessible from the internet. You can check using the nmap utility or online port checking services like check-host.net (UDP port). After the server has started, in the logs you will see an entry like: valheim-1  | valheim-server 04/01/2025 20:39:33: Server is already the latest version To start playing on your server, launch Valheim from your Steam library. Choose Start Game → Join Game → Add Server. Enter IP:PORT. Each time you connect, the system will request the password that we set in the compose.yaml file. Additional Valheim Server Settings For more advanced server configuration, there are predefined variables that you can add to the compose.yaml file in the environment section: SERVER_NAME: My Server — server name as it appears in the server browser SERVER_PORT: 2456 — UDP port the server listens on WORLD_NAME: dedicated — world name (server directory will use this name, helpful for migrations) SERVER_PASS: secret — password for accessing the server, at least 6 characters SERVER_PUBLIC: true — whether the server should appear in the public server list (true) or not (false) SERVER_ARGS: "" — additional Valheim server command-line arguments ADMINLIST_IDS: Space separated list of admin SteamIDs — list of SteamID64 admins separated by spaces, you can view the ID in server logs or in-game by pressing F2 BANNEDLIST_IDS: Space separated list of banned SteamIDs — list of blocked SteamID64s separated by spaces PERMITTEDLIST_IDS: Space separated list of whitelisted SteamIDs — list of allowed SteamID64s separated by spaces CROSSPLAY: false — whether the server allows non-Steam clients to connect (true) or not (false) UPDATE_CRON: "*/15 * * * *" — update check schedule in cron format UPDATE_IF_IDLE: true — check updates only if no players are on the server RESTART_CRON: "10 5 * * *" — server restart schedule in cron format RESTART_IF_IDLE: true — only perform daily restart if no players are on the server TZ: Europe/Nicosia — timezone Other variables can be found on the project page on GitHub. To adjust the gameplay itself, you can use additional arguments in the variable: SERVER_ARGS: "-preset casual" Allowed values: Normal, Casual, Easy, Hard, Hardcore, Immersive, Hammer. For even more fine-tuned settings, you can use modifiers. For example, to disable raids: SERVER_ARGS: "-modifier raids none" Modifiers and their values: Combat: veryeasy, easy, hard, veryhard DeathPenalty: casual, veryeasy, easy, hard, hardcore Resources: muchless, less, more, muchmore, most Raids: none, muchless, less, more, muchmore Portals: casual, hard, veryhard Detailed description of modifiers Combat veryeasy: Player damage ×1.25, enemy damage ÷2, enemy speed and size ÷0.9 easy: Player damage ×1.1, enemy damage ÷1.33, enemy speed and size ÷0.9 normal: Base parameters 1:1 hard: Player damage ÷1.18, enemy damage ×1.5, enemy speed and size ×1.1 veryhard: Player damage ÷1.43, enemy damage ×2, enemy speed and size ×1.2 DeathPenalty casual: No equipment loss, minimal skill loss veryeasy: All items stay, smaller skill loss easy: All items lost, smaller skill loss normal: Standard death penalty hard: Equipment loss, faster skill loss hardcore: Full loss of items and skills on death Resources muchless: ×0.5 less: ×0.75 normal: ×1.0 more: ×1.5 muchmore: ×2.0 most: ×3.0 Raids none: Raids completely disabled muchless: Significantly reduced raid frequency less: Reduced raid frequency normal: Standard raid frequency more: Increased raid frequency muchmore: Significantly increased raid frequency Portals casual: Metals can be carried through portals normal: Standard item transfer rules hard: Cannot use portals during active boss fights veryhard: Portals completely disabled Features of the Game World and Interesting Facts There is no place for tenderness in Valheim. This world, woven from Norse myths and pixelated beauty, does not just challenge you — it tests your limits. Here, even the simplest actions can turn into a catastrophe, and victories come through blood, sweat, and countless funny stories. When a tree is your main enemy You swing your axe at a big tree in the meadows, confident in your strength. The final blow — and the trunk starts to fall with a crash, its branches catching on neighboring trees, the trunk bounces, flying straight towards your teammates… And suddenly the entire team is wiped out, surrounded by a fallen forest, smashed buildings, and the bitter realization that nature in Valheim is more dangerous than any monster. The sea calls You decided to go on a scouting trip: built your first raft, pushed off from the shore, drifting lazily on the waves. And then the current suddenly grabs you and pulls you far out to sea. Around you — endless water, and from the depths comes an ominous bubbling. You helplessly try to row back to shore. Painfully struggle your way home: minutes of cheerful sailing turn into hours of suffering. Trolls are the best architects Three hours of painstaking work. You built a fortress with high walls, carefully planned the defenses, placed torches — pride swells. But as soon as the sun sets behind the horizon, the earth trembles with heavy footsteps. Two blue trolls, swinging clubs, approach your gates. Within minutes, your buildings are reduced to a pile of splinters. You fought desperately, but your creation is now just a memory. Valheim does not forgive mistakes, but that is precisely its charm. Each failure is a story you will tell around the campfire. Each victory is a reason for pride. Here your ambitions will be broken, your hopes trampled, and your buildings destroyed. Conclusion What attracts players to Valheim most is its atmosphere and cooperative mode, where teamwork unlocks new opportunities and makes the game more engaging and varied. Even a seemingly simple game like this can draw you in for many hours in good company. For a comfortable experience, it is recommended to set up the server according to the preferences and wishes of the main players who want to take part in the adventures. Did you know? Hostman got you covered with servers with big amounts of storage for every project! Check our VPS Storage and start deploying now!

Satisfactory is a factory simulation game where your goal is to exploit an alien's planet natural resources and build and manage increasingly complex factories. Introduction to Satisfactory Satisfactory is a game that will appeal to people interested in engineering and design, and here’s why: Deep Production and Automation System The game allows players to build complex production chains, including resource extraction, processing, and the assembly of parts and components. Players can design and optimize their factories using various mechanisms and devices to automate processes. Optimization and Planning Efficient use of space, logistics planning, and resource flow optimization are essential here. System thinking and the ability to analyze production processes are valuable skills in this context. Scalability Production can grow from a small workshop to a massive industrial complex, providing opportunities to apply knowledge about scaling and managing large systems effectively. Experimentation and Creativity Experimenting with factory configurations and production processes encourages creativity and helps discover optimal solutions. Satisfactory offers engineers a rich environment to apply their knowledge and skills in design, optimization, and production process management. Its deep production system and constant drive for improvement make this game perfect for those who enjoy solving technical challenges and building complex systems. Cooperative Gameplay Setting up a multiplayer Satisfactory server is a great idea because when playing with two or more players, your progress through the technology tree accelerates exponentially. Each player can focus on their own tasks, working in parallel. One might handle the extraction of rare resources, another could focus on researching new technologies, while a third designs the next development stage of your factory. This division of labor saves time and allows players to immerse themselves deeply in a specific aspect of the game. You can become an expert in a particular area while your teammates do the same in others. Two Heads Are Better Than One Planning and strategy discussions become much more effective. You can jointly analyze actions, identify bottlenecks, and brainstorm solutions together. This collaborative approach often leads to innovative ideas that you might never come up with on your own. When working on complex projects, there's always a risk of mistakes or overlooked details. In cooperative mode, there's always an extra set of eyes to catch what you might miss. This is especially crucial in Satisfactory, where even a small planning error can have major consequences down the line. Flexibility and Spontaneity One of the main advantages of cooperative play is its flexibility. Players can easily join or leave the game without disrupting the overall process. This is particularly convenient if you have limited time or need to step away briefly. Spontaneous ideas and improvisation also become part of the gameplay. You might suddenly think of a new solution to a problem or a better optimization strategy and discuss it immediately with your teammates. The Social Aspect Interaction in Satisfactory goes beyond mere communication. It's also a great opportunity to share knowledge and experiences. You can exchange discoveries and discuss your optimal designs or your base's long-term strategy. In cooperative mode, you're not just playing together — you're creating a shared story. You set impossible goals to achieve alone and work toward them collectively. You'll find joy not only in your personal achievements but in your teammates' successes as well. Every completed research project and every new structure is a reason for the entire team to celebrate. Failures and mistakes affect not just one person but the whole team — making victories even sweeter. Building Unity and Responsibility Working on shared goals strengthens the sense of unity and responsibility. You'll start to feel that every player is an integral part of the team, and one person's success is everyone's success. Cooperative play in Satisfactory is more than just the sum of individual players — it's true synergy. It brings together the best elements of the game while adding teamwork, knowledge sharing, and social interaction. If you haven't tried cooperative mode yet, you absolutely should. You'll discover that the game becomes even more engaging and profound. So gather your friends, set up a server, and get ready for adventures in the world of Satisfactory. Technical Guide Let's move on to the practical part of our tutorial and set up a Satisfactory server. Useful Resources These Satisfactory resource may be helpful to you: Multiplayer Dedicated Servers GitHub Docker for Satisfactory Dedicated Server Server Requirements To run Satisfactory on your own server, make sure to meet the following requirements. CPU: 2 cores (the server utilizes multiple cores but prioritizes single-core performance) RAM: 8 GB Disk: 20 GB Network: At least 50 Mbps (the key factor is server response time (ping), ideally under 50 ms) Ports: 7777 TCP/UDP The official wiki states: "If this is a VM (a VPS most definitely is), a kvm64 CPU won't work!" This means that Satisfactory will not run on standard VDS/VPS servers with a kvm64 processor. To launch the server, you need either a dedicated (physical) server or a cloud server with dedicated cores (Dedicated CPU). For this guide, we used a server running Ubuntu 24.04. Installing the Necessary Components After creating the server and connecting to it, update the packages and install Docker: apt update && apt upgrade -ycurl -fsSL https://get.docker.com -o get-docker.shsudo sh get-docker.sh Create a directory for the server files: mkdir /opt/satisfactory   Navigate to the directory: cd /opt/satisfactory   Create a compose.yaml file with the following content: services: satisfactory-server: container_name: satisfactory-server image: wolveix/satisfactory-server:latest restart: unless-stopped ports: - 7777:7777 volumes: - ./satisfactory-server:/config environment: VMOVERRIDE: true MAXPLAYERS: 4 PGID: 1000 PUID: 1000 ROOTLESS: false STEAMBETA: false Here, the parameter VMOVERRIDE: true allows ignoring the CPU type and is not necessary for dedicated servers. You can find additional commands and configuration variables on GitHub. Launching the Server Start the server: docker compose up -d Check the server status: docker compose ps View logs: docker compose logs -f In the initial container logs, you will see the following: WARNING: VMOVERRIDE is enabled, skipping CPU model check. Satisfactory might crash!Checking available memory: 7GB detectedWARNING: You have less than the required 8GB minimum (7GB detected) of available RAM to run the game server. The server will likely run fine, though may run into issues in the late game (or with 4+ players). Upon the first launch, the server will download the game files and the latest updates (this process takes about 5 to 10 minutes). Connecting to the Server Start the game. Ensure you have the latest version installed. Navigate to Server Management → Add Server. Enter the external IP address assigned during server setup. A certificate warning will appear since no domain name or SSL certificate is in use. Click Confirm. On the first connection, the system will indicate that the server is new and unconfigured. Enter the server name and click Confirm. Create an administrator password. You will then gain access to the server control panel and settings. Hovering over any item will provide additional information. It is advisable to set a password for other players to join. Now you can create a game and select a starting location. Game creation takes 2-3 minutes, after which it becomes available for connection. Updating the Satisfactory Server If the client and server versions differ, connections will not be possible. Update process: Stop the container: docker compose down -v   Restart the server: docker compose up -d   The system will check for the latest available versions and download updates (5 to 10 minutes). Recommendations Cooperative mode does not provide a tutorial for game basics. New players are advised to first progress to oil extraction and processing in single-player mode to become familiar with the game. The key benefits of cooperative gameplay include planning, task distribution, and goal discussions. The in-game interface features a small notepad where all players can share and see messages.