Search results

I eventually managed to uninstall php8.3-fpm and today the plesk update didn't show any errors. As plesk has its own plesk-php83-fpm package and because the fpm module isn't enabled in my apache so far, I hope my system will be ok again. I found in the apt logs that the automatic update on July...

Jul 31 06:31:45 host-82.plesk.page systemd[1]: Starting php8.3-fpm.service - The PHP 8.3 FastCGI Process Manager... ░░ Subject: A start job for unit php8.3-fpm.service has begun execution ░░ Defined-By: systemd ░░ Support: Enterprise open source support | Ubuntu ░░ ░░ A start job for unit...

# dpkg --configure php-fpm dpkg: dependency problems prevent configuration of php-fpm: php-fpm depends on php8.3-fpm; however: Package php8.3-fpm is not configured yet. dpkg: error processing package php-fpm (--configure): dependency problems - leaving unconfigured Errors were encountered...

Today I did get the error again. Below is the excerpt from the log. I did try all the steps, but nothing helped.

I am on obsidian 18.0.70 and I have configured my server to automatic updates. Since 2 days now, I get an error notification that the update fails. Errors were encountered while processing: php8.3-fpm php-fpm ... Error: An error occurred on attempt to install packages. Attention! Your software...

Thanks for the clarification. I added the appropriate records to my domain registrar DNS and now dmarcian reports everything as set. Alas, my test mails to my gmail account are not rejected anymore but still go into the spam folder. Maybe I need to wait a while until my server's reputation with...

I have 2 domains on my linux vserver with plesk obsidian 18.0.68 Update #2. SPF, DKIM adn DMARC are enabled in the mail server settings and in the domains. I don't have set an external DNS server. So I think, I am very much on the defaults. When I try the dmarcian.com/domain-checker, it shows...

Today, I received an email from expiry@letsencrypt.org about a certificate expiry for my domain. It says "Hello, Your certificate (or certificates) for the names listed below will expire in 19 days (on 2024-05-18)...." When I check my certificate in plesk's SSL-It extension, it shows 2024-05-29...

I found the solution Although Mail - Mail Settings did show the Mail Service as ON (see image), I clicked the Activate/Deactivate Services Button and set Mail Service and Webmail to enabled. Now it works again. To me, this seems to be a bug in the Plesk GUI.

Thanks for the quick reply. # apachectl -t Syntax OK # systemctl reload apache2.service # nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful # systemctl reload nginx # find /var/www/vhosts/system/*/conf |...

Additional Info: I already did a server reboot and I temporarily set the Webmailer to NONE in Mail - Mail Settings for my domains but nothing of it solved the problem.

I have migrated my plesk server to a new host and after everything was up and running, I checked the horde webmailer for my domains. The webmailers did work well. On the Tools & Settings - Webmail Services it says: "If you need to hide a webmail service temporarily, disable it using the button...

@w4systems Great idea, I never thought of this. I am happy with my custom solution, though, as ipsets allow me to swap ip sets for blacklisting easily without touching the other iptables rules at all. (see: plesk firewall 2.1.5-412 still has problems)

Sorry for not being precise enough. I did not mean that a filter for 404 errors should be enabled by default, but should be supplied by Plesk. It is then up to the user to enable it or not. Also, I think crawlers that do not obey pages excluded by a robots.txt should be banned.

Looking at the server logs of my Ubuntu 22.04 system with Plesk obsidian 18.0.56 I found many entries which are not covered by the plesk jails. The most frequent of these are apache 404 and postfix errors. The plesk developers eventually should take a deeper look at server logs and add filters...

I finally managed to get rid of the plesk firewall extension and to use ipset to manage by blacklists. For that I ran an ssh session, copied plesk's initial firewall script and installed the ipset package. cp /opt/psa/var/modules/firewall/firewall-active.sh /usr/local/bin/loadIPtables.sh apt -y...

Oh, I see. But blocking a whole country isn't very helpful. There are cloud hosters located in UK or NL which host servers from all over the world. I use the dialog shown in your link to block specific IPs or IP ranges like e.g. 46.148.40.0/24 which currently does a lot of login scanning. For...

geo-blocking? Where is it? I do not see this anywhere and a Plesk search for it does not reveal anything.

The support did analyze my server and found that a timeout of 150 solves the problem. They stated that the strato vServer seems to be the problem as it reacts very slow on the iptables scripts. During the investigation Pleask supporters also locked out themselves several times. Nevertheless, I...

I currently have an open support call with Plesk support. So far they have confirmed that for some reason it appears that adding any rule clears the firewall chains, and the server becomes unreachable. It happened to them too, when I gave access to my server and I had to restore it again to...