-
Explain what happens
NGINX Configuration: server {
listen 443 ssl;
server_name admin.example.com;
ssl_certificate /etc/letsencrypt/live/admin.example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/admin.example.com/privkey.pem;
location / {
# Required to proxy the connection to Cockpit
proxy_pass https://127.0.0.1:9090;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
# Required for web sockets to function
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
# Pass ETag header from Cockpit to clients.
# See: https://github.com/cockpit-project/cockpit/issues/5239
gzip off;
}
} Cockpit config ( [WebService]
Origins = https://admin.example.com wss://admin.example.com
ProtocolHeader = X-Forwarded-Proto Version of CockpitLatest, just installed today but I can't see because Cockpit is not working Where is the problem in Cockpit?Unknown or not applicable Server operating systemUbuntu Server operating system version22.04 What browsers are you using?Chrome System logNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Where exactly do you get the ERR_INVALID_REDIRECT? Is that an error message from nginx already? What do its logs (access.log and error.log) say?
Are you sure that you want to proxy to https? Normally you'd use a reverse proxy to terminate TLS, and talk unencrypted http to the backend service (cockpit in this case). |
Beta Was this translation helpful? Give feedback.
-
I don't know how to close a discussion, but I fixed it. I needed to set cloudflare SSL to full instead of flexible. |
Beta Was this translation helpful? Give feedback.
I don't know how to close a discussion, but I fixed it. I needed to set cloudflare SSL to full instead of flexible.