Closed bernd-wechner closed 3 years ago
Are you running Cockpit through a SSL proxy, such as with Nginx?
Cockpit version: 164-1
By-the-way: Your version of Cockpit is over a year and a half old. You may want to update it.
I'm not quite sure, as I use Fedora, but I think using the Debian backport would work on Mint? https://cockpit-project.org/running.html#debian
Thanks for the note. I just checked status again and observe three things:
$ journalctl -u cockpit --since -120m
-- Logs begin at Mon 2019-02-25 01:02:04 AEDT, end at Fri 2020-01-10 15:07:43 AEDT. --
Jan 10 13:12:12 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:12:12 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:12:12 myserver cockpit-ws[27764]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:16:45 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:16:45 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:16:45 myserver cockpit-ws[27899]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:21:20 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:21:20 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:21:20 myserver cockpit-ws[28033]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:26:00 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:26:00 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:26:00 myserver cockpit-ws[28176]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:30:22 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:30:22 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:30:22 myserver cockpit-ws[28306]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:34:50 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:34:50 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:34:50 myserver cockpit-ws[28438]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:39:12 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:39:12 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:39:12 myserver cockpit-ws[28570]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:42:50 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:42:50 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:42:50 myserver cockpit-ws[28677]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:46:27 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:46:27 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:46:27 myserver cockpit-ws[28785]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:50:43 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:50:43 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:50:43 myserver cockpit-ws[28912]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:55:10 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:55:10 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:55:10 myserver cockpit-ws[29045]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 13:59:42 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 13:59:42 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 13:59:42 myserver cockpit-ws[29170]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:04:00 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:04:00 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:04:00 myserver cockpit-ws[29338]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:08:46 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:08:46 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:08:46 myserver cockpit-ws[29480]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:13:21 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:13:22 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:13:22 myserver cockpit-ws[29615]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:17:58 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:17:58 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:17:58 myserver cockpit-ws[29749]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:22:22 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:22:22 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:22:22 myserver cockpit-ws[29883]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:26:55 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:26:55 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:26:55 myserver cockpit-ws[30021]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:31:17 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:31:18 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:31:18 myserver cockpit-ws[30154]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:35:30 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:35:30 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:35:30 myserver cockpit-ws[30279]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:40:30 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:40:30 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:40:30 myserver cockpit-ws[30428]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:43:58 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:43:58 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:43:58 myserver cockpit-ws[30532]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:47:40 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:47:40 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:47:40 myserver cockpit-ws[30643]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:51:43 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:51:43 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:51:43 myserver cockpit-ws[30761]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 14:55:59 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 14:55:59 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 14:55:59 myserver cockpit-ws[30889]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 15:00:05 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 15:00:05 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 15:00:05 myserver cockpit-ws[31044]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 15:04:28 myserver systemd[1]: Starting Cockpit Web Service...
Jan 10 15:04:28 myserver systemd[1]: Started Cockpit Web Service.
Jan 10 15:04:28 myserver cockpit-ws[31187]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert
Jan 10 15:04:38 myserver cockpit-session[31200]: pam_ssh_add: Failed adding some keys
Jan 10 15:04:38 myserver cockpit-session[31200]: pam_unix(cockpit:session): session opened for user myuser by (uid=0)
Jan 10 15:04:38 myserver cockpit-ws[31187]: logged in user session
Jan 10 15:04:40 myserver cockpit-ws[31187]: New connection to session from 192.168.0.11
So, although it works fine, this restart every 5 mins is concerning.
Oh and no not connecting through any proxy. Direct connection on the LAN. Only make cockpit available to on the LAN not outside of it. All behind a gateway, firewall, NAT etc, and on a 109.162.0 subnet.
As to versions well I'm using the Ubuntu standard I guess. I would perhaps update to a later version on a PPA, but and also content to run with Ubuntu's vetting.
cockpit.socket
is a port listener that starts cockpit.service
on demand, so logs will show Cockpit starting and stopping a good bit (such as whenever you hit port 9090 with a web browser).
I'm not sure about the lower level details like this, only guessing: It might also dynamically start and stop when you access the machine from another Cockpit instance in the dashboard or via the host switcher. @martinpitt would know more.
It might also dynamically start and stop when you access the machine from another Cockpit instance in the dashboard or via the host switcher.
No, that doesn't involve the web server (cockpit-ws, cockpit.socket, cockpit.service) at all. Just ssh and cockpit-bridge (but that's not a service, just a simple executable that runs in the user session, not on the system level).
For what it's worth I just checked that server and it's blank screening after login again. Seems intermittent. Examining the page source reveals a pretty rich page structure for a blank page ;-). The browser console however lends a clue:
Source map error: Error: request failed with status 401
Resource URL: https://myserver.lan:9090/cockpit/$c415b1318ee3f4f8895647e8466a7707098c89d4/shell/index.js
Source Map URL: index.min.js.map
is repeated a few times. Yet if I click that link (surf to that URL it reported 401 for I get a page of JS. I guess I should try and uninstall and install the latest version, but it smells of a bug. The server isn't slow per se, but maybe there's a timing issue with the availability of support files like that index.js and ungraceful handling of it. Would take some debugging I've not made time for ...
Source map errors wouldn't cause a blank page.
Source maps only map the compiled JS/CSS to the original JS/CSS files. If they're missing, then you just won't be able to map the sources back in browser developer tools. It would not impact anything else.
(We shouldn't have source maps referenced in packages; that's a bug.... but it really shouldn't impact anything other than developer tools.)
Ah, there's already a bug for source map issues @ https://github.com/cockpit-project/cockpit/issues/10420
Interestingly, the reporter also had some blank screen issue — caused by a browser extension called "Disable Autoplay". (FWIW: Firefox can natively disable autoplay without extensions now.)
Interesting. I checked the server in Chrome and it logged in and displayed fine. So I tried again in FF and it was fine again as well. It seems so intermittent somehow.
I don't have the Disable Autoplay extension installed. And I don't know off hand how to check FF configs to see if FF natively is disabling it.
hi,
I'm running OpenMediaVault (Debian 10) and I have the same white page problem after successful authentication.
when using Firefox's dev mode, I observe that all the GETs are OK 200 except one which is Forbidden 403 : the one on the websocket...
direct access without proxy (eg. on port 9090) return Switching Protocols 101 on the websocket.
(note that favicon.ico is 404 behind proxy and 200 with direct access)
regards, lacsaP.
hi,
for my part, it was just a problem of origins (cross domain).
no more blank page once the variable Origins
correctly defined in /etc/cockpit/cockpit.conf
.
(ignore the previous note concerning favicon.ico
which is requested by the navigator and not by the cockpit)
regards, lacsaP.
hi,
for my part, it was just a problem of origins (cross domain). no more blank page once the variable
Origins
correctly defined in/etc/cockpit/cockpit.conf
.(ignore the previous note concerning
favicon.ico
which is requested by the navigator and not by the cockpit)regards, lacsaP.
Hello, I managed to solve this myself. How did you do for the 404 on favicon.ico?
I am experiencing a similar issue when accessing my cockpit Raspbian 10 instance through nginx. Going to the same cockpit instance through the internal ip of the system works fine, so I suspect the issue lies within the nginx setup. Any help appreciated
I've seen the white page problem coming up on Debian 10 because my browser used a wpad proxy script and ws/wss need special treatment in there.
I've edited my wpad.dat script to exempt the following addresses and it worked properly after restarting the browser.
(...)
(shExpMatch(url, "ws://IP_OF_COCKPIT_SERVER:*")) ||
(shExpMatch(url, "wss://IP_OF_COCKPIT_SERVER:*")) ||
(...)
undefined cockpit.js:392:25
I just debugged this, this is a duplicate of issue #12745. PR coming.
Cockpit version: 164-1 OS: Linux Mint 19.2 Page: https://myserver.lan:9090/system
I installed cockpit recently on three servers I have:
It worked brilliantly on all three and I fell in love. Nice. beautiful app. Thanks.
Then a day after the install 3. the Mint 19.2 system presents a login page, but once I log in I get a blank page.
If I look in the Firefox console I see:
then after a short while it spews some more errors including:
and
and more . Methink JS is running and barfing.
Steps to reproduce
and
and
and
and
and
Though I notice it's a new pid every 2 minutes or so just like visible in the journalctl logs .... aaarg.
So I rebooted. Same issue. I removed cockpit and reinstalled it with
apt remove cockpit
andapt install cockpit
Same issue.Bizarre. As it was working fine then stopped and now is broken and not real clues bar: