Icons Not Loading in Elementor Pro After Restoring WordPress Site from Backup on Docker Desktop Win11

Docker Desktop
,
1

Hi everyone!

I have encountered another problem with WordPress. Earlier, I was developing a website using XAMPP (with modified and updated modules, of course). Then I decided to switch to Docker because it’s much faster and more convenient to use. But unfortunately, its usage requires more experience than I have right now.

What I did:

1. Created a new container with a .yml config file.
2. Used the Updraft plugin to restore the website from a backup.

Here is the compose.yml file:

version: '3.8'

services:
  db4:
    image: mysql
    environment:
      MYSQL_DATABASE: wordpress_db_4
      MYSQL_USER: db_user_4
      MYSQL_PASSWORD: db_user_pass_4
      MYSQL_ROOT_PASSWORD: securepassword_4
    volumes:
      - db4:/var/lib/mysql

  wordpress4:
    image: wordpress:6.9.0-php8.5-apache
    ports:
      - 8084:80
    environment:
      WORDPRESS_DB_HOST: db4
      WORDPRESS_DB_NAME: wordpress_db_4
      WORDPRESS_DB_USER: db_user_4
      WORDPRESS_DB_PASSWORD: db_user_pass_4
    volumes:
      - wordpress4:/var/www/html

volumes:
  wordpress4:
  db4:

Now, about the problems I’ve encountered:

1. None of the custom icon sets that I previously uploaded on Elementor Pro are being loaded or shown after restoring the website. I suspect the problem is related to read/write file permissions, but none of the methods I tried from ChatGPT helped me solve the issue.

That’s what I see when the restore via Updraft is done:

image_2026-01-30_021641660
image_2026-01-30_0216416601545×1131 36.4 KB

2. However, if I upload a new icon set to Elementor Pro, it uploads without any issues and is also visible on the page.

3. WP Rocket keeps showing the following message:

**WP Rocket** cannot configure itself due to missing writing permissions.
Affected file/folder: `wp-config.php`

The following code should have been written to this file:

define( 'WP_CACHE', true ); // Added by WP Rocket

Screenshot:

Screenshot 2026-01-30 163355
Screenshot 2026-01-30 163355723×470 25.1 KB

But his issue is easily fixed by changing the ownership of the wp-config.php file to www-data by applying the following command:

chown www-data:www-data /var/www/html/wp-config.php

However, I’m not sure if it won’t brake anything on the same time :smiley:

Based on what I’ve described above, I have some questions:

Has anyone faced similar problems to mine? Before I perform a full restore from the backup, is there any procedure I need to follow to ensure that all directories and files have the proper read/write permissions?

Is there maybe some universal command I can run in the terminal to assign general access rights to all files so that everything works without problems and restrictions? For example, with XAMPP, everything worked perfectly out of the box, the only issue with it was that it was slow. If it weren’t for that, I would have continued working with XAMPP.

Thanks in advance!

2

If you encounter issues with a Docker container, then it would be helpful to share your container config (compose.yml or docker run command, and Dockerfile if used).

1 Like
3

Thanks for your reply! I have added it to the original post :slightly_smiling_face:

4

Does updraft restore the icons outside Docker? I have used updraft for backups, but never had to restore :wink:

6

Well, it restores everything within the WordPress files and the DB. With XAMPP and VPS hosting, I’ve never had problems like that. Therefore, I decided to post a question in this community. I thought that maybe this is a common issue :smiling_face_with_tear:

7

rimelek

Hi there! Maybe you know what’s going on here? =)

Thanks in advance!

8

No, I don’t know.I don’t know updraft either and I don’t know if that is recommended to use in a container or not. You could also try the wordpress community. As a Docker community here, we can help with Docker related issues, but just because something is running in containers, doesn’t always mean the cause of the issue is the container even if everything worked with XAMPP before. There can be many difference between two environments.

I can share commands you can use to check files inside the container, but as you mentioned chown, I assume you already know about docker exec. You would also need to check server logs. I assume you had to do that sometimes with XAMPP as well. PHP and Apache HTTPD can have logs s well.That shows if the issue is about file permissions or missing files. You can check if the files are there on the filesystem, or not.

In the browser, you ca check the developer console (F12 usually on keyboard), go to network tab, refresh the page and se the status of the icons or any file that should be loaded. You can also inspect the HTML if ther eis any difference. If you have never done it, it could be difficult first, but it is worth learning about it.

If you need a wild guess, I would sy the backup plugin had no access to files responsible for the icons, so they were not backed up, which lead to that it was not able to restore the files. You could confirm it by doing a backup on Xampp and also with Dcoker. Than compare th too and see what kind of files are missing if any from the backup made in Docker. If that is the problem, we can think about why it happens in a container.

Unfortunately, using containers don’t solve all our problems. It solves some and can cause others, so being able to debug is important and only small part of that is Docker-related. The rest is general Linux, Web and application debugging. In this case, the wordpress community can help you better with the application part.

PS: If you want to meniton someone to notify them, you can use @username. Linking my profile will not notify me, I just noticed an unread topic.

9

@rimelek thanks for the reply again!

I’ve already figured it out. It was a vpn problem. Already solved! =)

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.