Project

General

Profile

Actions

Bug #15138

closed

Start foreman-proxy on non-DHCP network

Added by Lukas Zapletal over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Image
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We need to have a valid (self-signed) https certificate for particular
primary interface. If there is none, we can't do much about it. We might
change to code and start the proxy anyway so it is accessible over HTTP
at least. Instead an IP address in the common name, we will provide
a constant string.

https://github.com/theforeman/foreman-discovery-image/blob/master/root/usr/bin/generate-proxy-cert#L13

Actions

Also available in: Atom PDF