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:
[2024-03-26 08:19:50 +0000] critical/ApiListener: Client TLS handshake failed (from [::ffff:192.168.65.1]:59360): http request
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 use icingaadmin/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.
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
5665using 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:5665and 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.