secure connection between Fusion to XI

[elade]

Hi unfortunately I cant open remote session.
I did both SSL manuals for XI and Fusion with self signed certificate.
Close all HTTP communication between the 2 servers.
Still I can’t get fusion to fused this XI with https in the url section.
Telnet is working with port 443 from and to both servers.
Both servers are ubuntu 16 in AWS.

What logs/configuration or other info do you need in order to investigate?

[ssax]

Ok, that's definitely going to be a lot tougher.

Are you using a proxy in Admin > Proxy Configuration in your Fusion server?

When accessing the Fusion web interface, are you using http or https in the URL?

What do you have set for Admin > System Settings > Internal URL?

[elade]

Are you using a proxy in Admin > Proxy Configuration in your Fusion server?

No

What do you have set for Admin > System Settings > Internal URL?

https:/serverip/nagiosxi/

both Fusion and XI are accessed in https

[ssax]

What version of XI is the server running exactly?

In the Nagios Fusion web interface go to Admin > System Settings:
- Set Log Level to trace
- Check the box next to Enable writing log data to the specified file
- Check the box next to Enable writing debug data to the specified file.

Then in that same SSH session, please run this command (as root) and LEAVE IT RUNNING:

Code: Select all

tail -Fn0 /var/log/messages /var/log/cron /var/log/httpd/error_log /var/log/httpd/ssl_error_log /usr/local/nagiosfusion/var/log/*.log

Then go to Admin in the web interface and under the "Subsys Status" section, click the gear icon to the right of Polling Locks and then click the "Clear polling locks" button.

Now wait 10 minutes and send me the full output from the still running tail command above.

Click the Test Fusion Settings button while that tail command is still running as well.

Do you see anything standing out?

The only other thing I can think is if you hardened apache on the XI server or something.

[elade]

Hi,

I found out what was the problem and fixed it.
You can close the topic

Thank you!

[ssax]

Can you post what the resolution was so it can help us/and others in the future?

[elade]

When I created the Certificate the Common Name must be an IP at least in my case.

[scottwilkerson]

When I created the Certificate the Common Name must be an IP at least in my case.

Great!

Locking