Search results

I haven't tried to use the same Redis and different databases for different websites. define( 'WP_REDIS_DATABASE', 0 ); // 0-15

Plesk Migrator 2.26.5-1475 - (22 August 2024) When migrating from AlmaLinux 8.10 to AlmaLinux 8.10, In the "Migration results - overall" We have, [23 Aug 2024 12:05:06] Pre-migration checks Failed to check MySQL InnoDB strict mode. Command execution failed on the source server 'source'...

Thank you! @Sebahat.hadzhi It worked!

@Sebahat.hadzhi do we have an ETA for the official release of this fix?

You should be able use the same container with, define( 'WP_CACHE_KEY_SALT', 'example.com:' ); or define( 'WP_REDIS_PREFIX', 'my-site' ); Please see redis-cache/INSTALL.md at develop · rhubarbgroup/redis-cache I have noticed one issue with this Plugin so far. It FLUSHALL all redis data...

Sorry, I do not understand the above. In this article How to Optimize WordPress with Redis and Docker - Plesk Guide , they have used bitnami/redis. I'm not sure if there is a specif reason to use bitnami/redis. I tried with a #docker run --name=redis --sysctl net.core.somaxconn=511 -p...

The Plesk Support has confirmed the issue.

It seems the issue is with the latest version of the Plesk Migrator. I have a thread for this as well. Issue - Plesk Migrator Database - unhashable type: 'list'

The above error is when attempting to migrate from CentOS 7 to AlmaLinux 8.10. There is a different error when attempting to migrate from AlmaLinux 8.10 to AlmaLinux 8.10 --- Failed to check MySQL InnoDB strict mode. Command execution failed on the source server 'source' (xxx.xxx.xxx.xxx) with...

The second is only if you want to have the redis.conf file on the local disk in root/redis/conf directory. If you do not want to edit redis default configuration, you can simply run the first command. In most case this should be ok.

I'm experiencing database import issue with the Plesk Migrator. Log - --- Failed to copy content of database 'mage2-database' Migration tools tried to perform operation in 3 attempts: unhashable type: 'list' --- Plesk Migrator version is 2.26.4-1467.

If you have Docker Extension installed. You can simply run, #docker run --name=redis --sysctl net.core.somaxconn=511 -p 127.0.0.1:6379:6379 redis If you would like to edit the Redis config file, you can Map it to a local folder. # docker run --name=redis --sysctl net.core.somaxconn=511 -v...

You can configure to see the real IPs. https://support.plesk.com/hc/en-us/articles/12377061126807-Incorrect-IP-addresses-are-logged-by-Plesk-behind-a-Cloudflare-or-Google-Cloud-Load-Balancing

I have had the similar experience. Please see - Question - Wordpress Hacked! Unusual Plesk Behavior

How have you configure the DNS for this (main) domain in the domain registrar?

Just an idea, Did you try to chroot to the mounted volume? #chroot /mountedvol Then, #systemctl stop apparmor && systemctl disable apparmor #exit

Sorry, I didn't mention this in my above post. Please try this. Create this docker via command line. #docker run --network host --name=Wiki requarks/wiki Then the settings. You should be able to connect to local DB without allowing local DB to connect from external connections or the...

I might be wrong.. but the docker instant should be able to access the Local DB without above option or the firewall settings. I have done this before. Did you try both localhost and 127.0.0.1 for the DB settings in your Docker Instant? By the way which docker is this?

What docker is this? Have you tried the CLI? docker run -d -v /path/to/private-key.pem:/app/private-key.pem -e PRIVATE_KEY_FILE=/app/private-key.pem your_image

Thank you Everyone! A warning that firewalld is running when enabling the Plesk Firewall extension would have saved at least 3 hours for me. :D Most of the Almalinux 8 images I have worked with came the firewalld disabled. Unfortunately this hosting company image had the firewalld enabled by...