Recent content by mizar

Hello, Meanwhile, we are published the update 18.0.77.1, which should address the issue with code editor.

Hello, The panel.ini option to control visibility: [mail] smarthost.domain.enabled = false Unfortunately, no way so far. Should be.

Hello, By default Plesk require authentication when relaying even using localhost. You can add 127.0.0.1 and ::1 in Tools&Settings -> Mail Server settings -> White list to disable this requirement. Alternately - switch script to using sendmail or add authentication. Thanks,

Hello, On AlmaLinux 9, Plesk uses postfix from OS vendor repositories. Try to update your OS - it seems you have installed postfix from AlmaLinux 9.6 and openssl from 9.7 (it was updated from 3.2 to 3.5 in AlmaLinux 9.7)

Hello, > Improved the security of mail-account passwords. In some cases, password strength for mail accounts was calculated incorrectly - some weak passwords are estimated as strong. > And also, does the use of Apache Solr require any further manual configuration? Since 18.0.74 we start to...

Hello, Changelog is now available, thanks for the patience.

Hello, It seems you have Atomic repository, which contains conflicting clamav packages. You can either disable this repository before Email Security installation, or blacklist clamav packages from atomic repository.

Hello! It seems you have Plesk Email Security extension, and seems amavis is stopped. Try to start it and examine it's logs via systemctl status amavisd

Hello, The problem with pmmcli is that it uses python module pipes, which marked as deprecated in Debian 13 python, and deprecation warning break structured output, which is expected by this utility. I attach fixed version of the utility compressed by zip. Please unpack and replace...

Hello, The RN entry is a bit misleading, we will update it. Regarding the questions: > Hashing is now the default setting. > This applies not only to new installations, but also to existing ones after updating Plesk. No, it is not default yet. You need to go to Tools & Settings -> Security...

Hello! > Now, as the update has been released, should we revert the manual changes from the command (.../etc/nginx/conf.d/fixssl.conf...)? No, update actually do the same thing - it creates /etc/nginx/conf.d/fixssl.conf with the required directives.

Hi! This error can be caused non-update extensions. May be you have customer extension catalog configured by catalog.url in /usr/local/psa/admin/conf/panel.ini ? If yes, temporary comment the line and run plesk daily UpgradeExtensions. If no, try to compare installed version with version from...

Hi, Should be resolved. Let me know if the problem persists

> Presumably, the weak algorithm issues will still be resolved as part of the 18.0.69 release, as per this previous Plesk post ? Yes, Plesk 18.0.69 will be signed with new GPG key. Please, check the release notes for the details

Hi! We are updating GPG key for signing the repositories to stronger one. As you are on 18.0.68, you need to apply Plesk update using `plesk installer update` command or using UI to import the new GPG key