Icinga / Icinga/docker-icinga2

Out of box experience as a total beginner

Open
#123 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
73
Forks
29
PR merge metrics
No merged PRs in 30d

Description

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:

2024-03-26_09-19-56

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the README setup steps and the linked authentication documentation, then reproduce the published-port flow with the container. Done means a first-time user can determine the correct protocol and initial credentials from the repository's onboarding material and complete login without relying on external search.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.