Ports and IPs required for V2C Cloud
For a V2C e-Charger to function correctly with V2C Cloud, it needs to communicate with a series of external services (cloud control, time synchronization, diagnostics, etc.). On this page, you will find all the domains, IPs, and ports that must be allowed on the router, firewall, or NAT configuration of the network where the charger is installed.
The most important thing: all connections are outbound — it is the charger itself that initiates communication to the internet. In most installations, it is not necessary to open incoming ports or configure port forwarding; it is enough for the network to allow outbound traffic to the specified destinations.
Connections Always Needed
These connections must be allowed in all installations to ensure cloud control, remote diagnostics, and the proper functioning of the charger.
| Domain | IP | Port | Protocol | Type | Purpose |
|---|---|---|---|---|---|
| autossh.v2c.cloud | Various | 2222 | SSH | TCP | V2C SSH tunnel for diagnostics and technical support (SAT) |
| V2CIoTHub.azure-devices.net | Various | 443 | HTTPS | TCP | Cloud charger control and configuration (IoT) |
| dns.google | 8.8.8.8 / 8.8.4.4 | 53 | DNS | UDP | Domain name resolution and latency testing |
| time.cloudflare.com | Various | 123 | NTP | UDP | Synchronization of the charger’s time with the network |
| pool.ntp.org | Various | 123 | NTP | UDP | Synchronization of the charger’s time with the network |
| time.windows.com | Various | 123 | NTP | UDP | Synchronization of the charger’s time with the network |
| time.apple.com | Various | 123 | NTP | UDP | Synchronization of the charger’s time with the network |
| ifconfig.co | Various | 80 | HTTP | TCP | Public IP and timezone query |
| ipinfo.io | Various | 80 | HTTP | TCP | Public IP and timezone query |
| ipapi.co | Various | 80 | HTTP | TCP | Public IP and timezone query |
Only if the charger uses OCPP
If the charger is configured to connect to an external management system via OCPP (Open Charge Point Protocol), in addition to the previous connections, you must allow communication with the OCPP server of your platform (CMS).
| Destination | Port | Protocol | Type | Purpose |
|---|---|---|---|---|
| OCPP Server (your CMS) | 8080 | WebSocket | TCP | Connection of the charger with the chosen management system (CMS) via OCPP |
Note: the domain or IP and, in some cases, the port of the OCPP server depend on the management platform you use. Check the connection details with your CMS provider.