Search results

After i installed Mailman on a plesk Obsidian 18.0.52.1 with litespeed extension, i was able to create mailing lists for domain but cannot access it in order to manage https://domain.com/mailman/admin/test gives "403 Forbidden Access to this resource on the server is denied!" when litespeed...

we got another tracking ID reply from support, The reported error comes from bug with ID EXTLETSENC-1177, which should be fixed for now i just disabled SSLIT cron in order to stop all mails coming in

thanks, asked our plesk license provider about this issue. But is after the plesk update done today.

after plesk updated to 18.0.50 we receive a lots of tickets regarding SSL IT extension Could not secure domains of .............. (login ...................) with Let`s Encrypt certificates. Please log in to Plesk and secure the domains listed below manually. Securing of the following domains...

yes there is /etc/yum.repos.d/epel.repo and with same content as on other plesk server where i managed to do the upgrade

i have the same issue and followed the kb article. grep "exclude=" /etc/yum.repos.d/epel.repo no results grep -rin "exclude=" /etc/yum.repos.d also no results yum update fails This system is receiving updates from CloudLinux Network server. PLESK_18_0_45 extras...

hello Igor i have changed this as you mentioned but now i am facing a new error Plesk Migrator returned non-zero exit code COMMAND: '/usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator' 'generate-migration-list'...

i have a similiar issue, config: Fatal: master: service(config): child 3478411 returned error 83 (Out of memory (service config { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environme> created vim /etc/dovecot/conf.d/99-vsz.conf service imap { vsz_limit = 1 G }...

Username: TITLE plesk installer faild for upgrade PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Product version: Plesk Obsidian 18.0.45.2 OS version: CloudLinux 8.5 x86_64 Build date: 2022/07/22 09:00 Revision: eb4e2a3b37f5171bb9212b7a720f51b9edddefaf PROBLEM...

@IgorG any update for this issue?

Thank you Igor but even after i disable the epel repo. rpm -qa | grep libmodulemd libmodulemd-2.9.4-2.el8.x86_64 yum update libmodulemd Updating Subscription Management repositories. Unable to read consumer identity This system is receiving updates from CloudLinux Network server. Last metadata...

rpm -qa | grep libmodulemd libmodulemd-2.9.4-2.el8.x86_64 and yum update libmodulemd Updating Subscription Management repositories. Unable to read consumer identity This system is receiving updates from CloudLinux Network server. Last metadata expiration check: 1:11:30 ago on Thu 01 Sep 2022...

When upgrading plesk we have this message: No matches found for the following enable plugin patterns: amazon-id It can go further and upgrade is done but there is still another message at the end " Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error...

i thought about it but on what log is mentioned from what ip mails were deleted? so i can show customer that he deleted them.

My client is complaining about mails being deleted after 14 days. Can i see on some logs what ip or device deletes mails?

i also have a similar issue on another plesk server for a website hosted there , certificate is renewed but i still receive failed emails: Could not secure domains of........ (login .....) with Let`s Encrypt certificates. Please log in to Plesk and secure the domains listed below manually...

the ssl is disabled like in solution 2 proposed, but i still receive failed renew for website certificate.

We have more websites that are on our plesk server, some of them have A record elsewhere and we do Let's Encrypt on plesk just for mail and webmail. but we get daily mails like this: Could not secure domains of XXXXX (login XXXXXX) with Let`s Encrypt certificates. Please log in to Plesk and...