Search results

@Sebahat.hadzhi Thank you for your reply and the good news. I can confirm that the repository is working fine again.

Hello and sorry for the late reply. I haven't been notified by email despite having checked that option. Don't know if it's been filtered as spam. Now back to the problem. @Maarten Thank you very much for the suggestion. I haven't tried that but could of course change the repo to the archive. I...

Username: TITLE Repository for PHP 7.2 missing PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Onyx 17.5, CentOS 7.9, Intel x86_64 PROBLEM DESCRIPTION Since 6 November 2024 we're getting the following error from the Plesk Update Manager: STEPS TO REPRODUCE Wait for...

@Peter Debik Thanks, your last suggestion worked! I hope that the rollout of the faulty update of DrWeb has been stopped.

We haven't received those warnings for a while now, too. At the moment, everything seems to be fine again.

@Peter Debik Thanks for the explanation. But @Strangelove wrote: So he must have had access to the registered bug. Otherwise he wouldn't know about those details. That's why I was wondering about it. But maybe @Strangelove is the author of the bug report and that's why he knows about its...

@Strangelove Thank you. I'm not sure how you checked the registered bug. Is it accessible to the public somehow?

@Peter Debik Thank you for the information. Interestingly, we haven't created any custom logrotate rules nor did we manually delete the corresponding report files. As I already said above, the cleanup routines should be made more robust. A simple check for the existence of the report file would...

@trialotto Thank you for chiming in. rkhunter is working normally on our servers. We always get weekly reports, so I am sure it works correctly. I don't think the problem is with rkhunter being outdated (it is, I know), but due to a problem with the clean-up routines of watchdog. As the OP...

@Peter Debik: I don't think functionality is impacted. But I agree, the thread owner should create a bug report.

We are noticing this too on all our CentOS 7.9 servers with Plesk version 18.0.49 Update #2. Not sure if Watchdog still works as intended.

@Kaspar Thank you very much. Finally, the developers could reproduce the bug and confirmed its existence. I'm looking forward to the fix.

@IgorG As I already noted we cannot give access to our servers to external service providers (company policy). And I don't think this is necessary either, because Kaspar (see post #16) could reproduce it in a DigitalOcean droplet (fresh install). Follow his detailed steps and you will be able to...

@Kaspar Thank you for chiming in. Yes, that's exactly the problem we are observing. And it is of course reproducible.

@IgorG When I said "SPF enabled", I meant the DNS setting (TXT SPF record). This is important, because otherwise the problem does not occur. If your developers had that record for all domains, I'm not sure why they weren't able to reproduce the problem. BC108 (post #3) described the root cause...

@IgorG I can assure you that the problem is reproducible on a clean installation of Plesk. Unfortunately, we cannot give access to our servers to external service providers (company policy). Did your developers pay attention to my small correction in post #2 (Forwarded to devs - SPF_FAIL for...

@DaarGaJeDan No, your problem seems to be different from the problem described in this thread. The problem in this thread only occurs for internal forwards, not for regular emails to external email addresses.

That's unfortunate, because the problem is reproducible on all our Plesk servers (current version). The option "Fix incorrectly set sender for outgoing mail" is not enabled on any of our servers. So that can't be the reason for the problem. Also, Plesk doesn't add an "envelope" header, but...

@Peter Debik: Yes, but this wasn't the case when I wrote my message. The tag has been added only after I posted my preceeding message. But thank you for informing me about this change.

No answer from the Plesk team and no other news so far? Why hasn't this confirmed report been forwarded to the dev team?