Can LibreNMS communicate with oxidized using HTTPS with self-signed certificate?

I have Oxidized and LibreNMS on separate boxes.
Oxidized web UI is http only, but mine is sitting behind nginx proxy that adds SSL with self-signed certificate.
My problem is, when I point LibreNMS to Oxidized https address it won’t work.
If I point LibreNMS to the http address of oxidized, it does work. Curl gives the same response from http and https. So the problem seems to be with LibreNMS when https address for Oxidized is used.
Possibly because it uses self-signed certificate. Possibly because LibreNMS simply won’t work with Oxidized when https is used. I’m not sure.

Has anybody done something like this before? Or does anybody know if it should/shouldn’t be possible in principle?

1 Like