My site has some SVGs. They work fine on the original site, but when restoring on a new domain from an UpdraftPlus back, all those SVGs fail with a server 403 “forbidden” error.

Even weirder than that is that any new SVG I upload after the restore does work! Huh?

I checked my file and folder permissions and owners via SSH and didn’t see any difference. They both have the same permissions, same owners, same group. But no matter what, the SVGs from the restore won’t load—not even opening their URLs directly! But new SVGs load just fine!

I’ve also already tried disabling all plugins and switching to a default theme and that doesn’t change anything.

Any ideas what to check further or how to fix this?

My situation:

I have a nginx installation on my debian server. I configured a general nginx.conf (http settings) and I have a list of sites-enabled. My nginx does basically the https termination for a couple of applications on my server. Now I installed wordpress in a docker environment.

I used the following docker compose file.

version: "3.9"

services:
  db:
    image: mysql:8.0
    container_name: db_wp
    restart: always
    environment:
      - MYSQL_DATABASE=wordpress
      - MYSQL_ROOT_PASSWORD=<MYPASSWORD>
      - MYSQL_USER=wordpress
      - MYSQL_PASSWORD=<ANOTHER_PASSWORD>
    volumes:
      - /opt/docker/instances/wordpress/dbdata:/var/lib/mysql

  wordpress:
    depends_on:
      - db
    image: wordpress:latest
    container_name: wordpress
    ports:
      - 127.0.0.1:9000:80
    restart: always
    environment:
      - WORDPRESS_DB_HOST=db:3306
      - WORDPRESS_DB_USER=wordpress
      - WORDPRESS_DB_PASSWORD=wordpress
      - WORDPRESS_DB_NAME=wordpress
    volumes:
      - /opt/docker/instances/wordpress/data:/var/www/html

volumes:
  db_data: {}

I configured Nginx to forward https to http//localhost:9000.

After completed startup I went to the server name where wordpress should be reachable, the installation screen came up asking for my language and I let the installation complete.

After that I had to login and was brought to the wp-admin page. Everything exactly as it should be.

Then I went to the themes config section, clicked on “Add new Theme” and I got his message:

An unexpected error occurred. Something may be wrong with www.ads-software.com or this server’s configuration. If you continue to have problems, please try the support forums.

The same as many posts complained about.

What did I checkout so far?

I went to the plugin config section and clicked on Add new Plugin. It worked. No Problems at all

By default, 3 Themes were provided after the installation. Instead of trying to install a new one I clicked on update on one of them. After a short while it said: Update succesfull

I went into the docker container (docker exec …..) of wordpress and did a network test with curl to api.www.ads-software.com. It is reachable

Everything seems to work perfectly but I still get this error for adding a new theme.

I also added a WP_DEBUG to my config but no debug is produced:

define( ‘WP_DEBUG’, true );

define( ‘WP_DEBUG_LOG’, ‘/var/www/html/logs/problems.log’) ;

No log is written.

Any ideas what could be my problem ? (I doubt that my problem is nginx related so I did not provide its config here)

I run 2x nginx container and 2x php container

nginx -> proxy to -> php container

If the redis cache is enabled using the gui it creates a file only in one php container the files is called

object-cache.php and it’s localed in the public/wp-content/object-cache.php

The problem is that wp-content can’t be a global storage as the specific version of plugins are baked in into the container image and they can’t change until the image is rebuild. This is to make sure that release is version controller/tested and can’t change.

Can this file be configurable so it can be created in the different location?

What I end up is to have 2 instances or more when the redis can only be enabled in one container.

I am trying to install Google Site Kit on a containerised docker which sits behind a Nginx proxy providing the ssl certificate. The site is operating and fully accessible, however when I click on the “Sign In with Google” on the Goggle Site Kit plugin, I receive the following error:

“The request to the authentication proxy has failed with an error: invalid redirect URI”

Any suggestions would be appreciated.

Is it possible to add a configuration variable for the Server URL? Currently it is set to 127.0.0.1 and you can not change it. Currently I’m changing it in the configuration files themself. But I can’t activate automatic updates for this plugin since I always have to change 127.0.0.1 to my Redis server (docker container).

Is it possible to add a configuration variable for the Server URL? Currently it is set to 127.0.0.1 and you can not change it. Currently I’m changing it in the configuration files themself. But I can’t activate automatic updates for this plugin since I always have to change 127.0.0.1 to my Redis server (docker container).

I’ve done a page with wordpress in a docker in my local computer. Now I want to copy/paste this docker in other computer. In the same directory i have a persistent data for wordpress data and database data. but when I start the docker in the other computer I have an error “error connection with db” and the instalation starts like new.

How can I solve this problem of database? Thanks a lot

I need to merge them. And past my projects inside for testing and development.

The WordPress shows me this?page. I have installed everything regarding points with Docker. However the command “npm run test:php” returns the errors connecting to the database. Files?wp-config.php?and?wp-config-tests.php?are correct.

Please give me a guide about how to make it work.

Thanks

Among other things, we are trying to dockerize wordpress for a client’s website.

We have used the following docker-compose file:

version: '3'
services:
  cosde_wp:
    image: wordpress:6.4.1
    container_name: cosde_wp
    ports:
      - 82:80
    restart: unless-stopped
    environment:
      - WORDPRESS_DB_HOST=ip_db:3306
      - WORDPRESS_DB_USER=user
      - WORDPRESS_DB_PASSWORD=password
      - WORDPRESS_DB_NAME=db_name
    volumes:
      - ./wp-data:/var/www/html:rw

The server running Docker is a Debian 11 Bullseye VM.
The database is hosted on a separate server.

Everything is pretty basic; the container starts, we did the initial settings and created the WordPress user for the client’s external designer who will be creating the actual website.

The designer installed the Elementor plugin, and this is where the problems begin. Every time a page is created or modified, the error “The preview cannot be loaded” appears. I have done some tests and I can create pages and upload images, but it seems that the pages have no formatting. Even after downloading and applying a theme, the pages appear to be unformatted.

If it may be helpful, these are the permissions of the wp-data directory:
drwxr-xr-x 5 www-data www-data 4096 Jan 31 10:32 wp-data

Can someone kindly tell me if there are any specific settings needed to make dockerized WordPress work correctly? Is it necessary to apply specific privileges to the folders inside the container? Or is what happens an error of the Elementor plugin?