Anything you find on this page is to use at your own risk. We are not liable for any damages that stem from bad configurations.
The original concept of the OmegaManager was to restrict access as much as possible. Because of this, the OmegaManager is only available from the local host (localhost, 127.0.0.1).
This is the recommended approach
To make the OmegaManager interface available to the public it is best to set up a reverse proxy using Apache, nginx or similar.
Setting up a reverse proxy can be achieved by following this guide: https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html
Additionally, it is recommended to set up a form of authentication (HTTP Basic Auth etc.) and to utilize HTTPS when communicating with the webserver.
ABSOLUTELY DO NOT USE THIS UNLESS YOU ARE AWARE OF THE RISKS AND KNOW HOW TO SECURE YOUR SYSTEM
The OmegaManager has a integrated "internet mode" which exposes the OmegaManager port to all available networking interfaces and launches a HTTPS server instead of HTTP with self-signed certificates. The generated certificates do not conform to any best practices and are generated in the `certs` directory.
To re-configure the OmegaManager for this following adjustments need to be made to the manager.cfg file:
"webserver": {
"port": 8081,
"internet_accessibility": true,
"authentication": true,
"username": "username",
"password": "changeme"
},
| Parameter | Description |
| port | Which port the OmegaManager listens on |
| internet_accessibility | Whether to expose the webserver to all interfaces or only bind to localhost |
| authentication | Enable HTTP basic auth |
| username | HTTP Basic Auth Username |
| password | HTTP Basic Auth Password |