Introduction
Configure the Iguana Web Server.
This is the built in web server used by Iguana’s user interface. The web server port is also used to connect to Iguana for remote administration and monitoring etc. Iguana does not use an external web server such as Microsoft IIS or Apache.
From here you can set the Web Server Name, Port, Session Timeout and enable HTTPS.
Basic Configuration [top]
Click Edit to change settings, enter the desired settings then click Save Changes and Restart Web Server.
Server name
- Specify the name of your Iguana Server
- To include an Environment Variable in the Server Name, use ${variable name}
The Server Name will be previewed like this:
Setting the server name is helpful in environments where there are multiple Iguana servers that need to differentiated.
Allowable Login Failures
- If this setting is exceeded the user is locked out for 5 minutes
Session Timeout
- If the user is idle for longer than this they will be logged off
Web Server Port
- The default web server port is 6543.
- If this port is not available you must choose another port.
- In Iguana 6.1.2 and newer, you can use an environment variable in this field, just like for the server name.
Use HTTPS
- Sets the server to use secure HTTP
- The public/private key files must be in PEM format and cannot be password protected
- The certificate file must be x509 in PEM format and cannot be password protected
- HTTPS uses the Web Server Port (or the dedicated port specified in the HTTP(S) Channel Settings) for TCP, instead of port 80 that is used for HTTP
Enabling HTTPS Support [top]
Iguana’s HTTPS functionality is useful for ensuring that confidential data remains private. It is also secures changes made within the Dashboard, as these changes will be encrypted within your browser’s HTTPS layer. The acknowledgement that you receive from the web server will also be encrypted, and will be decrypted using your browser’s HTTPS sub-layer.
- Check Use HTTPS to enable HTTPS support
- Select the key files, this must be in PEM format and cannot be password protected
- Select the certificate file, this must be x509 in PEM format and cannot be password protected
- Click Save Changes and Restart Web Server to save your changes and restart the web server
- Verify that HTTPS is working by browsing to your secured Iguana instance, for example: https://localhost:6543/dashboard.html
Note: http://localhost:6543/dashboard.html will no longer work
You can use the view certificate link to view the certificate details:
