vrm_portal:troubleshooting_ccgx_vrm_connectivity
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vrm_portal:troubleshooting_ccgx_vrm_connectivity [2019-01-21 11:15] – [DISQUS Comments] ictbeheer | vrm_portal:troubleshooting_ccgx_vrm_connectivity [2020-07-21 09:52] (current) – mvader | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Troubleshooting CCGX to VRM connectivity ====== | + | Moved here: https:// |
- | + | ||
- | This document outlines the procedure to troubleshoot connectivity between a CCGX and the [[https:// | + | |
- | + | ||
- | Please also read the [[https:// | + | |
- | + | ||
- | Not using a CCGX but a Victron Global Remote or Victron Ethernet Remote? See [[https:// | + | |
- | + | ||
- | Trouble shooting Remote Console on VRM? See last section in this document. | + | |
- | + | ||
- | On initial contact with the VRM site it may take a few minutes for data to appear, as a newly-connected or re-connected CCGX’s presence requires that data to be filtered through our back-end systems, before the information becomes visible on the VRM site. | + | |
- | + | ||
- | If the data backlog size continues to increase after the chosen logging interval time is met, then you have internet connectivity issues. You could try to increase the logging interval to a longer time, in order to reduce necessary bandwidth. Bandwidth requirement is quite low, so this normally only happens when using a cellular data connection. Try moving the antenna or obtain a higher gain antenna. | + | |
- | + | ||
- | ==== Step 1. Update the CCGX to the latest available firmware ==== | + | |
- | + | ||
- | [[ccgx: | + | |
- | + | ||
- | ===== Step 2 - Verify that the CCGX has a valid IP address ===== | + | |
- | + | ||
- | In the menu Settings → Ethernet or Settings → Wi-Fi, State should be ‘Connected’ and there should be an IP address that does not start with 169: | + | |
- | + | ||
- | {{: | + | |
- | {{ : | + | |
- | + | ||
- | When using Ethernet and State shows ' | + | |
- | + | ||
- | When using Wi-Fi and the menu shows 'No Wi-Fi adapter connected' | + | |
- | + | ||
- | When using Wi-Fi and the State shows ' | + | |
- | + | ||
- | In case there is an IP address that starts with 169, check whether your network has a DHCP server running. 99% of all networks have a DHCP server running and it is enabled by default on all well-known ADSL, cable and 3G routers. If there is no DHCP server running, then configure the ip address manually. | + | |
- | + | ||
- | ===== Step 3 - Check connectivity between CCGX and VRM Portal ===== | + | |
- | + | ||
- | Navigate to Settings → VRM online portal. | + | |
- | + | ||
- | {{ : | + | |
- | + | ||
- | Check 'Last contact' | + | |
- | + | ||
- | Resolution: make sure that your network has access to the internet. Plugin a laptop and navigate to [[https:// | + | |
- | + | ||
- | If ' | + | |
- | + | ||
- | In case all above checks have been done, internet connection is sure to work, and still 'Last contact' | + | |
- | + | ||
- | The communication required to communicate to the VRM Portal is: | + | |
- | - Working DNS | + | |
- | - Proper IP address | + | |
- | - Working internet connection | + | |
- | - Outbound http(s) connection to http:// | + | |
- | + | ||
- | Note that the CCGX does not support a proxy setup. | + | |
- | + | ||
- | For details on the required networking, see [[https:// | + | |
- | + | ||
- | And if that also doesn' | + | |
- | + | ||
- | ===== Step 4 - Add the site to your VRM account ===== | + | |
- | + | ||
- | Adding a CCGX to your account is only possible after the CCGX has made its first initial contact to the VRM Portal. | + | |
- | + | ||
- | As long as 'Last Contact' | + | |
- | + | ||
- | Once the internet communication is up, and 'Last contact' | + | |
- | + | ||
- | + | ||
- | + | ||
- | ====== Trouble shooting Remote Console on VRM ====== | + | |
- | The Remote Console on VRM feature allows full remote control of a CCGX, over the internet: | + | |
- | {{ : | + | |
- | + | ||
- | After enabling the feature in the CCGX setting menu, setting or disabling the password, and then restarting the CCGX, a green button will show on the VRM website. Click it to open the Remote Console. | + | |
- | {{ : | + | |
- | + | ||
- | Steps to take when it does not work: | + | |
- | - First make sure that basic communication with VRM works, see above steps. | + | |
- | - After enabling the feature, make sure to set (or disable) the password. | + | |
- | - Then restart the CCGX. | + | |
- | - Make sure to update the CCGX to the latest firmware version: v2.11 or newer. | + | |
- | - After the restart, check the Remote Console on VRM status shows online or a port number. In case it says offline, or port number 0, the CCGX was unable to connect to the Remote Console server. This is normally caused by a (company) firewall, blocking the connection. The solution is then to configure an exception rules in the firewall. | + | |
- | - Verify that your local web browser can access the [[https:// | + | |
- | + | ||
- | 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. It is not necessary to set up port forwarding in routers to use Remote Console on VRM. It is necessary for the firewall/ | + | |
- | + | ||
- | ==== IP Address verification ==== | + | |
- | Remote Console on VRM checks the IP Address for security reasons. | + | |
- | + | ||
- | In case all above does not help, it might be that your internet connection very frequently changes its IP-address. And/or that the internet provider routes the different data stream over different of its routers. | + | |
- | + | ||
- | Both of which will make the IP verification fail and therefor makes Remote Console fail. To solve this problem, contact your internet provider and/or change to a different internet provider. | + | |
- | + | ||
- | Note that it is not necessary for the CCGX to be addressable itself, and/or have a public IP address. Worded differently: | + | |
- | + | ||
- | ====== Further debugging VRM communication (advanced) ====== | + | |
- | + | ||
- | === Debugging the connection (advanced) === | + | |
- | Data is sent to the VRM Portal using HTTP POST requests to http:// | + | |
- | The output should be a line containing the text 'vrm: OK'. If it does not, or wget hangs, check your network. Apparently communication is blocked. | + | |
- | + | ||
- | === Using HTTPS instead of HTTP (advanced) === | + | |
- | If your provider is blocking HTTP requests (e.g. the wget request above times out or fails), you can change the CCGX to log to the VRM portal via HTTPS: | + | |
- | + | ||
- | < | + | |
- | + | ||
- | Verify that the setting has been changed: | + | |
- | < | + | |
- | ' | + | |
- | + | ||
- | It is then recommended to reboot the CCGX to apply the changes. (Alternatively, | + | |
- | + | ||
- | After you reboot, you should see the buffer size decrease: | + | |
- | < | + | |
- | root@ccgx: | + | |
- | 375 | + | |
- | # after rebooting | + | |
- | root@ccgx: | + | |
- | 362</ | + | |
- | + | ||
- | + | ||
- | + | ||
- | \\ | + |
vrm_portal/troubleshooting_ccgx_vrm_connectivity.1548065748.txt.gz · Last modified: 2019-01-21 11:15 by ictbeheer