Wordpress site stopped loading on Docker v4.58.0

Docker Desktop
1

Hello, dear Docker community!

I’m facing a very unusual problem. I am new to Docker and about a month ago decided to use it for local WordPress development. According to the manuals available online, I’ve created the necessary containers.

Here’s the compose.yml file:

services:
  db:
    image: mysql
    environment:
      MYSQL_DATABASE: wordpress_db
      MYSQL_USER: db_user
      MYSQL_PASSWORD: db_user_pass
      MYSQL_ROOT_PASSWORD: securepassword
    volumes:
      - db:/var/lib/mysql

  wordpress:
    image: wordpress:6.9.0-php8.5-apache
    ports:
     - 8080:80
    environment:
      WORDPRESS_DB_HOST: db
      WORDPRESS_DB_NAME: wordpress_db
      WORDPRESS_DB_USER: db_user
      WORDPRESS_DB_PASSWORD: db_user_pass
    volumes:
     - wordpress:/var/www/html

volumes:
  wordpress:
  db:

For about a month, everything worked perfectly and very fast! However, today I launched the containers again and realized that the website is not loading whatsoever. I tried standard debugging techniques, like renaming the plugin folder to see if there were any issues there, but it didn’t help. The site is still not loading.

Here’s a screenshot of the containers in Docker GUI:

Screenshot 2026-01-28 155532
Screenshot 2026-01-28 155532953×191 15.1 KB

It looks like the problem appeared after I updated Docker to the latest version and rebooted my PC. Other than that, I haven’t made any changes to the website files or the DB.

Here are the log for wordpress-1 container after its restart:

[Wed Jan 28 13:27:28.662099 2026] [mpm_prefork:notice] [pid 1:tid 1] AH00170: caught SIGWINCH, shutting down gracefully

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.3. Set the 'ServerName' directive globally to suppress this message

[Wed Jan 28 13:27:30.262713 2026] [mpm_prefork:notice] [pid 1:tid 1] AH00163: Apache/2.4.65 (Debian) PHP/8.5.0 configured -- resuming normal operations

[Wed Jan 28 13:27:30.262771 2026] [core:notice] [pid 1:tid 1] AH00094: Command line: 'apache2 -D FOREGROUND'

172.18.0.1 - - [28/Jan/2026:13:27:51 +0000] "POST /wp-cron.php?doing_wp_cron=1769606871.9530580043792724609375 HTTP/1.1" 200 284 "-" "WordPress/6.9; [http://host.docker.internal:8080"](http://host.docker.internal:8080"/)

172.18.0.1 - - [28/Jan/2026:13:27:50 +0000] "GET / HTTP/1.1" 301 380 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.0"

And here are the logs for its DB “db-1”:

2026-01-28T13:29:21.123350Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 9.5.0).

2026-01-28 13:29:22+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.5.0-1.el9 started.

2026-01-28 13:29:22+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'

2026-01-28 13:29:22+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.5.0-1.el9 started.

'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'

2026-01-28T13:29:23.126018Z 0 [System] [MY-015015] [Server] MySQL Server - start.

2026-01-28T13:29:23.389672Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.5.0) starting as process 1

2026-01-28T13:29:23.389698Z 0 [System] [MY-015590] [Server] MySQL Server has access to 32 logical CPUs.

2026-01-28T13:29:23.389721Z 0 [System] [MY-015590] [Server] MySQL Server has access to 25147080704 bytes of physical memory.

2026-01-28T13:29:23.398414Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.

2026-01-28T13:29:23.846394Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.

2026-01-28T13:29:24.114635Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.

2026-01-28T13:29:24.114692Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.

2026-01-28T13:29:24.119035Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.

2026-01-28T13:29:24.147836Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock

2026-01-28T13:29:24.147999Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '9.5.0'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.

Has anyone faced the same problem? Please help! =)

2

I don’t think database logs are relevant here. What we should figure out what it means that the site is not loading. You are using port forwarding to access wordpress on port 8080. So I assume you try to load it in a web browser using localhost:8080, right?

What happens then? do you get a response from the browser that the site is not available? Do you get a white page maybe?

The access logs show some GET and POST requests. Were those logs shown after you tried to access Wordpress or were they there before and now your requests can’t even reach wordpress?

so basically the most important question whether you have a network issue or Wordpress loads and you just can’t see the expected output because it fails to return that.

3

Thanks for your reply!

I am getting this when trying to load the website:

Screenshot 2026-01-28 202708
Screenshot 2026-01-28 2027081774×1108 38 KB

4

And now I have tried to reach admin panel of WP and I got this:

Screenshot-2026-01-28-202846.png

Hope that makes it a bit more clear =)

5

I’m confused. host.docker.internal is a domain that can be used from inside a container to access a port on the actual host’s “localhost” when using Docker Desktop. I would not use it to access services in Docker Desktop itself. But now your logs make sense. I didn’t understand this domain in the logs.

I’m not sure how it worked befoe, but I would either use “localhost” or any other domain registered in the hosts file on Windows pointing to 127.0.0.1 to access forwarded ports to Docker Desktop.

Since the exact issue is still not clear, before recommending any specific possible solution, can you check the browser logs when you see the login page without proper style? You should see more info in the developer console on the Network tab (after reloading the page while the tab is open). Usually appears when pressing F12, but depends on the browser.

Than you wil see what it wants to load, why it canot load CSS and probably javascript and we can get closer to what’s wrong.

8

UPDATE: I’ve just fixed the issue. You were right! The problem was the address, which for some reason stopped working properly even though it worked fine before the last update.

I’ve just added these lines to the wp-config.php file:

define('WP_HOME', 'http://localhost:8080');
define('WP_SITEURL', 'http://localhost:8080');

For those who may encounter a similar problem in the future.

Thanks a lot!!! :face_blowing_a_kiss: