You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2019. It is now read-only.
I assume that this is because the new versions of Cockpit redirect HTTP requests to HTTPS. Cockpit on my target host is working fine and the Foreman host has access to 9090, but when I curl the address that the docs say needs to be available I get:
<html><head><title>Moved</title></head><body>Please use TLS</body></html>
The text was updated successfully, but these errors were encountered:
Maybe this is just an issue with documentation. It looks like it can use HTTPS as the protocol, but I can't seem to find the documentation to support that.
Foreman host OS: Debian 9.5
Cockpit host OS: Debian 9.5
Foreman: 1.18
Cockpit: 172-1
foreman_cockpit: 2.03
I assume that this is because the new versions of Cockpit redirect HTTP requests to HTTPS. Cockpit on my target host is working fine and the Foreman host has access to 9090, but when I
curl
the address that the docs say needs to be available I get:<html><head><title>Moved</title></head><body>Please use TLS</body></html>
The text was updated successfully, but these errors were encountered: