wallabag / wallabag/docker

Error nginx 2.6.8

Open
#395 4 comments 0 reactions 0 assignees View on GitHub
Awaiting response
Dominant language
Shell
Stars
769
Forks
168
PR merge metrics
No merged PRs in 30d

Description

Hello,

After the last update `2.6.8`. I get the following error:

```bash
wallabag | 2024/01/11 13:18:17 [emerg] 153#153: still could not bind()
wallabag | nginx: [emerg] still could not bind()
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to [::]:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to [::]:80 failed (98: Address in use)
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address in use)
wallabag | 2024/01/11 13:18:20 [emerg] 155#155: bind() to [::]:80 failed (98: Address in use)
wallabag | nginx: [emerg] bind() to [::]:80 failed (98: Address in use)
```

Contributor guide

No contributing guide indexed for this repository

Research direction

The report only identifies the 2.6.8 update and nginx bind() errors on port 80. Start by comparing the 2.6.8 Docker configuration with the previous release and reproducing the container startup; done means identifying the cause of the port conflict and confirming a working startup configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.