HTTP Server Config

Use this page to configure the HTTP Server Port on which the web server will run.

Select Network Configuration / HTTP.

For receivers activated after 1 August 2025 or receivers upgraded to v6.43 /5.83 and later. When the receiver is reset to its default settings, HTTPS is enabled and HTTP is disabled. To access the web interface when connected to the Wi-Fi access point, you will need to enter https://192.168.142.1 in the address bar of your web browser. For receivers activated for the first time prior to the release of version 6.43, you may need to manually disable HTTP and enable HTTPS or clear all receiver settings to change the HTTP server configuration defaults.

HTTP Server Port – Enter the port number for the HTTP server. The default is port 80.

HTTP Secure Enable – Enter a port number (the default is 443) and update your port forwarding rules (if applicable). You can then access the secure port by using the "https://" extension.

These settings are only available if the HTTPS option is installed. See Receiver Options – Details.

The receiver can support a secure HTTP link, with encryption limited to a 56-bit encryption.

BootMonitor HTTP – For receivers activated after 1 August 2025 or receivers upgraded to v6.43/5.83 and later. A BootMonitor HTTP check box enables HTTP access to the receiver's boot monitor. This is used when the receiver enters the boot monitor state, such as after continuous crashes. In this state, you can reinstall or upgrade the firmware. This feature must be enabled before the BootMonitor state can be accessed remotely via HTTP. Selecting this check box prompts the following message to appear: Warning: Enabling this feature is a security risk. Proceed?. Click OK to continue. In the Network Security Risks section of this screen, the status of this state is shown.

BootMonitor IP Port – For receivers activated after 1 August 2025 or receivers upgraded to v6.43/5.83 and later. A BootMonitor IP Port check box appears after you select the BootMonitor HTTP check box. The receiver IP port of 9999 can be used to send the boot monitor's TRIMCOMM DCOL commands to the receiver. Selecting this check box prompts the following message to appear: Warning: Enabling this feature is a security risk. Proceed?. Click OK to continue.

---

Network Security Risks

This list indicates the possible security risks associated with the receiver. Implementing HTTPS and High Security mode improves the security of the device, but you should also minimize all the different points where an unauthorized user could get into the system. All services that are not required should be disabled. For example:

• If the application does not require the FTP server, turn it off. See FTP Server Configuration.

• If HTTPS is active, turn off HTTP. See HTTP Enable.

• Is HTTPS needed? If the application does not require web access, both HTTP and HTTPS can be disabled. See HTTP Enable and HTTP Secure Enable.

• If service discovery is not required, then turn off mDNS, UPnP, and NETBIOS. See Network Service Discovery Configuration. These features are very useful during integration and development, but may not be used in the end application and can become security vulnerabilities.

• If NTP is not required, disable it. See NTP Configuration.

• Disable all unused TCP/IP and UDP connections. See I/O Configuration. Only allow inbound connections on the remaining ports if the use case requires it. The ports can be configured as output only, if the application only requires information from the receiver make sure the port(s) are set to output only.

• If HTTP and/or HTTPS must be enabled, make sure that the user accounts have the appropriate permissions.

• Enable the High Security mode. See High Security.

• Enable access to the BootMonitor via HTTP. See BootMonitor HTTP.

  • If this option is turned on, the message shows Risk. Enabled BootMonitor HTTP.

  • If this option is turned off, the message shows OK. Disabled BootMonitor HTTP.