Proxy
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.
Native webserver
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 are self-signed and thus not recommended to use in production. They will be stored 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 |
