1) Upgrading to Premium

Upgrading to Premium or ACSM v2

First of all, thank you very much for considering the upgrade to the premium version of Server Manager, every purchase helps us develop new great features and is very appreciated!

If you upgrade you'll get access to a download of the premium version of the manager, and there are a few different ways to upgrade, I'm going to go through those methods in this guide!

This guide is written with Windows users in mind (apart from the bit about docker), but Linux users should be able to translate the steps pretty easily.

On Windows, we recommend something like Visual Studio Code or Notepad++ for editing .yml files!

If you have any problems, please don't hesitate to ask questions in one of the following places:

These places are not checked often, but useful to search through if you have an issue.

Single Server - Clean Install

Hopefully you've done this before

If you're not worried about keeping your existing configuration, results, events etc. you can start from scratch with the new version of the manager. The install process is exactly the same as the free version, so you shouldn't encounter any issues if you've done that before!

Extract the premium manager folder to your preferred location
Edit config.yml to set your preferences, make sure to set up the steam: section, the manager won't work without it. Tip: If you're struggling with steamCMD it's usually easiest to set username and password to blank, install the server manually (just copy the server folder from your AC install next to server-manager.exe) and set the install path to ./server or similar.
After configuring the steam:, feel free to read the rest of the configuration file and change things as you see fit. We've tried our best to make the defaults be as sensible as possible, but you can tune things to your liking here.
Run server-manager.exe. On Windows, this will open your browser window. If you're on Linux, you'll need to manually open the URL: http://localhost:8772 in your browser.
Log in to Server Manager. You can do this with the "Login" link underneath the Person icon in the navigation. You'll need the default username and password to get in, they are:
```
username: admin
password: servermanager
```
When you log in, you will be immediately prompted to change your password. You can add new accounts at any time from the server manager web interface.
Party

Single Server - Keeping Existing Data

The easy way

If you want to keep existing content, but don't want to run a multi-server setup you can follow these steps!

Extract the premium manager folder to your preferred location
Copy the premium server-manager.exe into your existing manager folder, replacing the old free version
Start the manager, you should be good to go!

Multi-Server - Clean Install/Keeping Existing Data

The fun way

Multi-Server is only supported by Server Manager v1.6.0 and above

If you want to update to a multi-server install that's great, it's a really nice feature if you run multiple servers. If you want to keep your existing data for a multi-server install, follow these steps!

Extract the premium manager folder to your preferred location
Navigate to the multiserver folder inside the extracted folder
Open servers.yml
Change the 'servers' number to how many Assetto Corsa servers you want and save
Copy the premium server-manager.exe and config.yml into the multiserver folder, alongside servers.yml and assetto-multiserver-manager.exe
If you set the install_path to a value and you are not using steamcmd to install Assetto Corsa, make sure that the Assetto Corsa server is installed in that path. If you are using steamcmd, please make sure that steamcmd is in your system's PATH variable.
Run the Assetto assetto-multiserver-manager.exe!
If you're using a JSON store you now need to copy across your old store data. Look in the multiserver folder for shared_store.json then copy your old JSON store files into that directory. You should then see custom races, accounts, championships and race weekends from your old install on each of your multi-server instances. If you don't want to keep existing data skip this step
If you're using a bolt store unfortunately it is not possible to transfer your store at this time. We are working on a method to do this though, so contact us if you are interested
Now you need to go through each of your servers using the server switcher (the server icon in the top right of Server Manager) and set up their settings correctly. Note that each server will need its own ports for TCP Port, UDP Port, HTTP Port and Content Manager Wrapper Port in the Server Options. Be sure to set the server name too, so you can easily identify which server is which!

Multi-Server - Docker

Advanced users only, probably

Linux only!

If you want to run Server Manager in a Docker container be aware that Docker isn't necessarily an easy plug-and-play system, it does require a bit of time to get used to!

First, follow steps 1-5 in section 3 of this guide, then follow these steps!

Make sure that Dockerfile and docker-compose.yml are both next to server-manager
Open docker-compose.yml, you need to assign ports for each server instance and volume mount any required directories, for example if you have an assetto folder with the Assetto Corsa server inside it, you need to mount that directory. docker-compose.yml has some default ports and volume mounts set up already, use them as a guide!
If you're running any server plugins remember that their ports need to be assigned too!
Make sure that any directories volume mounted in docker-compose.yml have been created without admin permissions
In cmd cd to the folder containing Dockerfile and run docker-compse up -d

ludlem76

Provide feedback

Saved searches