Cockpit installed on local dev machine
by Jonathan Aquilina
Hi All,
I have a dev laptop which I have installed cockpit on. My question even though I have it installed on a local laptop would you guys still recommend I setup https on it if I plan on connecting to remote machines?
Regards,
Jonathan Aquilina
EagleEyeT
Phone +356 20330099
Sales - sales(a)eagleeyet.net<mailto:sales@eagleeyet.net>
Support - support(a)eagleeyet.net
4 years, 1 month
Cockpit 213
by Marius Vollmer
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes from version 213:
http://cockpit-project.org/blog/cockpit-213.html
Summary:
- Inline documentation
- Support for transient virtual machines
- Virtual machines can now use UEFI
- Unattended virtual machine installation
Enjoy!
4 years, 2 months
PSA: New server for test log files
by Martin Pitt
Hello all,
until today, most of our test logs went to <https://209.132.184.41:8493>, an
OpenStack instance in fedorainfracloud.org.
However this cloud will shut down at the end of the month, so I set up an
alternative. Initially, I thought that we could just log everything to
<logs-https-cockpit.apps.ci.centos.org>, but unfortunately Routes in OpenShift
only work for HTTP, not the SSH protocol.
So I set up an instance in AWS instead, which is now our new log sink:
<https://54.89.13.31/>. The first time you open a log, you will get a cert
validation error. Unfortunately AWS doesn't support setting up DNS names (or
it's really well hidden -- if you know how, please prod me!), so it's a bit
hard to get a proper certificate. But it's the exact same cert as we use on
image servers and our other log sinks.
Please let me know if you see any trouble with test logs.
Thanks,
Martin
4 years, 2 months
How to enable CORS?
by Daniel.
Hi everybody,
I have some code that runs as a cockpit plugin. I have a lot of calls to
cockpit.spawn, which I want to replace by fetch calls. The problem is that
the software running API is running on port 443, not 9090, so I get a big
and red error message about CORS not enabled,
I can check that response has Acces-Control-Allow-Origin set to
mymachine:9090, in dev tools
I did some googling and found that I would enable CORS by editing
cockpit.conf and placing a `Origin = https://mymachine:9090
wss://mymachine:9090 https://mymachine` I tried that without success. I may
be wrong here
I'm running a Centos7 machine with cockpit 195, here is the content of my
/etc/cockpit/cockpit.conf
[WebService]
Origin = https://192.168.123.2:9090 wss://192.168.123.2:9090
http://192.168.123.2 https://192.168.123.2
Any ideas?
Best regards
--
“If you're going to try, go all the way. Otherwise, don't even start. ..."
Charles Bukowski
4 years, 2 months
