ANEURISM IV server will not stop or does not appear in the list

These are the ANEURISM IV problems that reach our support queue most often.

1. The server sits in a stopping state

ANEURISM IV does not always act on a polite stop signal, so the panel can wait a long time for a process that has already decided to ignore it.

1. Give the stop around thirty seconds.
2. If the console is idle and the state has not changed, use the panel's Kill option to end the process.
3. Wait for the state to read offline before you start it again. Starting during a stop is what leaves a server stuck.

2. The server is not in the browser

• Give it a minute after boot. The listing depends on the query port answering.
• Check the console for a line confirming the server registered.
• Send players the connect <ip> console command with your IP and port. That path does not depend on the list at all.

3. Players are refused

• Check the player limit set by the -maxplayers launch parameter.
• Check whether a password is set as a launch parameter as well as in aniv.cfg. The launch parameter wins, so the password you are telling people may not be the one in force. Clear one of them.
• Confirm everyone is on the same game version. Restart the server after a game update so it updates too.

4. Config changes are ignored

• Stop the server before editing. The config is rewritten from memory on shutdown.
• ranks.json must be valid JSON or the whole file is skipped.
• Read the first lines of the console after a start. Parse errors appear there.

If the server keeps stopping on its own, open a ticket with the last 50 lines of the console. A process that is killed for memory looks different from a game error, and we can tell which one it was.