We’re proxying the rancher-server instance according to the documentation and using HTTPS.
It looks like the issue is mixed HTTPS/HTTP calls (the HTTPS page is calling content from unprotected HTTP for the REST API).
GET https://rancher-server.fqdn/v1-catalog/images/external-dns/catalogIcon-externaldns.svg 404 (Not Found)
3route.js:193 Subscribe ping
jquery.js:8630 Mixed Content: The page at 'https://rancher-server.fqdn/apps/catalog/all' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://rancher-server.fqdn/v1-catalog/templates/logspout/0'. This request has been blocked; the content must be served over HTTPS.
Is this the expected behavior, or is there another configuration change that needs to be made when you proxy over HTTPS (e.g. telling Rancher that the base URL should be https ?)