Skip to main content

HTTP(S) FAQ

Frequently Asked Questions for Setting Up HTTP or HTTPS​

Setting up HTTP or HTTPS is straightforward when everything goes smoothly. But what if things go wrong? How can you troubleshoot and identify the issue? Here, we’ll list some commonly encountered problems when setting up HTTP or HTTPS.

Mixed-Content warnings​

This warning appears when you’re mixing HTTP and HTTPS content. It’s important to use only HTTPS for secure connections and HTTP for non-secure connections. You may need to set up HTTPS, or you might have forgotten to add HTTP to your public address when configuring a reverse proxy.

HTTPS is set up, but doesn't work​

There are several possible causes, with the most common ones being:

  • Web server application isn't auto-forwarding MistServer.
  • Certificate is invalid or incorrect.
  • Attempting to Open HTTPS Through HTTP.
  • HTTPS Port Already in Use

Webserver application isn't auto-forwarding MistServer​

MistServer can be directed to the correct address if your web server application is set up as a reverse proxy for MistServer, and the X-Mst-Path header is passed along. If this header is missing, MistServer may not recognize the setup correctly.

If MistServer isn’t auto-forwarding, you can set the Public Address value in the HTTP protocol settings. This informs MistServer of the expected HTTP communication endpoint and helps it connect to your web server.

Note: Setting up only an HTTPS address will result in HTTPS-only configuration. To use both protocols, add an HTTP reverse proxy and Public Address as well.

Certificate is invalid or incorrect​

You can set up HTTPS manually with a certificate, which is recommended for servers dedicated to MistServer. This process is similar to using Certbot, except you’ll manage certificate updates manually.

When configuring the HTTPS (HTTP+TLS) protocol, you’ll be asked for the file locations of the certificate and key. Make sure these files follow the PEM standard. For detailed instructions, refer to the guides on using an existing certificate or Certbot.

Attempting to Open HTTPS Through HTTP​

This is less common since most browsers try to enforce HTTPS when available. However, you may encounter this issue on the preview page. Keep in mind that the MistServer interface uses HTTP, so you can’t check your HTTPS connection from there. We recommend opening the embed page and using the HTTPS HTML endpoint in a separate tab to verify the connection.

HTTPS Port Already in Use​

This occurs if you try to bind a port already used by another application. The default HTTPS port (443) may be occupied by a web server. In this case, using a reverse proxy is recommended. Alternatively, you can select another port. To identify open ports, use tools like netstat.

HTTP is set up, but no HTTP playback works​

This issue usually results from:

  • Your chosen HTTP port being in use.
  • Setting up an HTTPS public address without an HTTP public address.

Your chosen HTTP port being in use​

This issue can be identified in the protocol panel. If the protocol shows as unavailable, it’s likely that the HTTP protocol couldn’t start. For servers already hosting websites, port 80 is often in use. MistServer defaults to port 8080, but other applications may use the same logic. Try assigning MistServer a different port, or use tools like netstat to check which ports are already in use.

Setting up an HTTPS public address without an HTTP public address​

The HTTP protocol’s public address option can guide MistServer to another address, which is useful when using a reverse proxy. However, a common mistake is setting only an HTTPS address. To re-enable HTTP, add a reverse proxy for HTTP and add a HTTP Public Address as well.

Port or Connection Is Being Blocked​

Most users facing this issue likely have a router or firewall between themselves and the server. This can also occur in non-standard network environments, in which case consulting your network specialist would be your solution.

Your router is not forwarding the connection​

This only applies if you’re hosting MistServer on a private network, such as a home network. If you’ve rented a server, this step can be skipped.

Warning: Opening your home network requires networking knowledge. If you’re unsure, consider renting a server instead.

To allow TCP connections to the server’s chosen HTTP port, configure port forwarding on your router. Default ports for MistServer are:

  • TCP: 8080 (HTTP), 5554 (RTSP), 443 (HTTPS)
  • UDP: 5554 (RTSP), 8889 (SRT)

The API and interface use TCP (4242), but we don’t recommend making this available outside your private network.

Firewall is blocking connection​

A lack of connection attempts is your hint when a firewall is in the way. Set the HTTP protocol to a debug level of 4 to check for INFO messages. If nothing appears when attempting to connect, a firewall is likely blocking all traffic. Consult your firewall’s instructions to resolve this.

Note: Always check your router settings first!

Multiple HTTP(S) Protocols Are Set Up, but Only One Is Used​

By default, the interface connects to the first HTTP(S) protocol in the list that matches the protocol you’re using to access the interface. This means any additional HTTP(S) protocols won’t automatically connect. To verify additional protocols, manually connect to the stream URL or HTML addresses.

Replaced Certificates, but HTTPS Certificate Remains Invalid​

MistServer reloads the protocol when settings change but doesn’t monitor the HTTPS certificate and key files for updates. To apply a new certificate, restart the MistOutHTTPS process. You can do so by sending a kill command to MistOutHTTPS.