Yes, all of the race participants must have the skins installed to see them.
Misc AC Server Manager v1.7.9
- Thread starter Hecrer
- Start date
Yes, all of the race participants must have the skins installed to see them.
I started hosting an LA Canyons server, and the server itself is working great. But, unlike all the other LA Canyons servers available, when me and friends spawn in (or return to pit) we are all going to different locations all over the map. Does anyone know of a server setting in ACSM where I can select specific pit boxes for spawning in? Or something I can directly edit in the server files to fix this?
I also have the list of pit box locations from LAC so it shouldn't be a problem to map those out once I know the actual command/where to adjust this.
I also have the list of pit box locations from LAC so it shouldn't be a problem to map those out once I know the actual command/where to adjust this.
Thanks.
Also we have a interesting problem.
This night we completed our first race on Championship. But at the end of the race when i looked at Championship Point Table i saw that that someone who is kicked in qualifying is shown as 1st. All the results were wrong, so I used import feature. I selected race, qualify and practice sessions and still everything was wrong. Then I just imported only the race results and this time point table become correct.
Also when I look Entrants tab, some people raced until end but attendance showed as 0/1.
Why these problems happens? And how we can solve?
Also, some people who are not registered to tournament logged in to practice session. Also few players changed their cars (normally we selected cars for players). There is no advantage of system if these features aren't working
Thanks
Berkin
Last edited:
I keep running into this problem as well:
My docker compose file looks like this:
My home directory where the mount points for the container are created looks like this:
I used a more or less default version for the server config (acsm-config.yml)
I am a bit at a loss here, I followed the instructions and created the path /home/user/acsm-server and the /home/user/acsm-config.yml files before I ran docker-compose up.
I would assume that the paths inside the config yml file are all default and are used inside the container, so these wouldn't need to be touched right?
Anyway, it would be great if you can point me in the right direction
Code:
server-manager_1 | Error Details
server-manager_1 | -------------------------
server-manager_1 |
server-manager_1 | The error occurred attempting to: Open server manager storage (bolt or json)
server-manager_1 | The error more specifically is: mkdir assetto/manager: permission deniedMy docker compose file looks like this:
Code:
version: "3"
services:
server-manager:
image: seejy/assetto-server-manager:latest
ports:
# the port that the server manager runs on
- "8772:8772"
# the port that the assetto server runs on (may vary depending on your configuration inside server manager)
- "9600:9600"
- "9600:9600/udp"
# the port that the assetto server HTTP API runs on.
- "8081:8081"
# you may also wish to bind your configured UDP plugin ports here.
volumes:
# volume mount the entire server install so that
# content etc persists across restarts
- ./acsm-server:/home/assetto/server-manager/assetto
# volume mount the config
- ./acsm-config.yml:/home/assetto/server-manager/config.ymlMy home directory where the mount points for the container are created looks like this:
Code:
[user@server ~]$ ls -als
total 40
0 drwx------. 5 user user 191 May 5 19:20 .
0 drwxr-xr-x. 4 root root 28 May 4 19:50 ..
12 -rw-rw-r--. 1 user user 11553 May 5 19:19 acsm-config.yml
0 drwxrwxr-x. 2 user user 6 May 5 19:08 acsm-server
4 -rw-rw-r--. 1 user user 727 May 5 19:17 docker-compose.ymlI used a more or less default version for the server config (acsm-config.yml)
Code:
################################################################################
#
# Assetto Server Manager Configuration
# https://github.com/JustaPenguin/assetto-server-manager
#
# Thanks for using server manager!
#
#
# note that changes to this file require a restart of server manager to work! :)
#
#
# The below file is in YAML configuration format. Spacing is important within
# YAML, and can cause server manager not to launch correctly. You can validate
# this file online at: http://www.yamllint.com/
#
################################################################################
################################################################################
#
# steam settings - server manager can install the assetto corsa
# server for you using steamcmd (if you'd like)
#
################################################################################
steam:
# steam username and password. we recommend creating a separate account with
# steamguard disabled to use this application. Assetto Corsa Server is FREE
# so you don't need to worry about purchasing it again.
#
# server manager uses this information ONLY to install the
# assetto corsa server.
#
# however, if you do not wish to provide server manager with this information,
# leave it blank and install assetto corsa server to the path you specified in
# install_path (default: 'assetto')
username: steam_username
password: steam_password
# where to install assetto corsa server
install_path: assetto
# the path to the executable to run. relative to the install_path by default
executable_path: acServer
# set this to true to force an install every time the server manager is loaded
force_update: false
################################################################################
#
# http settings
#
################################################################################
http:
# hostname is the hostname the HTTP server should listen on.
# change '0.0.0.0' to 'localhost' if you don't want server manager to be
# available on the web.
hostname: 0.0.0.0:8772
# session key is used to encrypt the http session
session_key: <secret>
# server manager base URL is the URL that the server manager is accessible on
# used for ACSR integration and links in championship welcome message in game
# you can leave this blank if not required
# example: https://opengt3.assettocorsaservers.com <-- requires https:// or
# http://, no closing / at the end
server_manager_base_URL:
# session store type can be one of: 'cookie' or 'filesystem'
# if it is 'filesystem', you must set the session_store_path below.
# cookie is best for most users, but if you are running multiple Server
# Manager instances on the same IP address, you should use filesystem.
session_store_type: cookie
# session store path is where to save the session store
# (if using 'filesystem' above)
session_store_path: ""
tls:
# TLS configuration. Server Manager supports TLS v1.2 upwards. As of 12/03/2020,
# the Server Manager configuration yields a perfect score from SSL Labs.
# If you enable this, you likely want the hostname (above) to listen on port 443.
enabled: false
# the path to the SSL certificate file.
cert_path: ""
# the path to the SSL key file.
key_path: ""
################################################################################
#
# monitoring - enabling monitoring allows us to find out more information
# about how you're using Server Manager, as well as seeing any issues that may
# occur so we can collect and fix them. We understand that you may not wish
# for us to do any monitoring, so you can disable it by setting 'enabled'
# to false
#
################################################################################
# with monitoring enabled, the following systems are in place:
#
# 1. Sentry (https://sentry.io) monitoring of both Server Manager's backend
# code and frontend javascript. This lets us see application errors when
# they occur.
#
# 2. Google Analytics (https://analytics.google.com) tracking so we can see how
# many people use Server Manager, when they use it and where they are in
# the world.
#
# 3. Prometheus Monitoring - this provides more technical debugging in terms of
# memory and CPU usage, etc. This is *NOT* sent to us. We have added this in
# so that anybody who wants to monitor Server Manager for themselves can do
# so with Prometheus. We use it internally at assettocorsaservers.com to
# track our Server installs to help us improve our service.
#
# you can access the prometheus endpoint at:
# <your servermanager domain>/metrics
#
#
# once again, if you do not wish for Server Manager to do these things, simply
# set 'enabled' to false and monitoring will not take place.
################################################################################
monitoring:
enabled: false
################################################################################
#
# data storage - where server manager keeps your data!
#
################################################################################
store:
# store type: this can be one of:
# - 'json' - saves each custom race, championship as separate JSON files
# in the directory specified by store_path
# - 'boltdb' - saves all content inside a single database file specified by
# store_path
#
# boltdb is recommended for most users.
type: boltdb
# where to save the server manager data
path: server_manager.db
# shared data path: Set the same directory for multiple AC Server Manager
# instances to share accounts, race weekend, championship, entrants and custom
# events across them. Leave blank to use the same path as the one set up here.
# works only with JSON database
shared_data_path:
# check for new scheduled races not created by server manager on a loop. this is an experimental
# feature, and should not be used by most people. formats look like, e.g. 15s, 1m, 2h
# 0s == disabled. recommended values are 5m and above.
scheduled_event_check_loop: 0s
################################################################################
#
# user management - this is now mostly done via the web interface.
#
################################################################################
accounts:
# admin password override is used to override the admin password in the case
# that you have forgotten it. set it to e.g. 'password' and log in with:
# username: admin
# password: password
# and you will be prompted to change your admin password back to something you
# can remember
#
# If you are logging in for the first time, do not use this override system.
# Instead, log in by using these credentials:
# username: admin
# password: servermanager
# As soon as you log in, you will be immediately asked to set a new password.
admin_password_override:
################################################################################
#
# live map config
#
################################################################################
live_map:
# how often to refresh the map data in milliseconds. This value can't be below
# 200. If you find that championship events do not finish properly, try
# changing this to a higher number.
# set this to 0 to disable live map.
refresh_interval_ms: 250
################################################################################
#
# server config - configure plugins, e.g. kissmyrank here.
#
################################################################################
server:
# audit logging logs the actions of registered users locally on your server.
# Only Admins can access the logs, they are intended for tracking if users
# have deleted content, started/stopped events when they shouldn't have etc.
audit_logging: true
# performance mode disables live timing entirely, and prioritises low cpu
# usage.
performance_mode: false
# set this to 'true' if you don't want server manager to open a browser window
# on launch on windows
dont_open_browser: false
# set this to 'true' if you want server manager to scan content folders for
# changes every 15 seconds and update the search index with changes
# this is useful for multi-server setups with a shared content folder so that
# each server manager instance can see added/removed cars as they change
scan_content_folder_for_changes: false
# list of commands to run on server start and kill on server stop. this should
# contain the full command with arguments to run the given program.
#
# note: if you are looking for stracker support, Server Manager supports it via
# the UI! Go to the "STracker" page in Server Manager for more instructions.
#
# note #2: if you are looking for KissMyRank support, Server Manager supports it
# via the UI! Go to the "KissMyRank" page in Server Manager for more instructions.
#
# you can use additional plugins with AC Server Manager, but while configuring
# them you have to ignore the ports that AC Server Manager writes in the
# server_cfg.ini, as the Server Manager provides an interface to the plugins
# instead. The plugin ports in the Server Options page are the ones that must
# be used for the plugin configuration.
#
# Note that AC Server Manager provides an interface for a single plugin only,
# as the AC game server does. If you want to chain multiple plugins, please
# follow the documentation of the plugins you're using. Plugins usually
# feature interfaces so additional plugins can be chained between themselves.
#
# you can of course add your own commands (whatever you like!) here.
#
# each executable specified is run from the directory it is inside, for example,
# the command:
#
# /my/cool/plugin/path/run.sh --some-opt config.json
# now actually performs the following two commands:
#
# 1. cd /my/cool/plugin/path
# 2. ./run.sh --some-opt config.json
plugins:
# uncomment the two lines below to run the command '/my/cool/plugin/path/run.sh --some-opt config.json'
# - executable: /my/cool/plugin/path/run.sh
# arguments: ["--some-opt", "config.json"]
################################################################################
#
# championships
#
################################################################################
championships:
# reCAPTCHA is used to protect registration requests to championships. You
# must specify a site_key and secret_key to enable reCAPTCHA
# Register for reCAPTCHA here: https://www.google.com/recaptcha
# Please note you must register for reCAPTCHA v2.
#
# Note: reCAPTCHA is NOT required, but highly recommended if you are running
# Championship Sign Up Forms
recaptcha:
site_key:
secret_key:
################################################################################
#
# lua config - configure lua plugins
#
################################################################################
lua:
# lua plugins allow you to run custom lua scripts through hooks with server
# manager! If you're interested have a look at the server-manager/plugins
# folder to see some examples!
# Lua plugins are a premium feature, they won't run without the premium build!
enabled: falseI am a bit at a loss here, I followed the instructions and created the path /home/user/acsm-server and the /home/user/acsm-config.yml files before I ran docker-compose up.
I would assume that the paths inside the config yml file are all default and are used inside the container, so these wouldn't need to be touched right?
Anyway, it would be great if you can point me in the right direction
Last edited:
ça serait sympas de pouvoir intégrer la page Championnats sur notre site sans utiliser un ifram sa éviterais quand les gens qui s'inscrit le site de steam refuse la connection via une extention ifram
it would be nice to be able to integrate the Championships page on our site without using an ifram its would be avoided when people who register for the steam site refuse connection via an ifram extension
Rajouter dans la panneau administrateur un module d'intégration qui afficherais que la page championnats sur le site sa serais top.
Add in the administrator panel an integration module which would display that the championships page on the site would be top.
it would be nice to be able to integrate the Championships page on our site without using an ifram its would be avoided when people who register for the steam site refuse connection via an ifram extension
Rajouter dans la panneau administrateur un module d'intégration qui afficherais que la page championnats sur le site sa serais top.
Add in the administrator panel an integration module which would display that the championships page on the site would be top.
Last edited:
Hi,
there is a issue to load cars & setups content (every car).
The Message is: " Internal Server Error"
The LOG shows:
What is happend?
The system es running for more than 3 month fine.
Thanks for help
there is a issue to load cars & setups content (every car).
The Message is: " Internal Server Error"
The LOG shows:
Code:
time="2020-05-10T09:48:16+02:00" level=error msg="Could not load car details for: abarth500" error="invalid character 'P' looking for beginning of value"The system es running for more than 3 month fine.
Thanks for help
Hello, i was wondering where i can turn off track penaltys
such as wrong way offence etc etc?
such as wrong way offence etc etc?
sorry if this has been posted before, but i'm having trouble giving other users permission to start the application.
Ubuntu server
my account has sudo permission, but i want non root users to be able to start the program
ownership of the files are *my-admin-name* : race-organisers and have permissions of 776
can anyone give me a hint as to what the problem might be?
output of terminal from non root is
multiserver$ ./assetto-multiserver-manager
INFO[0000] Creating/Updating server 0 at: servers/SERVER_00
FATA[0000] Could not create assetto corsa multiserver instance error="chmod server-manager: operation not permitted"
Ubuntu server
my account has sudo permission, but i want non root users to be able to start the program
ownership of the files are *my-admin-name* : race-organisers and have permissions of 776
can anyone give me a hint as to what the problem might be?
output of terminal from non root is
multiserver$ ./assetto-multiserver-manager
INFO[0000] Creating/Updating server 0 at: servers/SERVER_00
FATA[0000] Could not create assetto corsa multiserver instance error="chmod server-manager: operation not permitted"
Hi. I have tried to upgrade to multiserver manager from server manager but it starts as if it was a brand new server without configured races a part from the default ones. If I put back the binary with the old single-server then I see my data again. The only non-standard thing that I do is to use json storage instead of boltdb.
I am using (a slightly modified version of) the docker-compose file that you provide in the multiserver directory.
Well, I think I need to better read the multiserver-specific documentation... I must have skipped some step.
I am using (a slightly modified version of) the docker-compose file that you provide in the multiserver directory.
Well, I think I need to better read the multiserver-specific documentation... I must have skipped some step.
Last edited:
Assuming I do have root access, how do I use this program with my rented web server?
Dear Joe Stevens.
We have purchased the premium version for our Simracers community.
We would like to know if it is possible with ACServerManager to open 2 servers simultaneously at the same time, is it possible to do it?
What is the procedure?
Thank you very much for your time and for your prompt response.
José Diaz
We have purchased the premium version for our Simracers community.
We would like to know if it is possible with ACServerManager to open 2 servers simultaneously at the same time, is it possible to do it?
What is the procedure?
Thank you very much for your time and for your prompt response.
José Diaz
Hi Robbe,
My first thought would be that you need to forward the ports for the AC server on your router/firewall, there are plenty of guides on this online if you search! If you've already done that then I'd need to have another look/think, let me know!
Thanks
Hi,
This is a new one to me, although it can be caused by some tracks that have incorrect values for the map size in their files, potentially could be caused by that? If not then I'm really not sure, would need to have a look at your logs, maybe an issue with the websocket.
Thanks
Everyone does need to download the skins, unfortunately AC has no support for automatically sharing skins through the game. You could upload the skins somewhere and share them through content manager, following this guide: https://github.com/JustaPenguin/ass.../Sharing-Content-With-Content-Manager-Wrapper. I hope that helps!
Thanks
Upload and run it as you would locally, but on the server. Server manager is compatible with Windows and Linux, so as long as your server is running one of those operating systems the manager should work just fine!
Thanks
Hi Jose,
It is possible! If you have a look inside the "multiserver" folder included with the premium download and read the instructions in the readme.txt while they should guide you through how to do it.
Thanks
Hi,
This is an interesting one! I've not experienced this behavior before , but we don't really run free roam maps ourselves. Perhaps there are layouts of the map with only one spawn point?
If there aren't then the only way you could control this is by locking the entry list to make sure your GUID connects to a certain pit box - each entrant in the entry list has a "Grid/Pit ID" that controls which pit box they will spawn in.
I hope that helps, thanks!
Thanks.
Also we have a interesting problem.
This night we completed our first race on Championship. But at the end of the race when i looked at Championship Point Table i saw that that someone who is kicked in qualifying is shown as 1st. All the results were wrong, so I used import feature. I selected race, qualify and practice sessions and still everything was wrong. Then I just imported only the race results and this time point table become correct.
Also when I look Entrants tab, some people raced until end but attendance showed as 0/1.
Why these problems happens? And how we can solve?
Also, some people who are not registered to tournament logged in to practice session. Also few players changed their cars (normally we selected cars for players). There is no advantage of system if these features aren't working
Thanks
Berkin
Hi,
If the results are wrong then Assetto has outputted them wrong, we don't modify them at all by default, we just display them. Unfortunately it can get a bit confused sometimes. You could try turning on "Fallback Results Sorting" on the server options page, which will do its best to manually sort the results, but it may not help.
Did you run your Championship as "Open"? This is the only way that other drivers would have been allowed to connect, or drivers would be able to connect in the wrong car, as otherwise the entry list would be locked. If you aren't running the championship as Open then I'm not sure what could have happened, I've never seen reports of behavior like this before.
If that is the case let me know, it might help if I had a look at the server!
Thanks!
I keep running into this problem as well:
Code:server-manager_1 | Error Details server-manager_1 | ------------------------- server-manager_1 | server-manager_1 | The error occurred attempting to: Open server manager storage (bolt or json) server-manager_1 | The error more specifically is: mkdir assetto/manager: permission denied
My docker compose file looks like this:
Code:version: "3" services: server-manager: image: seejy/assetto-server-manager:latest ports: # the port that the server manager runs on - "8772:8772" # the port that the assetto server runs on (may vary depending on your configuration inside server manager) - "9600:9600" - "9600:9600/udp" # the port that the assetto server HTTP API runs on. - "8081:8081" # you may also wish to bind your configured UDP plugin ports here. volumes: # volume mount the entire server install so that # content etc persists across restarts - ./acsm-server:/home/assetto/server-manager/assetto # volume mount the config - ./acsm-config.yml:/home/assetto/server-manager/config.yml
My home directory where the mount points for the container are created looks like this:
Code:[user@server ~]$ ls -als total 40 0 drwx------. 5 user user 191 May 5 19:20 . 0 drwxr-xr-x. 4 root root 28 May 4 19:50 .. 12 -rw-rw-r--. 1 user user 11553 May 5 19:19 acsm-config.yml 0 drwxrwxr-x. 2 user user 6 May 5 19:08 acsm-server 4 -rw-rw-r--. 1 user user 727 May 5 19:17 docker-compose.yml
I used a more or less default version for the server config (acsm-config.yml)
Code:################################################################################ # # Assetto Server Manager Configuration # https://github.com/JustaPenguin/assetto-server-manager # # Thanks for using server manager! # # # note that changes to this file require a restart of server manager to work! :) # # # The below file is in YAML configuration format. Spacing is important within # YAML, and can cause server manager not to launch correctly. You can validate # this file online at: http://www.yamllint.com/ # ################################################################################ ################################################################################ # # steam settings - server manager can install the assetto corsa # server for you using steamcmd (if you'd like) # ################################################################################ steam: # steam username and password. we recommend creating a separate account with # steamguard disabled to use this application. Assetto Corsa Server is FREE # so you don't need to worry about purchasing it again. # # server manager uses this information ONLY to install the # assetto corsa server. # # however, if you do not wish to provide server manager with this information, # leave it blank and install assetto corsa server to the path you specified in # install_path (default: 'assetto') username: steam_username password: steam_password # where to install assetto corsa server install_path: assetto # the path to the executable to run. relative to the install_path by default executable_path: acServer # set this to true to force an install every time the server manager is loaded force_update: false ################################################################################ # # http settings # ################################################################################ http: # hostname is the hostname the HTTP server should listen on. # change '0.0.0.0' to 'localhost' if you don't want server manager to be # available on the web. hostname: 0.0.0.0:8772 # session key is used to encrypt the http session session_key: <secret> # server manager base URL is the URL that the server manager is accessible on # used for ACSR integration and links in championship welcome message in game # you can leave this blank if not required # example: https://opengt3.assettocorsaservers.com <-- requires https:// or # http://, no closing / at the end server_manager_base_URL: # session store type can be one of: 'cookie' or 'filesystem' # if it is 'filesystem', you must set the session_store_path below. # cookie is best for most users, but if you are running multiple Server # Manager instances on the same IP address, you should use filesystem. session_store_type: cookie # session store path is where to save the session store # (if using 'filesystem' above) session_store_path: "" tls: # TLS configuration. Server Manager supports TLS v1.2 upwards. As of 12/03/2020, # the Server Manager configuration yields a perfect score from SSL Labs. # If you enable this, you likely want the hostname (above) to listen on port 443. enabled: false # the path to the SSL certificate file. cert_path: "" # the path to the SSL key file. key_path: "" ################################################################################ # # monitoring - enabling monitoring allows us to find out more information # about how you're using Server Manager, as well as seeing any issues that may # occur so we can collect and fix them. We understand that you may not wish # for us to do any monitoring, so you can disable it by setting 'enabled' # to false # ################################################################################ # with monitoring enabled, the following systems are in place: # # 1. Sentry (https://sentry.io) monitoring of both Server Manager's backend # code and frontend javascript. This lets us see application errors when # they occur. # # 2. Google Analytics (https://analytics.google.com) tracking so we can see how # many people use Server Manager, when they use it and where they are in # the world. # # 3. Prometheus Monitoring - this provides more technical debugging in terms of # memory and CPU usage, etc. This is *NOT* sent to us. We have added this in # so that anybody who wants to monitor Server Manager for themselves can do # so with Prometheus. We use it internally at assettocorsaservers.com to # track our Server installs to help us improve our service. # # you can access the prometheus endpoint at: # <your servermanager domain>/metrics # # # once again, if you do not wish for Server Manager to do these things, simply # set 'enabled' to false and monitoring will not take place. ################################################################################ monitoring: enabled: false ################################################################################ # # data storage - where server manager keeps your data! # ################################################################################ store: # store type: this can be one of: # - 'json' - saves each custom race, championship as separate JSON files # in the directory specified by store_path # - 'boltdb' - saves all content inside a single database file specified by # store_path # # boltdb is recommended for most users. type: boltdb # where to save the server manager data path: server_manager.db # shared data path: Set the same directory for multiple AC Server Manager # instances to share accounts, race weekend, championship, entrants and custom # events across them. Leave blank to use the same path as the one set up here. # works only with JSON database shared_data_path: # check for new scheduled races not created by server manager on a loop. this is an experimental # feature, and should not be used by most people. formats look like, e.g. 15s, 1m, 2h # 0s == disabled. recommended values are 5m and above. scheduled_event_check_loop: 0s ################################################################################ # # user management - this is now mostly done via the web interface. # ################################################################################ accounts: # admin password override is used to override the admin password in the case # that you have forgotten it. set it to e.g. 'password' and log in with: # username: admin # password: password # and you will be prompted to change your admin password back to something you # can remember # # If you are logging in for the first time, do not use this override system. # Instead, log in by using these credentials: # username: admin # password: servermanager # As soon as you log in, you will be immediately asked to set a new password. admin_password_override: ################################################################################ # # live map config # ################################################################################ live_map: # how often to refresh the map data in milliseconds. This value can't be below # 200. If you find that championship events do not finish properly, try # changing this to a higher number. # set this to 0 to disable live map. refresh_interval_ms: 250 ################################################################################ # # server config - configure plugins, e.g. kissmyrank here. # ################################################################################ server: # audit logging logs the actions of registered users locally on your server. # Only Admins can access the logs, they are intended for tracking if users # have deleted content, started/stopped events when they shouldn't have etc. audit_logging: true # performance mode disables live timing entirely, and prioritises low cpu # usage. performance_mode: false # set this to 'true' if you don't want server manager to open a browser window # on launch on windows dont_open_browser: false # set this to 'true' if you want server manager to scan content folders for # changes every 15 seconds and update the search index with changes # this is useful for multi-server setups with a shared content folder so that # each server manager instance can see added/removed cars as they change scan_content_folder_for_changes: false # list of commands to run on server start and kill on server stop. this should # contain the full command with arguments to run the given program. # # note: if you are looking for stracker support, Server Manager supports it via # the UI! Go to the "STracker" page in Server Manager for more instructions. # # note #2: if you are looking for KissMyRank support, Server Manager supports it # via the UI! Go to the "KissMyRank" page in Server Manager for more instructions. # # you can use additional plugins with AC Server Manager, but while configuring # them you have to ignore the ports that AC Server Manager writes in the # server_cfg.ini, as the Server Manager provides an interface to the plugins # instead. The plugin ports in the Server Options page are the ones that must # be used for the plugin configuration. # # Note that AC Server Manager provides an interface for a single plugin only, # as the AC game server does. If you want to chain multiple plugins, please # follow the documentation of the plugins you're using. Plugins usually # feature interfaces so additional plugins can be chained between themselves. # # you can of course add your own commands (whatever you like!) here. # # each executable specified is run from the directory it is inside, for example, # the command: # # /my/cool/plugin/path/run.sh --some-opt config.json # now actually performs the following two commands: # # 1. cd /my/cool/plugin/path # 2. ./run.sh --some-opt config.json plugins: # uncomment the two lines below to run the command '/my/cool/plugin/path/run.sh --some-opt config.json' # - executable: /my/cool/plugin/path/run.sh # arguments: ["--some-opt", "config.json"] ################################################################################ # # championships # ################################################################################ championships: # reCAPTCHA is used to protect registration requests to championships. You # must specify a site_key and secret_key to enable reCAPTCHA # Register for reCAPTCHA here: https://www.google.com/recaptcha # Please note you must register for reCAPTCHA v2. # # Note: reCAPTCHA is NOT required, but highly recommended if you are running # Championship Sign Up Forms recaptcha: site_key: secret_key: ################################################################################ # # lua config - configure lua plugins # ################################################################################ lua: # lua plugins allow you to run custom lua scripts through hooks with server # manager! If you're interested have a look at the server-manager/plugins # folder to see some examples! # Lua plugins are a premium feature, they won't run without the premium build! enabled: false
I am a bit at a loss here, I followed the instructions and created the path /home/user/acsm-server and the /home/user/acsm-config.yml files before I ran docker-compose up.
I would assume that the paths inside the config yml file are all default and are used inside the container, so these wouldn't need to be touched right?
Anyway, it would be great if you can point me in the right direction
Hi,
I think this is happening because the directory has been volume mounted before it exists, so the assetto folder has been created with root permissions, and then server manager can't run mkdir inside it.
The easiest solution would be to manually create the directories before running docker-compose.
I hope that helps, thanks!
Unfortunately as far as I know you can't turn off the one way offence on an online server, all of the penalties that you can change are in the "Rules" section of the race form.
Thanks
