Change Default WSS Port from 8884 to 443 on HiveMQ Cloud

Overview

This knowledge base article documents the process for changing the default WebSocket Secure (WSS) port from 8884 to 443 on a HiveMQ Cloud cluster.

Issue Description

A customer requested to change the default WSS port from 8884 to 443 on their HiveMQ Cloud cluster.

Background

HiveMQ Cloud uses port 8884 as the default port for secure WebSocket (WSS) connections. WebSocket is a network protocol that provides bidirectional communication, and when combined with TLS/SSL, it creates secure WebSocket connections.

Port 443 is the standard HTTPS port and is commonly used in enterprise environments where firewall rules may restrict outbound connections to standard ports only.

Resolution Steps

For HiveMQ Cloud Customers

Contact HiveMQ Support through the [HiveMQ Service Desk|https://hivemq.atlassian.net/servicedesk/customer/portal/1]
Provide the following information:

Cluster URL or identifier
Requested port change (from 8884 to 443)
Environment (production or non-production)

HiveMQ Support will create an internal ticket to process the request
Wait for confirmation from the HiveMQ Support team that the change has been completed
Update your client applications to connect to the new port

Client Configuration Update

After the port change is complete, update your client connection settings:

{code:javascript}
var options = {
    host: 'your-cluster.hivemq.cloud',
    port: 443,
    protocol: 'wss',
    username: 'your-username',
    password: 'your-password'
}

Verification

After the port change, verify the connection:

Test connectivity using an MQTT client (such as MQTT.js or Paho)
Confirm successful connection to port 443
Verify that existing functionality works as expected

Important Considerations

This change requires intervention from HiveMQ Support and cannot be performed by customers directly
The change may cause temporary disruption to connected clients
All client applications must be updated to use the new port
Port 443 provides better compatibility with corporate firewalls and network policies

Prevention and Best Practices

To avoid issues related to port configuration:

Plan port requirements during initial cluster setup
Document port configurations in your architecture documentation
Consider firewall and network requirements early in the design phase
Test connectivity from your deployment environment before production rollout
When using WebSocket connections, ensure your clients support the required protocols(2)(https://www.hivemq.com/blog/mqtt-essentials-special-mqtt-over-websockets)

Related Information

Support

For additional assistance with port configuration or other HiveMQ Cloud issues, contact HiveMQ Support: