Recent content by Thomas Wilhelmi

The real solution was to call shadowconfig

Yes, I do have a /etc/psa/.psa.shadow. This file is updated with the Password-Change-Process described in your link. But I still have no entry for psaadm in /etc/shadow

Thx for the reply. But there is no entry at all in /etc/shadow for psaadm. That's why I ask wich password should I set?

Addendum: I See that the user psaadm has no password in "/etc/shadow". In the old system it had. Can this be the reason? And what password should I define there? The admin-Password from Plesk?

Hi, I have a fresh install from Ubuntu 24.04 LTS with Plesk Obsidian 18.0.64. In /various/log/syslog I see for every cronjob for user psaadm this error: In /various/log/auth I see the following line: I really would need some help here. Thx. Best regards

What is the difference between customer and personal domain in your opinion? my first guess is that the 6 personal Domains are part of the 25 and are related to customers in their profile

Did you tried the port 8443?

I made a little more research and found out that DNSSEC is working right after signing and insert the DS-records. I get the following messages in the log: As said: it's working. I cann't find the trabsfer-message to the secondary but probably no issue. Than I restart the named-service and...

Yes, more than once because my issue with "invalid IP address" is also back. But it is also back if I disable DNSSEC. But if it is diasbaled the zone is loaded successfully.

I had a very similiar question and found the answer here.

Hello, I configured DNS with Plesk and it worked like a charme. But than I tried to configure DNSSEC. I followed the intructions in this link: DNSSEC configuration After restart of the DNS-Service the DNSSEC-Zone is not loading. In the Server-Log I find this messages: But nothing said that...

The verion of the extension is 2.0.1-344

Thx, that seems to make the trick. I now still have an issue with apparmor messages but this is another topic and I first try to solve it by myself

@scsa20 I'm using the standardPlesk-Firewall. Not ufw and not firewalld. That is confirmed. So it's iptables. @Peter Debik That is checked and confirmed. I use the latest Plesk version and all extensions are up to date but the IPv6-traffic is vloked if this rule is set to DENY. I switched back...

Even if the reload is done by Plesk, not myself, the error appears