HTTPS LibreNMS + Oxidized API

Lucheni · 25 August 2016 09:28

Hi,

Was wondering if anyone had successfully setup LibreNMS to use only HTTPS and at the same time keep the API-communication with Oxidized working. As it stands now, with HTTPS LibreNMS oxidized can’t seem to return API calls and at the same time spews HTTP parse errors while running.

2016-08-25 10:52:21 +0200: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>
2016-08-25 10:52:21 +0200: ENV: {“rack.version”=>[1, 3], “rack.errors”=>#<IO:>, “rack.multithread”=>true, “rack.multiprocess”=>false, “rack.run_once”=>false, “SCRIPT_NAME”=>"", “QUERY_STRING”=>"", “SERVER_PROTOCOL”=>“HTTP/1.1”, “SERVER_SOFTWARE”=>“2.16.0”, “GATEWAY_INTERFACE”=>“CGI/1.2”}

Has anyone encountered this and have any leads on where to look for a solution?

Lucheni · 25 August 2016 09:56

github.com/ytti/oxidized

SSL issues when running over Librenms using https

opened 04:27PM - 03 May 16 UTC

closed 07:10PM - 27 Sep 17 UTC

brokerdavelhr

user_pending

I have set up LIbrenms to use https only. Now that I have my cert etc done and t…hat up and running, I then tried to install oxidized. All was going well until this step: root@ubuntu:/opt/librenms# oxidized I, [2016-05-03T01:07:20.004152 #122586] INFO -- : Oxidized starting, running as pid 122586 F, [2016-05-03T01:07:20.034261 #122586] FATAL -- : Oxidized crashed, crashfile written in /root/.config/oxidized/crash SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed I understand both were written with http support mainly, but I needed https. Is there anyway to point oxidized to where the crt and key are like I did in apache? SSLEngine on SSLCertificateFile "/etc/ssl/certs/server.crt" SSLCertificateKeyFile "/etc/ssl/private/server.key" ? Sorry if this is a stupid question...still getting used to the finer points in Linux... I am running Ubuntu 10.04 lte with ruby=>2 etc already installed and running.

murrant · 25 August 2016 11:50

Are you using the same hostname as in your SSL cert?

laf · 26 August 2016 06:55

We run LibreNMS with https only and talk to the Oxidized API with no issues so it’s certainly possible.

Where are those errors from?

Lucheni · 29 August 2016 13:13

Those errors were from an instance of Oxidized. These errors seems to have resolved themselves though and now I am stuck with a port already in use error when reading through the oxidized crash log. Will have a go at it tomorrow and if I solve it I will share whatever it was I messed up.