Firewall Requirements for NexBlue Charge Points

To get the most out of your NexBlue charge point, it needs to securely connect to the NexBlue Cloud.

In most home and standard business networks, this happens automatically. However, if your charger is installed on a restricted or corporate network, you may need to allow the following outbound connections.

Required Outbound Access

Your network must allow the following outbound traffic:

• ICMP Type 8 – Ping
• UDP 53 – DNS
• TCP 443 – HTTPS
• TCP 8883 – MQTT
• TCP 8888 – Debug / diagnostics

Why this matters

These connections allow your charge point to:

• Stay connected to the NexBlue Cloud
• Send charging data and receive commands
• Support features in the myNexBlue App and Partner Portal
• Receive firmware updates
• Enable remote diagnostics and support

Without these, the charger may appear offline or have limited functionality.

Quick explanation (for IT teams)

HTTPS (443): Core API communication with NexBlue Cloud

MQTT (8883): Lightweight, real-time messaging for status and control

DNS (53): Required to resolve NexBlue service domains

ICMP: Used for basic connectivity checks

Port 8888: Used only when needed for diagnostics and troubleshooting

Key points to note

Outbound only: No inbound ports are required

Secure by default: All critical communication is encrypted

Corporate networks: May require firewall or proxy configuration

Whitelisting: If your network restricts by domain or port, ensure the above are permitted

Summary

If these outbound rules are in place, your NexBlue charge point will connect reliably and support all core features, including remote access, monitoring, and updates.

If you’re unsure, share this article with your IT team or contact NexBlue support — we’re happy to help get everything set up correctly.