Telling Cockpit to listen on a specific IP address #21193
yrro
started this conversation in
Show and tell
Replies: 2 comments
-
Hah, I see the info about |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks @yrro ! Just for other readers, another way is to change cockpit's port to something else. https://cockpit-project.org/guide/latest/listen describes that as well. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
To solve a conflict between cockpit and prometheus, which both want to use port 9090/tcp, I added an additional IP address to my machine, and told prometheus to listen on
192.0.2.10:9090
. However, this still conflicts withcockpit.socket
which is unable to bind to0.0.0.0:9090
if prometheus starts first.I modified
cockpit.socket
to make it bind to the machine's original IP address:I added
FreeBind=
so thatcockpit.socket
can start before the IP address is available. Originally I tried addingWants=network-online.target
but this caused an ordering cycle (network-online.target
->NetworkManager-wait-online.service
->basic.target
->sockets.target
->cockpit.socket
->network-online.target
).I hope someone else finds this useful.
Beta Was this translation helpful? Give feedback.
All reactions