Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Aborted connection # to db: 'unconnected' user: 'unauthenticated' host: 'x.x.x.x' (This connection closed normally without authentication)

Open
  • Is something wrong?
#420 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker-compose, mariadb
Domain
databases, devops

Research direction

Start with the Docker Compose MariaDB service and reproduce the installation using the reported MariaDB versions and command options. Compare the resulting unauthenticated aborted-connection warning with the compose configuration; done means identifying the cause and documenting or applying a configuration that prevents the reported problem.

Written by the indexing model from the issue text.

Description

Hello
Since omnivore is going down, I decided to try wallabag, but I hit a snag.

I'm trying to install via docker compose.
Everything gets installed
Screenshot_67

But...
Mariadb returns:
[Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: '172.29.0.4' (This connection closed normally without authentication)

I found the supposed solution to this issue at the mariadb-docker github page:
Adding this
command: --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
to the mariadb compose would fix the problem..

So I did and nothing changed.. it still returns the same error.

I already tried:

  • several different mariadb versions from 10.4 to 11.4.2.
  • only --character-set-server=utf8mb4 in command

Have anyone gone through the same problem?
Thank you!

Dominant language
Shell
Stars
771
Forks
168
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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.

More from wallabag/docker

All issues in wallabag/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.