Troubleshooting & Help ‐ Need help ? ‐ Common issues and their solutions - MarechJ/hll_rcon_tool GitHub Wiki

🧭 You are here : Wiki home / Troubleshooting & Help / Need help ? / Common issues and their solutions


[!NOTE] The shell commands given below assume your CRCON is installed in /root/hll_rcon_tool.
You may have installed your CRCON in a different folder.
If so, you'll have to adapt the commands below accordingly.

[!TIP]
See this guide to get into a SSH terminal prompt.


Menu

Installing

Updating

Using

Tweaking


🆘 CRCON doesn't start

  • First check you have pulled the correct Docker containers images and restart :
    You'll find the current version numbers to use in the git checkout command on the Releases Tags page :

    image

    cd /root/hll_rcon_tool
    git fetch --tags
    git checkout v11.1.0
    docker compose pull
    docker compose down
    docker compose up -d --remove-orphans
    
  • If it still doesn't start, you may have a configuration error.
    We'll have to check two files.

    • compose.yaml

      • If you only manage one game server in CRCON,
        make sure you're using the right compose.yaml file version :
        cp /root/hll_rcon_tool/compose.yaml /root/hll_rcon_tool/compose.yaml.old
        rm /root/hll_rcon_tool/compose.yaml
        cp /root/hll_rcon_tool/docker-templates/one-server.yaml /root/hll_rcon_tool/compose.yaml
        
      • If you manage more than one game server in CRCON,
        you'll have to edit the "10 servers version" to fit your needs.
        cp /root/hll_rcon_tool/compose.yaml /root/hll_rcon_tool/compose.yaml.old
        rm /root/hll_rcon_tool/compose.yaml
        cp /root/hll_rcon_tool/docker-templates/ten-servers.yaml /root/hll_rcon_tool/compose.yaml
        
        Edit /root/hll_rcon_tool/compose.yaml, following the installation procedure instructions.
        Basically, it's just about deleting the unused servers parts.
        You don't have to enter any information.
    • .env
      This is the main configuration file where CRCON finds the Game server's RCON IP and credentials.
      Check the parameters values you've entered are correct, as described in the installation procedure instructions.

      • :warning: If you've already set a HLL_DB_PASSWORD= value : do NOT change it !
      • :warning: If you've already set a RCONWEB_API_SECRET= value : do NOT change it !
      • Double check the RCON IP in HLL_HOST=
      • Double check the RCON port in HLL_PORT=
        :warning: It is NOT the same as the game server (query) or SFTP ports.
      • Double check the RCON password in HLL_PASSWORD=
      • ... repeat process for server #2, #3, etc if you manage more than one game server.

    Now you're sure about these two files, try to restart CRCON :

    cd /root/hll_rcon_tool
    docker compose down
    docker compose up -d --remove-orphans
    

    If CRCON still doesn't start,
    ask for help on CRCON's Discord tech-support channel.
    Don't forget to say you've already been through these diagnosis steps.


🆘 I can't get into the CRCON interface at all

  • Check for your CRCON Docker containers statuses :

    cd /root/hll_rcon_tool
    docker compose ps
    

    All should be up and running :

    image

    If all containers are up :
    CRCON is working the way it should.

    • check you're using the right url to access your CRCON.
      By default, it's located in http://(your VPS IP):8010 (first -or only- server)
    • If you're using a domain name, try using the IP instead.
    • If you're using https://, try using http:// instead.
    • On your PC : check for any firewall or proxy that could block your VPS IP and/or 8010 port.
    • On your VPS : check for any firewall or proxy that could block your PC IP.

    If one containers isn't up :

    • try to relaunch CRCON :
      cd /root/hll_rcon_tool
      docker compose down
      docker compose up -d --remove-orphans
      
      Wait for one minute or two, then recheck for the containers statuses.
      cd /root/hll_rcon_tool
      docker compose ps
      
      • If one of them is still down or restarting in loop (compare CREATED and STATUS times) :
        Ask for this container's logs (choose the relevant command line) :
        docker compose logs backend_1 --tail 200
        docker compose logs frontend_1 --tail 200
        docker compose logs maintenance --tail 200
        docker compose logs postgres --tail 200
        docker compose logs redis --tail 200
        docker compose logs supervisor_1 --tail 200
        
        If you don't see/understand any obvious error message,
        ask for help on CRCON's Discord tech-support channel.
        Don't forget to say you've already been through these diagnosis steps.
        You also should show the logs you've got (copy-paste them in https://privatebin.net/ and share the link)

🆘 I can enter the CRCON interface, but I can't see any data from my game server

A fully working and well-configured CRCON should display something like this :

image (the red zones are the ones where you should see your game server's data)

If any of these are blank or returning a "no data" status : CRCON can't retrieve them for some reason.

● Check the game server is running

Yep. That may sound a bit "easy", but... ;)

● Double-check the game server's parameters values in .env file :

  • HLL_HOST=
  • HLL_PORT=
    :warning: It is NOT the same as the game server (query) or SFTP ports.
  • HLL_PASSWORD=

[!IMPORTANT] Any change made to the .env file requires a CRCON restart to be taken in account.
Restarting CRCON Docker containers :

cd /root/hll_rcon_tool
docker compose down
docker compose up -d --remove-orphans

● Check for your CRCON Docker containers statuses :

cd /root/hll_rcon_tool
docker compose ps

All should be up and running :

image

If one of these isn't up and running : please follow this guide.


🆘 I can't get into admin panel, CRCON returns a "CSRF" error

  • First time you're trying to enter ?
    -> You must have missed the step #5 of the installation procedure
  • It was working before ?
    -> You may have moved CRCON to a new VPS (or your VPS IP has changed, or you changed the private UI port) and forgot to redo that mandatory step.

🆘 I can't update CRCON : I get an error when I enter the git checkout command

You may have modified one or more files that need to be updated.
As it doesn't want you to loose your modified files, Git refuses to replace them with the newer official versions.

If you have modified these files for a reason, you'll have to make a backup of them (so you'll keep your modifications handy if you want to redo them in the new file).

Let's say Git complains about finding this modified file : rcon/hooks.py
Her's how to make a backup of it and restore the original version :

cd /root/hll_rcon_tool
cp rcon/hooks.py rcon/hooks.py.old
git restore rcon/hooks.py

Now you can retry the git checkout command and, as long as you've restored all the modified files to their original versions, it should not complain anymore.

You may then redo the modifications you previoulsy made in the files.


🆘 I've updated CRCON following the official procedure, but its version remains the same

Check your .envfile for the TAGGED_VERSION= parameter value.
It should read :

TAGGED_VERSION=latest

If you have any other string than latest after the = sign, change it to latest.

Then redo the official update procedure.


🆘 I've changed HLL_DB_PASSWORD= in the .env file, now CRCON doesn't start

You changed the PostgreSQL database password in .env while the database has already been used ?
Now your CRCON can't access it anymore, as the database container still expects the "old" password.

These commands can change the database password to match the one you've set for HLL_DB_PASSWORD= in the .env file.

:warning: Check the comments in the .env file for forbidden characters, such as ?, %, $, @, :, / or !.
Keep it "simple", as the postgres Docker container will never be exposed out of the Docker environment :
You'd better only use alphanumeric characters (a-z, 0-9).

cd /root/hll_rcon_tool
docker compose down
docker compose exec -it postgres psql -U rcon -c "ALTER USER rcon WITH PASSWORD 'YourNewPassword';"
docker compose up -d --remove-orphans

🆘 I've changed RCONWEB_API_SECRET= in the .env file, now I can't log into CRCON anymore

The RCONWEB_API_SECRET= parameter value is used to scramble the users passwords before storing them in the database.

Changing it after having the users accounts created will invalidate existing passwords.

You have two choices to get out of this situation :

  • put the previous (working) RCONWEB_API_SECRET= value back
  • recreate users accounts

Recreating users accounts will require you to log into the CRCON admin panel.
As you can't use any existing "superuser" account anymore, you won't be able to log in until you create a new "superuser" using this procedure.


🆘 I have lost/don't have access to the admin panel

You lost your only "superuser" account's password ?
The only person who has "superuser" status is missing ?

-> You can get "superuser" status or create a new "superuser" account.

Get "superuser" status

This command will enable "Superuser" status on any existing "normal" CRCON account,
this user will then be able to administrate other users in the Admin panel.

(Change yourusername to an existing username account in the following command)

cd /root/hll_rcon_tool
docker compose exec -it postgres psql -U rcon -c "UPDATE auth_user SET is_superuser = true WHERE username = 'yourusername';"

Create a new "superuser" account

These commands will allow to create a new "superuser"

  1. Get the backend container instance name

    cd /root/hll_rcon_tool
    docker ps
    

    -> you'll usually find this : hll_rcon_tool-backend_1-1

  2. Enter backend container bash
    (adapt the command if your container has another name)

    docker exec -it hll_rcon_tool-backend_1-1 bash
    
  3. Create a new "superuser"

    python rconweb/manage.py createsuperuser
    

    You'll get some prompts where you'll define a username, its e-mail address (can be left blank) and its password (2 times).


🆘 My Discord webhooks don't work (anymore)

Discord webhooks configurations are pretty straightforward : enter the url in the settings area and they should work.

  • If your webhook never worked :
    You may have a typo in the url, or it hasn't been defined as expected in the json CODE window (though there is a json syntax check that should prevent to enter badly formatted code).
  • If your webhook suddenly stopped from working :
    You may face a Discord webhook rate limitation.
    See this guide to verify your Discord server has been limited and get instructions to get out of this limitation.

🆘 I tried to increase NB_API_WORKERS in the .env file and I get various errors

As said in the .env file, increasing NB_API_WORKERS parameter value should get you "better performance".
In fact, several people tried to increase it and only got database access errors and/or API commands failures.

This often happens if you are managing more than one game server in CRCON, but can occur using only one, too.

As the promised "better performance" remains to be proven anyway, you're advised to NOT increase NB_API_WORKERS parameter value.

If you did so, revert it back to 1 and restart CRCON.