FxV will not accept connections from the FxMs on 443. Changing the FxV port on the FxM fails the connectivity test. FxV has a valid certificate and they are on the same subnet.
The FxMs were using port 80 previously. We tried changing that to port 443 or 7643 and both failed despite the fact that the appliance has a valid CA signed certificate on it. The certificate works fine when logging into the web UI via SSL.
In the FxV Server Port box, type the port that the Foglight Experience Viewer Server uses. This
value should always be set to default HTTP port value (80 or 7630).
Important To ensure a secure communication with the FxV Server, you must also log in to the FxV browser
interface, navigate to Configure > Superuser Tasks > Server Configuration, and set SSL
Redirection Enabled to Yes. This setting affects all the Web console traffic, and the FxM
drilldown links are automatically redirected to the HTTPS port (by default, 443 or 7643).
The “FxV Server Port” on FxM is used for two purposes, 1) drilldown links from FxM; and 2) FxM collection to FxV Server communication (configuration download and metric upload).
The drilldown links from FxM are acted on by the user’s browser, so either 443 or 80 will work for this purpose (it’s the user’s browser contacting the FxV web console).
However, FxM collection doesn’t support ssl. When it contacts the FxV Server for configuration settings it needs to be over a non-ssl socket. So this needs to use port 80.
Since the “SSL Redirection” setting on FxV only affects web console traffic, the drilldown links will get redirected to 443 but the collector communications will not get redirected. That allows you to secure all web console traffic and, at the same time, allow collector to communicate with the FxV Server over a non-ssl socket.
So, the “FxV Server Port” on FxM must always be either 80 or 7630 (the legacy port).