Changed unattended url to match deployment vlan and got 404 for kickstart


I have a new foreman installation on a virtual machine
we have an administration lan on eth0 and a deployement lan on eth1

i’ve changed the unattended url in foreman to who is the ip of the virtual machine on eth1

but I got curl (22) the requested url returned 404 when anadonca is trying to get the kickstart
eg failed to fetch kickstart from …

Expected outcome:

Foreman and Proxy versions:

Foreman and Proxy plugin versions:

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)


extract from httpd logs: - - [28/Feb/2019:14:45:49 +0100] “GET /unattended/provision?token=bfe99873-286f-479a-8a7d-87e94fdaba22 HTTP/1.1” 404 80 “-” “curl/7.29.0” - - [28/Feb/2019:14:54:41 +0100] “GET /unattended/provision?token=bfe99873-286f-479a-8a7d-87e94fdaba22 HTTP/1.1” 404 80 “-” “curl/7.29.0” - - [28/Feb/2019:14:56:39 +0100] “GET /unattended/provision?token=fe99873-286f-479a-8a7d-87e94fdaba22 HTTP/1.1” 404 80 “-” “Wget/1.14 (linux-gnu)” - - [28/Feb/2019:14:57:19 +0100] “GET /unattended/provision?token=bfe99873-286f-479a-8a7d-87e94fdaba22 HTTP/1.1” 404 80 “-” “Wget/1.14 (linux-gnu)”

.202 is the foreman server
.217 is the dhcp ip for the provisionned vm

2019-02-28T16:18:56 [I|app|b51d3] Processing by UnattendedController#host_template as TEXT
2019-02-28T16:18:56 [I|app|b51d3] Parameters: {“token”=>“bfe99873-286f-479a-8a7d-87e94fdaba22”, “kind”=>“provision”}
2019-02-28T16:18:56 [E|app|b51d3] unattended: unable to find a host that matches the request from
2019-02-28T16:18:56 [I|app|b51d3] Rendering text template
2019-02-28T16:18:56 [I|app|b51d3] Rendered text template (0.0ms)
2019-02-28T16:18:56 [I|app|b51d3] Completed 404 Not Found in 51ms (Views: 1.1ms | ActiveRecord: 7.4ms)

This should explain it. There is no such host in Foreman database that either has:

  • Enabled build mode and provisioning token set to bfe99873-286f-479a-8a7d-87e94fdaba22
  • Or IP address of the provision interface equal to

Therefore 404 is returned.

I highly recommend to avoid multihome Foreman setups, it’s a challenging and you will run into issues. Install Foreman on a host with single network interface.

I don’t have the choice to have one interface.
I’ve found the problem, the token was expired in fact.

Now the last problem est that i’m stuck at the boot installer when choosing the kickstart