OmegaManager uses an RCon based approach to lock, kick and send messages for its shutdown and update procedures. The configuration for the RCon interface is automatically loaded from your BattlEye RCon configuration folder.
Should the messaging no longer work - without configuration change - there are two possible reasons for this:
- RCon port has been double allocated
- RCon configuration has been doubled/copied and contains conflicting information
RCon port has been double allocated
Issue: Multiple game server deployments attempt to use the same RCon port. Only the first one to boot will reserve this port and the other RCon interface will simply fail to start.
Solution: Go through all RCon configuration files of all server deployments, and check the port configurations. If more than one deployment uses the same port, adjust the port. Also check if your firewall has opened this new port (host & provider)
RCon configuration has been doubled/copied and contains conflicting information
Issue: The BattlEye RCon folder contains more than one configuration file with conflicting configurations. This may happen if a server has been copied and the RCon port was not adjusted, or in rare cases if the RCon interface did not properly shut down, some files may double and leave leftover files which are not automatically cleaned up.
Solution: Open the RCon configuration folder (profiles/BattlEye) of the impacted server deployment and look for RCon configuration files. These may be called BEServer_x64.cfg or some variation of it containing additional random characters. If there are more than one, go through each and delete the one that contains outdated information. You should only have one configuration file in this folder.
