Wordpress-Container start, but no connection to Website #943

phillipunzen · 2025-02-24T13:35:07Z

phillipunzen
Feb 24, 2025

Hello everyone,
I run my WordPress websites within a Kubernetes cluster. And unfortunately I have a problem with the latest wordpress:latest image that I can't connect to the website.

I just don't get a response on port 80. If I then switch to the container's shell and enter curl http://127.0.0.1:80, the query hangs and doesn't get a response. I then have to cancel it with CTRL + C.

To test whether this is perhaps a Kubernetes cluster problem, I did the same on my Docker server. A new installation with the latest tag cannot be opened either.

The ports are open, there is just no response. Maybe the following will help:

# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp6 0 0 :::80 :::* LISTEN 1/apache2
# curl http://127.0.0.1:80
^C

The liveness and readiness probes also logically fail. It seems that the web server is not delivering any data or is not responding. But it is sufficient to keep the port open.

yosifkit · 2025-02-24T18:29:46Z

yosifkit
Feb 24, 2025
Maintainer

I am unable to reproduce the issue. I ran wordpress:latest in one terminal and tested from another.

$ docker run -it --rm --name wordy wordpress:latest
Unable to find image 'wordpress:latest' locally
latest: Pulling from library/wordpress
63eaf96fd2ee: Pull complete
beeeb2e72514: Pull complete
b7fd27be5b20: Pull complete
8ca47539e139: Pull complete
c6834909cd19: Pull complete
e2a530cb2e77: Pull complete
4f4fb700ef54: Pull complete
814b6ecb84b0: Pull complete
ea823f46cc3c: Pull complete
ed50d9a76bab: Pull complete
a4e58aa84c36: Pull complete
bcbecb454049: Pull complete
f473bcbd0e44: Pull complete
1475f50d3e62: Pull complete
08dc3bd6914b: Pull complete
68d70c2b9fc9: Pull complete
5ac3fe5e5e7e: Pull complete
b545bb7ff18e: Pull complete
5c36aa47b3f5: Pull complete
b9903ecbcf0b: Pull complete
d8b79b64a9d5: Pull complete
Digest: sha256:0211348df9f5e29a32cb6a65ec5aff2c2e775670fdb054ab98f7833eb539234a
Status: Downloaded newer image for wordpress:latest
WordPress not found in /var/www/html - copying now...
Complete! WordPress has been successfully copied to /var/www/html
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
[Mon Feb 24 17:54:06.988521 2025] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.62 (Debian) PHP/8.2.27 configured -- resuming normal operations
[Mon Feb 24 17:54:06.988756 2025] [core:notice] [pid 1:tid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
172.17.0.1 - - [24/Feb/2025:17:54:42 +0000] "GET / HTTP/1.1" 302 231 "-" "curl/7.88.1"
172.17.0.1 - - [24/Feb/2025:17:55:00 +0000] "GET / HTTP/1.1" 302 231 "-" "curl/7.88.1"
172.17.0.1 - - [24/Feb/2025:17:55:00 +0000] "GET /wp-admin/setup-config.php HTTP/1.1" 200 13470 "-" "curl/7.88.1"
127.0.0.1 - - [24/Feb/2025:17:55:47 +0000] "GET / HTTP/1.1" 302 230 "-" "curl/7.88.1"
127.0.0.1 - - [24/Feb/2025:17:55:47 +0000] "GET /wp-admin/setup-config.php HTTP/1.1" 200 13462 "-" "curl/7.88.1"
^C[Mon Feb 24 17:56:20.458055 2025] [mpm_prefork:notice] [pid 1:tid 1] AH00169: caught SIGTERM, shutting down

And in the second terminal:

$ docker container inspect --format '{{ .NetworkSettings.IPAddress }}' wordy
172.17.0.2
$ curl 'http://172.17.0.2'
$ # returned instantly, (oh, from the apache logs, that was a 302 redirect, so I need `-L` for my curl)
$ curl -fL 'http://172.17.0.2'
<!DOCTYPE html>
...
$ docker exec -it wordy bash
root@b33ee9f6f736:/var/www/html# curl -fL 'http://127.0.0.1'
<!DOCTYPE html>
...

0 replies

phillipunzen · 2025-02-24T18:52:52Z

phillipunzen
Feb 24, 2025
Author

Strange, do you have any idea how I can solve the problem?

5 replies

tianon Feb 24, 2025
Maintainer

Can you provide more information about exactly how you're running the container? Any interesting arguments/configuration? If you run @yosifkit's example verbatim, does it work, or does it fail too?

phillipunzen Feb 25, 2025
Author

I ran the example from him, and i get the same error.
My Docker and Kubernetes-Server runs in a Debian 12 Installation in a VMware vSphere Cluster.

This is my Kubernetes-Deployment:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: wp
  namespace: websites
spec:
  replicas: 1
  selector:
    matchLabels:
      app: wp
  template:
    metadata:
      labels:
        app: wp
    spec:
      containers:
      - name: wp
        image: wordpress:latest
        imagePullPolicy: Always
        ports:
        - name: http
          containerPort: 80
        env:
        - name: WORDPRESS_DB_HOST
          value: "192.168.10.10"
        - name: WORDPRESS_DB_USER
          value: "wordpress"
        - name: WORDPRESS_DB_PASSWORD
          value: "passwort"
        - name: WORDPRESS_DB_NAME
          value: "wordpress_wp"
#        readinessProbe:
#          httpGet:
#            path: /
#            port: 80
#          initialDelaySeconds: 30
#          periodSeconds: 10
#        livenessProbe:
#          httpGet:
#            path: /
#            port: 80
#          initialDelaySeconds: 30
#          periodSeconds: 10
        volumeMounts:
        - name: pvc-wordpress-pcwikide
          mountPath: /var/www/html
      volumes:
      - name: pvc-wordpress-pcwikide
        persistentVolumeClaim:
          claimName: pvc-wordpress-pcwikide

And this is my docker-compose.yml:

services:
  wordpress:
    image: wordpress
    restart: always
    ports:
      - 8081:80
    environment:
      WORDPRESS_DB_HOST: 192.168.10.10
      WORDPRESS_DB_USER: wordpress
      WORDPRESS_DB_PASSWORD: Passwort
      WORDPRESS_DB_NAME: wordpress_wp
    volumes:
      - ./wordpress1:/var/www/html

What really puzzles me is that even in the container itself a curl on localhost with port 80 is not successful, and according to netstat it only listens on IPv6. IPv4 won't start at all. But according to ports.conf, the IPv4 interface should also listen.

# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp6       0      0 :::80                   :::*                    LISTEN      1/apache2

LaurentGoderre Feb 25, 2025
Collaborator

What version of the docker engine are you running?

phillipunzen Feb 25, 2025
Author

i used the 28.0.0 Version.
But since the error also occurs in Kubernetes, one can assume that it is not a Docker-specific problem?

Client: Docker Engine - Community
 Version:           28.0.0
 API version:       1.48
 Go version:        go1.23.6
 Git commit:        f9ced58
 Built:             Wed Feb 19 22:10:43 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          28.0.0
  API version:      1.48 (minimum version 1.24)
  Go version:       go1.23.6
  Git commit:       af898ab
  Built:            Wed Feb 19 22:10:43 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.25
  GitCommit:        bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc:
  Version:          1.2.4
  GitCommit:        v1.2.4-0-g6c52b3f
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

tianon Feb 25, 2025
Maintainer

My best guess is firewall or kernel configuration on your hosts -- are they set up in the same way, same OS, same configuration between your k8s and Docker nodes?

Listening only on IPv6 is normal because listening on the IPv6 wildcard on Linux will also listen on IPv4. I know there's a way to disable that, and I think that's net.ipv6.bindv6only -- you don't happen to have that set, do you?

LaurentGoderre · 2025-03-04T01:43:54Z

LaurentGoderre
Mar 4, 2025
Collaborator

Version 28.0.0 has a few issues with networking such as moby/moby#49511. Would it be possible to try upgrading to 28.0.1 to see if it resolves your issue?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Wordpress-Container start, but no connection to Website #943

{{title}}

Replies: 3 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Wordpress-Container start, but no connection to Website #943

phillipunzen Feb 24, 2025

Replies: 3 comments · 5 replies

yosifkit Feb 24, 2025 Maintainer

phillipunzen Feb 24, 2025 Author

tianon Feb 24, 2025 Maintainer

phillipunzen Feb 25, 2025 Author

LaurentGoderre Feb 25, 2025 Collaborator

phillipunzen Feb 25, 2025 Author

tianon Feb 25, 2025 Maintainer

LaurentGoderre Mar 4, 2025 Collaborator

phillipunzen
Feb 24, 2025

Replies: 3 comments 5 replies

yosifkit
Feb 24, 2025
Maintainer

phillipunzen
Feb 24, 2025
Author

tianon Feb 24, 2025
Maintainer

phillipunzen Feb 25, 2025
Author

LaurentGoderre Feb 25, 2025
Collaborator

phillipunzen Feb 25, 2025
Author

tianon Feb 25, 2025
Maintainer

LaurentGoderre
Mar 4, 2025
Collaborator