Differences

This shows you the differences between two versions of the page.

--- ccgx:ccgx_faq [2020-01-21 16:18] – [Q15: What type of networking is used by the Color Control GX (TCP and UDP ports)?] wiebe
+++ ccgx:ccgx_faq [2020-10-15 10:33] – [Q15: What type of networking is used by the Color Control GX (TCP and UDP ports)?] ictbeheer
@@ Line 74: / Line 74: @@
-==== Q9: When I type the ip-address of the Color Control into my browser, I see a web page mentioning Hiawatha? ====
-Our plan is to at least run a website where you can change settings and see the current status. If all works out as we would like to, there might come be a fully functional version of the online VRM Portal running locally on the Color Control GX. This allows people without an internet connection, or an intermittent internet connection to have the same features and functionality.
 ==== Q10: I have multiple Solar chargers MPPT 150/70 running in parallel. From which one will I see the relay status in the CCGX menu? ====
@@ Line 106: / Line 104: @@
 VRM Portal:
-  * Data to the VRM Portal is sent via HTTP POST and GET requests to http://ccgxlogging.victronenergy.com on port 80. Sensitive data is sent using HTTPS on port 443 to the same host.
+  * Data to the VRM Portal is sent via HTTP POST and GET requests to https://ccgxlogging.victronenergy.com on port 443, with a user configurable override to use plain HTTP on port 80. Note that, even when configured to use plain HTTP, some outgoing requests will always use HTTPS on port 443.
 Firmware updates:
-  * The CCGX connects to [[https://updates.victronenergy.com/|http://updates.victronenergy.com/]] on port 443.
+  * The CCGX connects to [[https://updates.victronenergy.com/|https://updates.victronenergy.com/]] on port 443.
 Remote support (default disabled):
-  * When enabled, an outbound SSH connection to supporthost.victronenergy.com is maintained. The CCGX will try to connect on port 22, 80 and 443, and the first that works is maintained.
+  * When enabled, an outbound SSH connection to supporthosts.victronenergy.com is maintained. The CCGX will try to connect on port 22, 80 and 443, and the first that works is maintained.
-  * Enabling Remote Support also enables the sshd daemon, listening for incoming SSH requests on port 22. See next FAQ entry for more information about the Remote Support functionality.
+  * Enabling Remote Support also enables the sshd daemon, listening for incoming SSH requests on port 22. See below FAQ entry for more information about the Remote Support functionality.
 Two way communication (Remote VEConfig and Remote Firmware updates):
@@ Line 120: / Line 118: @@
 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 a victron MQTT cloud server  ranging from mqtt0.victronenergy.com to mqtt127.victronenergy.com), on port 8883, using SSL.
+   * 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  ranging from mqtt0.victronenergy.com to mqtt127.victronenergy.com), on port 443, using SSL. It uses port 443 to reduce the chance of using blocked outgoing ports.
 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 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 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, 84.22.107.120, 3.25.10.245, 13.244.154.199 or 35.165.124.40, depending on where you are.
-  * See [[vrm_portal:troubleshooting_ccgx_vrm_connectivity#trouble_shooting_remote_console_on_vrm|here]] to trouble shoot Remote Console on VRM.
+  * Remote console also relies on the data connection to the VRM portal using HTTPS (port 443), as describe above.
+  * For troubleshooting, refer to the [[https://www.victronenergy.com/live/ccgx:start#remote_console_on_vrm_-_trouble_shooting|Remote Console on VRM trouble shooting guide]].
 Remote Console on LAN (default disabled):
@@ Line 158: / Line 157: @@
 ==== Q20: Issues with Multi not starting when CCGX is connected / Caution when powering the CCGX from the AC-out terminal of a VE.Bus Inverter, Multi or Quattro ====
-Make sure that the GX device and MultiPlus is running the latest firmware version.
+NOTES:
+  - We recommend to power a GX device from the battery. Not from the AC-out. In case you still power it from AC-out, carefully read this FAQ item.
+  - This FAQ item applies to Venus GX, CCGX, and all other GX Devices, but not the Cerbo GX. It has an improved design due to which its no longer recommended to cut pin 7 of the VE.Bus cable when powering the GX device on the AC-out port.
+  - Make sure that the GX device and MultiPlus is running the latest firmware version.
-If you power the CCGX from an AC adaptor connected to the AC-out port of any VE.Bus product (Inverter, Multi or Quattro), then a deadlock can occur after the VE.Bus products are powered-down for any reason (after any operational fault or during a black start). The VE.Bus devices will not boot-up until the CCGX has power ...but the CCGX will not boot-up until //it// has power. See FAQ for more information about this.
+If you power the CCGX from an AC adaptor connected to the AC-out port of any VE.Bus product (Inverter, Multi or Quattro), then a deadlock can occur after the VE.Bus products are powered-down for any reason (after any operational fault or during a black start). The VE.Bus devices will not boot-up until the CCGX has power ...but the CCGX will not boot-up until //it// has power.
 This deadlock can be rectified by briefly unplugging the CCGX VE.Bus cable at which point you will observe the VE.Bus products will immediately begin to boot-up.
@@ Line 203: / Line 205: @@
-===== DISQUS =====
-~~DISQUS~~