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 revisionNext revisionBoth sides next revision | ||
vrm_portal:troubleshooting_ccgx_vrm_connectivity [2017-12-10 11:58] – [Trouble shooting Remote Console on VRM] mvader | vrm_portal:troubleshooting_ccgx_vrm_connectivity [2019-06-05 03:37] – guy_stewart | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | This document outlines the procedure | + | Looking for how to trouble shoot transmission of data logs to VRM? [[https://www.victronenergy.com/ |
- | + | ||
- | Please also read the [[https:// | + | |
Not using a CCGX but a Victron Global Remote or Victron Ethernet Remote? See [[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: | 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 | + | After enabling the feature in the CCGX setting menu, setting or disabling the password, and then restarting the CCGX, a new Menu Option |
- | {{ : | + | {{ : |
Steps to take when it does not work: | Steps to take when it does not work: | ||
Line 83: | Line 19: | ||
- Verify that your local web browser can access the [[https:// | - 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/ | + | 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/ |
- | In case all above does not help, it might be that your internet connection very frequently changes its IP-address. | + | ==== IP Address verification ==== |
+ | Remote Console on VRM checks the IP Address for security reasons. | ||
- | ====== Further debugging VRM communication (advanced) ====== | + | 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. |
- | === Debugging | + | Both of which will make the IP verification fail and therefor makes Remote Console fail. To solve this problem, contact your internet |
- | 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) === | + | Note that it is not necessary for the CCGX to be addressable itself, and/or have a public IP address. Worded differently: traversing NAT translation is no problem. |
- | If your provider | + | |
- | < | ||
- | |||
- | 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</ | ||
- | |||
- | ====== DISQUS Comments ====== | ||
+ | ===== DISQUS ===== | ||
~~DISQUS~~ | ~~DISQUS~~ | ||
- | |||
- | \\ | ||
- |
vrm_portal/troubleshooting_ccgx_vrm_connectivity.txt · Last modified: 2020-07-21 09:52 by mvader