Nagios Network Analyzer fresh install issues

[sgardil]

ok. Along with the static ip, I had a DNS host A record for the name nagiosna.mysite.com to resolve to the static ip address I was using. I was using that to access the web page, which worked fine for the initial web page, for the licensing info, and nagiosadmin password, etc.... Once I updated APP_URL in .env to use APP_URL=http://nagiosna.mysite.com, I can login.

Thanks for the help.

Glad to help and happy that we could diagnose the issue. We will look into it more to see if we can find a viable solution for the software to better handle ip address changes when the ip differs in the environment file.

[scorpion1976]

I saw a few more weird things happening when using http://nagiosna.mysite.com so I've reverted .env to use only the ip address and not the fqdn, and will access it only using http://<ip address>.

[sgardil]

I saw a few more weird things happening when using http://nagiosna.mysite.com so I've reverted .env to use only the ip address and not the fqdn, and will access it only using http://<ip address>.

Got it, good to know. What were the weird things you noticed happening when using the FQDN btw if you dont mind me asking? There should be a fix in to allow for dynamic ip's in the next release that should also potentially fix issues you might be having using a FQDN.

For others experiencing this is as well, if you arn't using a FQDN you can run this command and it should update your app_url to be the correct ip address.

Code: Select all

sed -i "s|^APP_URL=.*|APP_URL=http://$(hostname -I | awk '{print $1}')|" /var/www/html/nagiosna/.env && cd /var/www/html/nagiosna && php artisan config:clear

If using a FQDN or are running multiple outward facing interfaces then you may want to manually update the APP_URL variable in

Code: Select all

/var/www/html/nagiosna/.env

[scorpion1976]

Sorry just seeing this now... The license information was complaining that I was both licensed fine with 147 or so days remaining, and that I also needed to activate my license (saying that I was not activated). After changing the .env back to only use the ip address, the problem went away.

[sgardil]

Sorry just seeing this now... The license information was complaining that I was both licensed fine with 147 or so days remaining, and that I also needed to activate my license (saying that I was not activated). After changing the .env back to only use the ip address, the problem went away.

Hm got it, so using a FQDN at all right now is pretty much out of the picture, good to know. We are looking to get a build out early next month that should have a fix for this. We would still want the main IP address as the APP_URL in the .env file but it should allow you to connect with a FQDN. Thanks for reporting the findings and working with us.