Hi,

sorry for the inconvenience, our Log Insight team is currently working on this issue.

The current workaround would be to connect to the Log Insight using the IP first.

This will assure that the Content will load, and after that you should be able to use the FQDN again.

Hope that helps. Best Regards from Cork

Benedikt