Minion to reach OpenNMS server https, behind a reverse proxy

I’ve got an OpenNMS session running in the cloud, reachable over https/443 (it’s running in the backend of a reverse proxy).
I opened the tcp/61616 and i’ve NAT’d it ok to the OpenNMS.

Now I’m trying to connect my first test minion to it, so following the Minion install guide

ssh -p 8201 admin@localhost
admin@minion> config:property-set http-url http://%opennms_inthecloud%:443
admin@minion> config:property-set broker-url failover:tcp://%opennms_inthecloud%:61616
admin@minion> config:update
admin@minion> opennms:scv-set opennms.http minion minion
admin@minion> opennms:scv-set opennms.broker minion minion
systemctl restart minion

admin@minion> health-check
Verifying the health of the container

Connecting to OpenNMS ReST API [ Failure ] => %opennms_inthecloud%:443 failed to respond
Verifying installed bundles [ Starting ] => Bundle 307 is waiting for dependencies
Connecting to JMS Broker [ Success ]

=> Oh no, something is wrong

I think or the syntax for the https is wrong, or i’ve got to do something on the reverse proxy maybe?

Has anyone had any success with connecting minions to reverse-proxied OpenNMS servers?

Thanks.

Try using https://%opennms_inthecloud%/opennms instead ofhttp://%opennms_inthecloud%:443 for the URL:

  1. https instead of http
  2. include /opennms in the path
1 Like

admin@minion> health-check
Verifying the health of the container

Connecting to OpenNMS ReST API [ Success ]
Verifying installed bundles [ Success ]
Connecting to JMS Broker [ Success ]

=> Everything is awesome

Many thanks Jesse.