Troubleshooting Proxy Connections and FQDN

Sometimes clients connected through a proxy appear in the Web UI, but do not show that they are connected through a proxy. This can occur if you are not using the fully qualified domain name (FQDN) to connect, and the proxy is not known to SUSE Multi-Linux Manager.

To correct this behavior, specify additional FQDNs based on the configuration file location used:

When placing a configuration file in the /etc/venv-salt-minion/minion.d/ directory, specify the top-level grains block:

grains:
  susemanager:
    custom_fqdns:
      - name.one
      - name.two

Alternatively, when using /etc/venv-salt-minion/grains directly, omit the grains: line because the filename itself acts as the parent grain name:

susemanager:
  custom_fqdns:
    - proxy.example.com
    - proxy-alias.example.com