Not being able to use ‘foreman-proxy’ *is* in the manual.
https://theforeman.org/manuals/1.16/index.html#4.3.8Realm
But it seems odd that your other choices didn’t work.
Sent from my iPhone
> On 18 Dec 2017, at 13:17, Matt wrote:
>
> Hi Guys,
>
> I have found out, also earlier, that any user
wget don't have an option --no-check-certificate. I just
> have to use only wget -q -O . and it did the trick.
>
> Thank again.
>
>
>
>> On Friday, October 20, 2017 at 4:31:22 AM UTC-5, Alexander Fisher wrote:
>> Odd. That should be better now. If you manually
da612c
>>
>> <http://foreman.mydomain.com/unattended/built?token=1980ecab-86bf-4f10-a6eb-3c1624da612c>*
>> echo "Done with Foreman call"
>>
>> exit 0
>>
>>
>
>
>
>
>
> On Thursday, October 19, 2017 at 12:54:05 AM UTC-5, Alex
Hi
I can’t recall when it changed, but these days you have to use “<%=
foreman_url('built') %>” instead of just “<%= foreman_url %>”
Kind regards,
Alex
> On 19 Oct 2017, at 06:46, No1 wrote:
>
> Hi,
>
> I am trying to install the Esxi 6.0 using foreman and the process is
> completely success
Lukas - I think Justin is expecting the CNAME api to be exposed in the UI.
There's an open PR for this?
https://github.com/theforeman/foreman/pull/4171
On Wed, Jun 7, 2017 at 8:21 AM, Lukas Zapletal wrote:
> Our API endpoint did not change, just provide CNAME type. It's in /dns
> path, search in
On Sun, Jun 4, 2017 at 1:56 PM, Ido Kaplan wrote:
> Hi,
>
> Is it possible to register the servers via short name and not FQDN?
> Please advise.
>
>
You can use the short name for VMs you create with Foreman using the 'Use
short name for VMs' setting.
http://projects.theforeman.org/issues/2975
N
The API call is to https://domain.com:8433/puppet because it's from foreman to
the proxy endpoint, not to the puppet API. Looks like foreman can't connect to
the proxy, but perhaps you're trying to connect to the wrong host. Is your
proxy on your foreman host, or on your puppet host?
Sent from
