Catalog in 0.43.1 seems to spin mercilessly

Archive Rancher 1.x
1

Screen Shot 2015-11-03 at 4.59.36 PM.png1590×1098 120 KB

I was curious to try out launching a Logspout stack, since I had already deployed a LogSpout stack in the past, so when I gave it a try, I didn’t get past the spinning balls and so I took a screen shot and uploaded it here. Has anyone come across an easy fix on this?

I’m not seeing anything jumping out of the logs on the rancher server on this.
I’ve also tested on two installations of Rancher

2

This seems like a UI issue where it’s not coming up with the details in the drop down for some reason. I haven’t been able to reproduce.

Is this an upgraded set up? Can you click on the cow in Rancher to show me version of UI? I have seen caching issues where even though I upgraded, the UI version didn’t change.

With v0.43.1, the UI should be at v0.65.0.

3

Can you open up the browser dev tools console before clicking on the launch button? There’s probably a relevant error there.

4

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 ?)

5

This was fixed in 0.44, the catalog API was returning http:// URLs and the browser refuses to load mixed content.

6

I’m still fighting this constantly in version 0.44.0 on nearly every page. On a fresh load of the page I can do anything, but after selecting something (like view logs or stop a container), subsequent commands fail with the http/https error. I have to reload the page to get back to a working order.