Project

General

Profile

Actions

Bug #18007

closed

Can't assign new proxy to my foreman system

Added by Shahaf Benita over 7 years ago. Updated over 7 years ago.

Status:
Duplicate
Priority:
High
Assignee:
Category:
Smart Proxy
Target version:
-
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hey,
Ruby implementation and version: Not Sure
Rails version: Not sure
OS: rhel 7
DB: postgres
Ruby-aware server used: Webrick

When i'm using the web gui and trying to create new proxy for the first time after installing foreman on Server1 and foreman-proxy on Server2, I get the following error:
Unable to communicate with the proxy:ERF12-2530[ProxyAPI::ProxyException]: Unable to detect features ([OpenSSL::SSL:SSLError]: HOSTNAME "Server2" doesnot match the server certificate) for proxy https://Server2:8443/features
Please check the proxy is configured and running on the host.

This is how i created the crtificates:
I ran this command on Server1(where foreman and puppet are installed): puppet cert generate Server2.new
and after that I copied those files which were generated from:
private_keys/Server2.new
certs/Server2.new
and certs/ca.pem
I copied it to Server2 and in settings.yml I pointed the ca's to those new files.
ofcourse I changed the ownerships on those files to foreman-proxy so i can restart the service foreman-proxy proparley, and i also did some more instructions which provided in foreman website.
still could not add the Server2 to the proxies list in Server1 web gui.


Related issues 1 (1 open0 closed)

Is duplicate of Foreman - Support #18008: Having problem with adding new smart-proxiesNewShahaf Benita01/10/2017Actions
Actions #1

Updated by Dominic Cleal over 7 years ago

  • Is duplicate of Support #18008: Having problem with adding new smart-proxies added
Actions #2

Updated by Dominic Cleal over 7 years ago

  • Status changed from New to Duplicate

Filed at #18008 as a support request instead. Unclear that this is a bug.

Actions

Also available in: Atom PDF