vrm_portal:troubleshooting_ccgx_vrm_connectivity
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| vrm_portal:troubleshooting_ccgx_vrm_connectivity [2019-05-26 21:10] – mvader | vrm_portal:troubleshooting_ccgx_vrm_connectivity [2019-05-26 23:00] – [Further debugging VRM communication (advanced)] mvader | ||
|---|---|---|---|
| Line 30: | Line 30: | ||
| Note that it is not necessary for the CCGX to be addressable itself, and/or have a public IP address. Worded differently: | 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</ | ||
| - | |||
| - | |||
| - | |||
| - | \\ | ||
| ===== DISQUS ===== | ===== DISQUS ===== | ||
| ~~DISQUS~~ | ~~DISQUS~~ | ||
vrm_portal/troubleshooting_ccgx_vrm_connectivity.txt · Last modified: 2020-07-21 09:52 by mvader