[BUG] Custom Wordpress Location - Error establishing a database connection

[linkthepirate]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Site loads not secure with : Error establishing a database connection

Expected Behavior

Site should load

Steps To Reproduce

I have a docker-compose.yaml which contains my entire stack and network. I have everything in the one directory so all configs are:

./service_name/config:/config

I have used swag since it was called letsencrypt so my folder says that, anyway.

I have wordpress working with the local ip and can access no problem with the actual database connection, edit and publish pages, the works.

I followed this guide: https://docs.linuxserver.io/general/swag/#hosting-a-wordpress-site

I have this volume:

/home/my_admin/apps:/apps

I noticed that when this is declared:

root /config/sites/mydomain.tld/www

the index file is directly under that, it's not the case with my wordpress instance so I modified the root to be:

root /apps/wordpress/var/www/html;

This is after I tried to get around this by using symbolic link. I saw issue 137 but the op never replied. Maybe they did something else entirely, idk.

Environment

- OS: Debian 11 Bullseye
- How docker service was installed: https://docs.docker.com/compose/install/linux/

CPU architecture

x86-64

Docker creation

wordpress:
    container_name: wordpress
    hostname: wordpress
    image: wordpress:6.7-php8.3-apache
    restart: unless-stopped
    environment:
      PUID: $PUID
      PGID: $PGID
      WORDPRESS_DB_HOST: wordpress-db
      WORDPRESS_DB_USER: wordpress
      WORDPRESS_DB_PASSWORD: $WORDPRESS_DF_DB_PASSWORD
      WORDPRESS_DB_NAME: wordpress
    volumes:
      - ./wordpress/var/www/html:/var/www/html
    networks:
      - gate
    ports:
      - 8888:80
    depends_on:
      - wordpress-db
  wordpress-db:  
    container_name: wordpress-db
    image: mariadb:10.6
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: $WORDPRESS_DF_DB_PASSWORD
      MYSQL_DATABASE: wordpress
      MYSQL_USER: wordpress
      MYSQL_PASSWORD: $WORDPRESS_DF_DB_PASSWORD
    volumes:
      - ./wordpress-db/var/lib/mysql:/var/lib/mysql
    networks:
      - gate

Container logs

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 3.1.0-ls360
Build-date: 2025-01-25T03:21:46+00:00
───────────────────────────────────────

using keys found in /config/keys
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2023-08-13 │ 2024-12-06 │ /config/nginx/ssl.conf                                                 │
│ 2020-05-23 │ 2024-03-14 │ /config/nginx/authelia-location.conf                                   │
│ 2018-08-10 │ 2022-08-20 │ /config/nginx/ldap-server.conf                                         │
│ 2020-05-23 │ 2024-03-16 │ /config/nginx/authelia-server.conf                                     │
│ 2023-06-05 │ 2024-12-17 │ /config/nginx/site-confs/default.conf                                  │
│ 2023-04-13 │ 2024-12-17 │ /config/nginx/nginx.conf                                               │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
**** The following site-confs have extensions other than .conf ****
**** This may be due to user customization. ****
**** You should review the files and rename them to use the .conf extension or remove them. ****
**** nginx.conf will only include site-confs with the .conf extension. ****
/config/nginx/site-confs/default.conf.old
Variables set:
PUID=1000
PGID=1000
TZ=$TIMEZONE
URL=domain1.tld
SUBDOMAINS=wildcard
EXTRA_DOMAINS=domain2.tld
ONLY_SUBDOMAINS=false
VALIDATION=dns
CERTPROVIDER=
DNSPLUGIN=$PROVIDER
EMAIL=
STAGING=

Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Wildcard cert for domain1.tld will be requested
EXTRA_DOMAINS entered, processing
Extra domains processed are: domain2.tld
No e-mail address entered or address invalid
dns validation via digitalocean plugin is selected
Certificate exists; parameters unchanged; starting nginx
The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
/config/nginx/geoip2.conf exists.
        Please migrate to https://github.com/linuxserver/docker-mods/tree/swag-maxmind
/config/nginx/ldap.conf exists.
        Please apply any customizations to /config/nginx/ldap-server.conf
        Ensure your configs are updated and remove /config/nginx/ldap.conf
        If you do not use this config, simply remove it.
[custom-init] No custom files found, skipping...
[ls.io-init] done.
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:15
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:16
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/airsonic.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/airsonic.subdomain.conf:8
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/audiobookshelf.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/audiobookshelf.subdomain.conf:13
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/bookstack.subdomain.conf:15
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/bookstack.subdomain.conf:16
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/calibre-web.subdomain.conf:13
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/calibre-web.subdomain.conf:14
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/emby.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/emby.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/emby.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/emby.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/filebrowser.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/filebrowser.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/grocy.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/grocy.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/grocy.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/grocy.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/guacamole.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/guacamole.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/navidrome.subdomain.conf:14
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/navidrome.subdomain.conf:14
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/navidrome.subdomain.conf:15
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/navidrome.subdomain.conf:15
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/nextcloud.subdomain.conf:18
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/nextcloud.subdomain.conf:19
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/ombi.subdomain.conf:10
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/ombi.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/organizr.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/organizr.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/organizr.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/organizr.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/photoprism.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/photoprism.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/photoprismprv.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/photoprismprv.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/photoview.subdomain.conf:12
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/photoview.subdomain.conf:13
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/plex.subdomain.conf:10
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/plex.subdomain.conf:11
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/podgrab.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/podgrab.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/tautulli.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/tautulli.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/wizarr.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for 0.0.0.0:443 in /config/nginx/proxy-confs/wizarr.subdomain.conf:6
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/proxy-confs/wizarr.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: protocol options redefined for [::]:443 in /config/nginx/proxy-confs/wizarr.subdomain.conf:7
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/domain2.tld.conf:15
2025/02/05 17:17:06 [warn] 791#791: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/domain2.tld.conf:16
2025/02/05 17:17:06 [warn] 791#791: conflicting server name "media.*" on 0.0.0.0:80, ignored
2025/02/05 17:17:06 [warn] 791#791: conflicting server name "" on 0.0.0.0:80, ignored
2025/02/05 17:17:06 [warn] 791#791: conflicting server name "media.*" on [::]:80, ignored
2025/02/05 17:17:06 [warn] 791#791: conflicting server name "" on [::]:80, ignored

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[linkthepirate]

Relevant, the nginx conf, didn't have a spot for it in the initial post.

# redirect all traffic to https
server {
    listen 80; #default_server;
    listen [::]:80; #default_server;
    server_name mydomain.tld www.mydomain.tld;
    location / {
        return 301 https://$host$request_uri;
    }
}

# main server block
server {
    listen 443 ssl http2; # default_server;
    listen [::]:443 ssl http2; # default_server;
    server_name mydomain.tld www.mydomain.tld;
    include /config/nginx/ssl.conf;
    # root /config/www;
    # root /config/sites/mydomain.tld/www;
    root /apps/wordpress/var/www/html;

    index index.html index.htm index.php;
    location / {
        try_files $uri $uri/ /index.html /index.php$is_args$args =404;
        #try_files $uri $uri/ /index.html /index.php$is_args$args;
    }
    location ~ ^(.+\.php)(.*)$ {
      
        fastcgi_split_path_info ^(.+\.php)(.*)$;
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_index index.php;
        include /etc/nginx/fastcgi_params;
    }
    # deny access to .htaccess/.htpasswd files
    location ~ /\.ht {
        deny all;
    }
}
# enable subdomain method reverse proxy confs
# include /config/nginx/proxy-confs/*.subdomain.conf;
# enable proxy cache for auth
# proxy_cache_path cache/ keys_zone=auth_cache:10m;

[j0nnymoe]

I'm not entirely sure what you're crossing container paths with wordpress/swag. If you're using their docker container, just edit the nginx config to point at wordpress:80 address rather than trying to load the files directly.

Swag is likely isn't picking up this ENV's because they're not out into a config file that it can read.

[linkthepirate]

That was the very first thing I did, my wordpress.sudomain(replaced with mydomain).conf

I get "welcome to our server"

## Version 2024/07/16
# make sure that your wordpress container is named wordpress
# make sure that your dns has a cname set for wordpress

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name mydomain.tld www.mydomain.tld;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth (requires ldap-location.conf in the location block)
    #include /config/nginx/ldap-server.conf;

    # enable for Authelia (requires authelia-location.conf in the location block)
    #include /config/nginx/authelia-server.conf;

    # enable for Authentik (requires authentik-location.conf in the location block)
    #include /config/nginx/authentik-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable for ldap auth (requires ldap-server.conf in the server block)
        #include /config/nginx/ldap-location.conf;

        # enable for Authelia (requires authelia-server.conf in the server block)
        #include /config/nginx/authelia-location.conf;

        # enable for Authentik (requires authentik-server.conf in the server block)
        #include /config/nginx/authentik-location.conf;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app wordpress;
        set $upstream_port 80;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }
}

[j0nnymoe]

Is wordpress/swag sharing the same docker network?

[j0nnymoe]

It's also worth noting, you're running old nginx configs so might be wise to get those updated.

[linkthepirate]

Yes

 swag:  # Reverse Proxy - See it's page: https://github.com/linuxserver/docker-swag
    cap_add:
      - NET_ADMIN
    container_name: swag
    environment:
      - VALIDATION=dns
      - DNSPLUGIN=$SWAG_DNS
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TIMEZONE
      - URL=$SWAG_URL
      - SUBDOMAINS=wildcard
      - ONLY_SUBDOMAINS=false
      - EXTRA_DOMAINS={redacted}
    image: linuxserver/swag:latest #2.7.3 #1.32.0-ls170 # These are other versions I was static on.
    networks:
      - gate
    ports:
      - 443:443/tcp
      - 80:80/tcp
    restart: unless-stopped
    volumes:
      - ./letsencrypt:/config     ## There is a proxy folder with all the sample files. NGINX
      - /home/administrator/apps:/apps

[linkthepirate]

It's also worth noting, you're running old nginx configs so might be wise to get those updated.

I just removed samples and re-created, it's the same version date.

[linkthepirate]

I mean I'm assuming that copying the wordpress.subdomain.conf would work, replacing the sudomain logic with my own domain. Please tell me if this is a fundamental inconsistency.

[j0nnymoe]

The proxy config is incorrect, subdomain isn't what's needed. Look at our example for Heimdall as root domain, it uses a subfolder conf but you have to adjust it slightly.

[linkthepirate]

Do I need to update 443 to 80? I changed the name to wordpress, but not sure what else I should do, as I've always use subdomain. I'm sure I have to add my domain somewhere though lol.

## Version 2023/02/05
# make sure that your heimdall container is named heimdall
# In order to use this location block you need to edit the default file one folder up and comment out the / location

location / {
    # enable the next two lines for http auth
    #auth_basic "Restricted";
    #auth_basic_user_file /config/nginx/.htpasswd;

    # enable for ldap auth (requires ldap-server.conf in the server block)
    #include /config/nginx/ldap-location.conf;

    # enable for Authelia (requires authelia-server.conf in the server block)
    #include /config/nginx/authelia-location.conf;

    # enable for Authentik (requires authentik-server.conf in the server block)
    #include /config/nginx/authentik-location.conf;

    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app wordpress;
    set $upstream_port 443;
    set $upstream_proto https;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;

}

[j0nnymoe]

Yes you need to change those relevant to the wordpress container.

[linkthepirate]

Ok I did - still get the welcome to our server message.