ccgx:ccgx_faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ccgx:ccgx_faq [2019-08-15 12:34] – replace venus-device with GX device guy_stewart | ccgx:ccgx_faq [2020-05-12 15:41] – [Q15: What type of networking is used by the Color Control GX (TCP and UDP ports)?] wiebe | ||
---|---|---|---|
Line 106: | Line 106: | ||
VRM Portal: | VRM Portal: | ||
- | * Data to the VRM Portal is sent via HTTP POST and GET requests to http:// | + | * Data to the VRM Portal is sent via HTTP POST and GET requests to https:// |
Firmware updates: | Firmware updates: | ||
Line 120: | Line 120: | ||
MQTT (default disabled): | MQTT (default disabled): | ||
- | * When enabled, a local MQTT broker is started, which accepts TCP connections on port 1883. The CCGX will also try to connect to the victron MQTT cloud server | + | * When enabled, a local MQTT broker is started, which accepts TCP connections on port 1883. The CCGX will also try to connect to a victron MQTT cloud server |
Remote Console on VRM (default disabled): | Remote Console on VRM (default disabled): | ||
- | * Remote Console on VRM uses the same reverse ssh tunnel as is used for Remote Support: outbound connection to supporthost.victronenergy.com on port 22, 80 or 443. No port forwarding in routers is necessary to use Remote Console on VRM. | + | * Remote Console on VRM uses the same reverse ssh tunnel as is used for Remote Support: outbound connection to supporthosts.victronenergy.com on port 22, 80 or 443. No port forwarding in routers is necessary to use Remote Console on VRM. Note that supporthosts.victronenergy.com resolves to multiple IP addresses: 84.22.108.49 and 84.22.107.120. |
+ | * Remote console also relies on the data connection to the VRM portal using HTTPS (port 443), as describe above. | ||
* See [[vrm_portal: | * See [[vrm_portal: | ||
ccgx/ccgx_faq.txt · Last modified: 2021-02-05 11:34 by marmour