Skip to main content
Version: 6.10.0

HTTP Connection Setup

For security the Portal UI can only be accessed in a browser over HTTPS. This is the default configuration, running on port 8443, using a provided self-signed certificate.

However the Portal service can be configured to run over HTTP if there is a secure load balancer or proxy in between the browser and the Portal service.

In addition a HTTP port can be configured in addition to the HTTPS port, for insecure Agent connections.

1. Switching to HTTP connection​

It will not be possible to log into the Portal UI if the service is directly accessed over HTTP. The following configuration will only work if a load balancer or proxy is in between the browser and the service.

  1. To start the Portal over HTTP, ensure the file application.properties already exists. if not already present, see section Create application.properties to create.
  2. Add the following flag to application.properties
server.port=<HTTP port number, e.g. 80 or 8080>
server.ssl.enabled=false

When started the Portal log will confirm the port and protocol in its startup message, for example:

INFO 29495 --- [main]o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''

2. Setting up an additional HTTP port for Agent connections​

There is an additional property server.http.port that can be used to specify a dedicated HTTP port - the value must be a valid port number, otherwise the service will not start. This is designed to allow Agents connect over an insecure HTTP connection, while the UI runs on HTTPS. The HTTP port is in addition to the default HTTPS port configured using the server.port property. For example, to configure HTTP on port 8080 add the following line to the application.properties:

server.http.port=8080

When started the Portal log will confirm the ports and protocols in its startup message, for example:

INFO 80782 --- [main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8443 (https) 8080 (http) with context path ''

Waratek Agents can connect to this HTTP port with the following settings in the Agent waratek.properties:

com.waratek.ControllerPort=8080
com.waratek.ControllerSecure=false