Hello,

the subnets in dhcp.yml look suspicious, why you have them there? Also
these are not valid subnet addresses if I am not mistaken. Delete,
restart foreman-proxy.

Before you re-test verify that foreman-proxy see all subnet
definitions in dhcpd.conf, that would be:

curl -kvs --cert /etc/foreman/client_cert.pem --key
/etc/foreman/client_key.pem --cacert /etc/foreman/proxy_ca.pem
https://$(hostname):9090/dhcp

Not sure if you have cert paths right, if you change

:enabled: https

to

:enabled: true

and restart, then you can simply hit http endpoint:

curl http://$(hostname):9090/dhcp

LZ

On Fri, Aug 11, 2017 at 10:57 AM, Michal Hagara <[email protected]> wrote:
>
> duplicate of:
> https://groups.google.com/forum/#!topic/foreman-users/tHk4vS2aEws
>
>
> Im sorry for that!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.



-- 
Later,
  Lukas @lzap Zapletal

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to