This is a collection of regular issues that users run into when running an Assetto Corsa server, and how to avoid them!
The first thing you should do is have a look at your server logs and pick out any errors, they're usually a different colour (yellow or red) and quite descriptive. If you have an issue that isn't answered here please pop over to the Support channel on our Discord server. We'll be happy to help!
If you're using Content Manager and Custom Shaders Patch, please pay attention to the bottom left corner of the screen when loading into the game. Most error messages will be written there right before the game crashes.
Head over to the Accounts wiki page where the process of "forgotten password" is covered.
Firstly, make sure that your manager has started correctly. Take a look at your console window that is running ACSM, you should see something like this:
time="2222-22-22T22:22:22Z" level=info msg="initialising Prometheus Monitoring" time="2222-22-22T22:22:22Z" level=info msg="Server manager instance identifies as: a-bunch-of-random-numbers-letters" time="2222-22-22T22:22:22Z" level=info msg="starting assetto server manager on: 0.0.0.0:8772""
If the manager is running on your PC, simply enter
127.0.0.1:8772 into your browser to connect (The port that the manager will use is the port you set in
If the manager is running on a VPS or remote server, make sure the port has been opened in the firewall and forwarded correctly. Then enter the public IP of the server and it's port into your browser:
Updating ACSM is covered in our Updating To A New Version Guide.
data.acdfile and UI folder, and tracks require
surfaces.iniand a UI folder.
There are many things that could prevent a client from being able to connect to and drive on your server. Below are a few of the listed causes and recommended solutions.
Make sure your ACServer HTTP, UDP, and TCP ports (see below) are opened on the "incoming" side of your firewall, and forwarded correctly in your router. Usually if you are using a hosting server like a VPS then forwarding is done by the provider.
You can read more about port forwarding in our Advanced Setup Guide.
This is caused by either a full server or a locked entry list and means that the GUID of the connecting driver does not match a slot in the "entrants" list. If you're using a Race Weekend, Closed Championship or Custom Race with Locked Entry List turned on then ensure that the driver is listed in the entry list, and that the session has been started again using the appropriate session start buttons. Clicking the "restart" button top right will not update the entry list
Usually this error is shown by a server plugin that cannot confirm a client side feature. Common causes are sTracker checksums, and Real Penalty app requirements.
Please see the Troubleshooting section of the Checksums topic.
Try clearing your browser cache, Server Manager caches data extensively to help with page load performance. This can affect certain things to do with content such as layouts and pit boxes when uploading updated versions. The shortcut on most Chromium browsers is "control + shift + R".
This topic has now been moved to Sharing Content With Content Manager Wrapper.
Unfortunately we can't fix this, it seems like after a session the time of day reverses back to the start time set for the next weather. If your practice lasts three days (in game time) and you only have one weather configured then at the start of qualifying the time will reverse three days to get back to the weather start time. Alongside this there seems to be a bug where clients will get stuck with the time reversing/advancing quickly for even longer than you would expect.
This system is entirely controlled by the WeatherFX module in Custom Shaders Patch and therefore not possible to be fixed by ACSM.
Our only advice is to make sure the session wait times between sessions are long enough to allow CSP/Sol/Pure to stabilise the weather, especially if you're using large time multipliers.
As of ACSM v2.2.0 you can avoid this issue by turning on the "Use CSP Weather Transitions" switch, even if you are not using transitions the above problem will be solved.
This is an interesting one. If you're hosting an AC server from your machine and using an Oculus this can happen, you have two options:
1: Switch to using OpenVR in content manager instead of Oculus mode
2: Move your Server Manager .exe out of the root Assetto Corsa folder, having other
.exe files next to the
assettocorsa.exe confuses the Oculus software.
You probably need to make the manager "Open" so that Simresults can access the results files without account permissions, you can do this on the Server -> Accounts page.
This feature is also incompatible with exporting full championships.
This can be caused by few things:
Password Overridein your event config.
Server -> Current Configpage and scroll to the bottom. There are lines there that show what the current AC Server passwords are:
"name": "My Awesome AC Server", "password": "pass", "admin_password": "adminpass", "spectator_password": "watch",
Overly long sessions (It's not known where the cut-off is, somewhere longer than five hours) can cause ACTI to stop working completely, if ACTI isn't working for you in a session try reducing the length of the session. Generally running really long sessions in AC isn't a great idea anyway, we'd suggest looking into looping sessions instead.
Due to how the multiserver migration checks work, a Docker environment with a volume mounted shared_store.json folder will fail on first time setup of Server Manager. This is an issue from v2.1.7 until v2.3.0 of Server Manager. It will be fixed in v2.3.1 of Server Manager.
As a workaround, you can do the following:
docker-compose stop docker-compose rm -f rm -rf shared_store.json servers
Next, you need to run the multi-server manager outside of Docker in order to perform first time setup. You only need to do this once. Please do NOT re-make the shared_store.json or servers folders before doing this step
Let the assetto-multiserver-manager run until the message "Starting HTTP server" appears, then press
CTRL+C on your keyboard to stop it.
Finally, you should be able to run the Docker container as normal:
docker-compose up -d