Search results

Hello, @jmar83 . There is no built-in option to bypass RBL checks on Plesk. If you are using Postfix, what you can try is to manually configure /etc/postfix/rbl_override according to the following guide...

Hi again, @TorbHo . So, what I said previously is not entirely correct - apologies for misleading you. The PHP version has to be already present on the server and must be packaged by Plesk, i.e. not by the OS vendor. Then, the aforementioned command will install and configure the corresponding...

Hello, @tertek . Kindly submit the request on features.plesk.com . If you can also include particular use-cases in it will be great. Thank you in advance.

Hi, @dijitul . If you have auto-sync enabled, the TXT verification record should be automatically pushed to the Cloudflare DNS zone and the domain validation process for the SSL installation should pass without an issue even for wildcard SSLs. Yes, there's an option that allows you to only...

Hi, @TorbHo . You should be able to install and configure PHP versions (5.6, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0) through the extension itself: plesk ext tuxcare-php --install-configure -version 7.2 I will test that tomorrow to be sure and update you with confirmation.

Hi, @Maarten . Thank you for your input. We recently got a similar feature request and I will add your input as an addition to it for further check. I will follow-up with more details as soon as possible.

Hi, @MCV . I don't think 'statisticsMeasurement' belongs to the psa database. If I am right, it is normal for the repair tool not to detect any issue. Is the same error logged when you execute the maintenance task manually, please? Could you please try plesk daily ExecuteStatistics and confirm...

Hi, @jackk556 Could you please check /var/log/sw-cp-server/error_log and confirm if there are any errors/failures logged? Just for the record, I am able to load the login page on my end. Does the issue occur after you enter the login credentials?

Hi, @Liewebs . If I understand correctly the case has been reported to CloudLinux and addressed by them. Getting in touch with them is typically the right thing to do when the issue involves any of their products. Could you please provide more details on what's the expectation from Plesk...

@rammstein could you please also confirm if you use Dovecot or Courier? Thanks in advance.

Thank you for your input, @J.Wick . The objective is clear. Our team will cerate an internal task to further explore what would be the optimal solution. I will follow-up as soon as there are more details.

Thank you for the report, @rammstein . Unfortunately, I was unable to replicate the described behavior regardless of what I tried (empty IMAP login attempts, non-standard characters, etc.). Just to be sure I have the exact same test environment, is Log browser version 1.9.15-4476? If yes...

Thank you for the update. The ability to secure the mail service with a separate SAN was introduced back in January along with Plesk Obsidian 18.0.67. If you do not use Plesk's mail service and there's no valid DNS record for mail.domain.com, but the "Assign the certificate to the mail...

You can either check the mail logs in /var/log/maillog or if you have the Log Browser extension installed through the Plesk GUI in Tools & Settings > Log Browser > Mail. You can query for the address you are unable to send to.

Hello, @ashley . Is root login permitted on the servers? Please try executing the following command on the source and destination servers: grep -i permitrootlogin /etc/ssh/sshd_config

Thank you for the report, @AmaZili Communication . There are some critical steps and details missed in the report. As in what settings exactly are selected during the Let's Encrypt installation attempt. If you are installing a wildcard SSL have you tried adding the acme_challeange record in the...

Plesk (and most control panels) generally do not send proactive “security advisory” emails to server admins, even when an update contains a security patch. What you can do is to sign up for our Release Notes RSS feed: https://docs.plesk.com/release-notes/obsidian/change-log/rss.xml This way...

Hi, @Sascha Schlüter . While uninstalling/reinstalling the Grafana extension have you also removed the package and cleaned the leftover files as per...

Thank you for the update. Based on the logged entries, I would suggest re-installing Grafana and Monitoring according to the following guide: https://support.plesk.com/hc/en-us/articles/19431741403671-Plesk-Monitoring-thresholds-cannot-be-updated-Request-failed-with-status-code-500

That doesn't sound like a Plesk issue. It seems like the signing key of Collabora's repository is missing. I hope that helps: Collabaora Online public key is not available