Project

General

Profile

Actions
Copy link

Bug #9459

closed

Unable to register discovered host via https proxy

Added by Lukas Zapletal about 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Smart Proxy Plugin
Difficulty:
Triaged:
Bugzilla link:
1194204
Pull request:
https://github.com/theforeman/smart_proxy_discovery/pull/7
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

I ran the discovery via https proxy and while registering the host with server, I got following error:

---
[2015-02-19T15:37:45.309389 #914] ERROR -- : Unable to resolve hostname for connecting client - 192.168.100.34. If it's to be a trusted host, ensure it has a reverse DNS entry.

no name for 192.168.100.34
192.168.100.34 - - [19/Feb/2015 15:37:45] "POST /discovery/create HTTP/1.1" 403 159 0.0256
E, [2015-02-19T15:38:15.854556 #914] ERROR -- : Unable to resolve hostname for connecting client - 192.168.100.34. If it's to be a trusted host, ensure it has a reverse DNS entry.

Related issues 1 (0 open — 1 closed)

Related to Discovery - Feature #9460: Extend authorize_with_trusted_hosts in proxy with subnets supportRejected02/19/2015Actions
Actions
Copy link
 #1

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart_proxy_discovery/pull/5 added
  • Pull request deleted ()
Actions
Copy link
 #2

Updated by Lukas Zapletal about 9 years ago

  • Related to Feature #9460: Extend authorize_with_trusted_hosts in proxy with subnets support added
Actions
Copy link
 #3

Updated by Lukas Zapletal about 8 years ago

  • Status changed from Ready For Testing to Closed
  • Pull request https://github.com/theforeman/smart_proxy_discovery/pull/7 added
  • Pull request deleted (https://github.com/theforeman/smart_proxy_discovery/pull/5)
Actions
Copy link

Also available in: Atom PDF