Search results

213.165.88.236 is blocking your IP address. I was able to telnet to 213.165.88.236:25. Or, you might have a drop policy on the OUTPUT chain without an accept rule: iptables -S OUTPUT -P OUTPUT DROP -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A OUTPUT -p tcp -m tcp ! --tcp-flags...

Try to telnet to the remote server from your Plesk server: telnet mail.targetdomain 25 Do you have IPv6 on your server and a PTR for your IPv6 address? Can you mtr mail.targetdomain?

Sorry about that. I was under the impression you were getting the data from a database. In this case, the MariaDB part is not relevant.

I'm sorry to hear that. Did you try the contact page on the website?

How did you register? At Shopping Cart - SolusVM you have the option to buy a license and start with a 30 day trial. Furthermore, You should contact them directly at Login - SolusVM

Do your connection collation and charset match the database collation and charset? MariaDB [(none)]> SHOW SESSION VARIABLES LIKE 'character\_set\_%'; +--------------------------+---------+ | Variable_name | Value | +--------------------------+---------+ | character_set_client |...

What PHP version are you using? We encountered such an issue when using an old MySQL connector from PHP 5.x.

Yes it is an active product.

You can also set the cron using bin/magento.

Were the indexes removed? What happens if you run the queries again? Did the MariaDB service restart after the above mentioned error?

Unfortunately, emailsecurity database is not part of Plesk daily backups. Plesk daily contains: zgrep -i "^use" /var/lib/psa/dumps/mysql.daily.dump.0.gz USE `psa`; USE `mysql`; USE `horde`; USE `apsc`; USE `roundcubemail`; USE `phpmyadmin`; USE `psa`; USE `mysql`; USE `horde`; USE `apsc`; USE...

You need to recreate the broken index from dns_recs. You can run the following queries to rebuild the indexes: ALTER TABLE `psa`.`dns_recs` DROP PRIMARY KEY, ADD PRIMARY KEY (`id`) USING BTREE; ALTER TABLE `psa`.`dns_recs` DROP INDEX `dns_zone_id`, ADD INDEX `dns_zone_id` (`dns_zone_id`) USING...

Unfortunately, 43896-37639.pph-server.de doesn't resolve to your server IP address. You won't be able to issue a Let's Encrypt certificate for it. You can check with your hoster to fix the domain name, or you can use your own domain name.

43896-37639.pph-server.de doesn't resolve to an IP address. Thus you can't issue a Let's Encrypt for it. Is that the correct address provided for your server?

Please show us what you selected on the Let's Encrypt page.

Do you own PPH-Server.de? DNS domain ownership validation is required for wildcard Let's Encrypt SSL certificates. Plesk can issue wildcard Let's Encrypt certificates for domains that use the Plesk server nameservers. Try issuing a certificate only for 43896-37639.PPH-Server.de.

I suspect you received the extension update. My server received the extension update the next day (we applied the patch on all servers as soon as we were made aware of the issue): # plesk bin action-log --show | grep -i email-security 127.0.0.1 admin [2025-03-13 03:37:16.680] 'Upgrade extension'...

Interesting. When it happens, connect to the database service and check the number of active processes: plesk db "show full processlist;" | cat In the meantime, check if you don't have a small connection limit: plesk db "select @@max_connections; select @@max_user_connections;"

A KB article was published for this issue: https://support.plesk.com/hc/en-us/articles/30609832237591-Unable-to-receive-email-with-Plesk-Email-Security-extension-installed-connect-to-sql-unable-to-connect-to-DSN-DBI-mysql-database-emailsecurity-mysql-socket-var-run-mysqld-mysqld-sock

The first step is to verify that the MariaDB service is working correctly. If it restarts when the 4th Plesk user connects then you need to find out why. MariaDB can support up to 200 concurrent connections at any given time with the default configuration. If you have the time stamp when it...