Bug #1461

preseed URL hardcoded to http (patch)

Added by Adrian Bridgett about 8 years ago. Updated over 6 years ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


The preseed url in the tftp file was incorect for me:

I found another ticket which said that it was worked out from the URL you visit foreman on when clicking "Build".

Ideally I guess this isn't right - I might be accessing foreman from a different network than the host being built.

In any case, visiting foreman as changed the URL to - still not https.

The attached patch fixes this - not sure it's the right way (I very rarely write ruby or rails!)

The preseed itself isn't working so I need to look at that, but at least this fixes one issue :-)

preseed_https_support.diff preseed_https_support.diff 1.7 KB Adrian Bridgett, 01/20/2012 10:03 AM

Related issues

Is duplicate of Foreman - Bug #3569: Port in use by the browser is used in rendering the templatesClosed2013-11-04


#1 Updated by Adrian Bridgett about 8 years ago

looks like debian preseeding doesn't support https anyway :-(

Hopefully that'll change so probably still worth having the patch - it doesn't appear to make life any worse

#2 Updated by Dominic Cleal over 6 years ago

  • Is duplicate of Bug #3569: Port in use by the browser is used in rendering the templates added

#3 Updated by Dominic Cleal over 6 years ago

  • Description updated (diff)
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

As you say, many installers don't support HTTPS so we switch the protocol to HTTP. Newer generation ones (like the recent anaconda rewrite) now do HTTPS though, so perhaps we can switch in the future.

For the original issue, the fix added in #3569 should resolve this for you. It adds a new unattended_url setting which is always used for URLs in templates, so no host, port or protocol should leak from the web browser request (it defaults to HTTP too).

Also available in: Atom PDF