Foreman-proxy 1.1rc5 = connection reset by peer

Support
1

Hi,
so I set up a new VM and installed foreman 1.1rc5 using the installer which
worked without any error and the web interface can be navigated but
foreman-proxy only returns "connection reset by peer". I tried setting the
log level to DEBUG but no proxy.log file is written at all.

Any ideas what this could be? When I installed foreman 1.0.2 the same way I
didn't see this issue.

Regards,
Dennis

2

Turns out that the SSL stuff doesn't seem to work. After commenting out
these three lines I no longer get the connection reset error:

#:ssl_ca_file: /var/lib/puppet/ssl/certs/ca.pem
#:ssl_certificate: /var/lib/puppet/ssl/certs/foreman11.local.pem
#:ssl_private_key: /var/lib/puppet/ssl/private_keys/foreman11.local.pem

Regards,
Dennis

··· On Sunday, February 3, 2013 5:29:07 PM UTC+1, Dennis Jacobfeuerborn wrote: > > Hi, > so I set up a new VM and installed foreman 1.1rc5 using the installer > which worked without any error and the web interface can be navigated but > foreman-proxy only returns "connection reset by peer". I tried setting the > log level to DEBUG but no proxy.log file is written at all. > > Any ideas what this could be? When I installed foreman 1.0.2 the same way > I didn't see this issue. > > Regards, > Dennis >
3

So now that the proxy is sorted I try to import the environments an I am
greeted with a 500 internal server error. The foreman log says this:

Started GET "/environments/import_environments?proxy=1-local-proxy" for
10.99.0.1 at Sun Feb 03 17:37:30 +0100 2013
Processing by EnvironmentsController#import_environments as HTML
Parameters: {"proxy"=>"1-local-proxy"}
Operation FAILED: 500 Internal Server Error
Rendered home/_topbar.rhtml (1.9ms)
Rendered common/500.rhtml within layouts/application (9.8ms)
Completed 500 Internal Server Error in 165ms (Views: 12.1ms | ActiveRecord:
1.2ms)

The "1-local-proxy" bit looks a bit suspicious to me.

··· On Sunday, February 3, 2013 5:36:39 PM UTC+1, Dennis Jacobfeuerborn wrote: > > Turns out that the SSL stuff doesn't seem to work. After commenting out > these three lines I no longer get the connection reset error: > > #:ssl_ca_file: /var/lib/puppet/ssl/certs/ca.pem > #:ssl_certificate: /var/lib/puppet/ssl/certs/foreman11.local.pem > #:ssl_private_key: /var/lib/puppet/ssl/private_keys/foreman11.local.pem > > Regards, > Dennis > > On Sunday, February 3, 2013 5:29:07 PM UTC+1, Dennis Jacobfeuerborn wrote: >> >> Hi, >> so I set up a new VM and installed foreman 1.1rc5 using the installer >> which worked without any error and the web interface can be navigated but >> foreman-proxy only returns "connection reset by peer". I tried setting the >> log level to DEBUG but no proxy.log file is written at all. >> >> Any ideas what this could be? When I installed foreman 1.0.2 the same way >> I didn't see this issue. >> >> Regards, >> Dennis >> >
4

That you had to comment out the SSL configuration directives suggest to me
that you're not hitting the proxy on an https url - if I recall, the proxy
doesn't do a redirect, so you have to be explicit about the
https://protocol in the Foreman Smart Proxy UI page.

As for the Error 500, the logs are fine but uninformative - can you provide
the logs from the proxy when you attempt an import?