Open agross opened 4 months ago
Hi @agross,
Thanks for your feedback. Icinga monitoring consists of several components and this one here "simply" does the monitoring part but does not include the web interface. For the full stack, have a look here:
https://github.com/lippserd/docker-compose-icinga
Best regards, Eric
Thank you for the feedback, I'll have a look! You may close this issue or keep it open if you want to act on my feedback.
Hello,
today I wanted to try Icinga2. Since I like hosting services using containers I didn’t bother installing Icinga using packages but headed straight here. I executed the commands from the README and tried to access the published port
5665
using my web browser. This is what I was greeted with after following the steps outlined in the README:The "master" container logged this every time I tried to access
http://localhost:5665
:After 30 minutes of wondering what was wrong, I had the idea that the container would do TLS termination itself by default. This is rather unusual as a default since most images expect you to place a reverse proxy in front of them. So I tried
https://localhost:5665
and was greeted with a login dialog.The login dialog did not accept default credentials I tried - like
admin/admin
. A Google search brought up the auth docs but this page does not list the default login. The https://default-password.info/icinga/icinga-web-2 page suggests to useicingaadmin/icinga
- which didn't work either.This is where I'm currently stuck.
I hope this feedback helps to improve the onboarding process for new users. I can see how as developers or long-term users of Icinga the initial setup must be obvious to you. As a new user who doesn't know the ins and outs of the system it might feel very differently.