Search results

Thank you for the update. The status should return if there are any issues detected with the license. According to internal discussion with our team about this case, it could be correlated to an issue with invalid license. It might be a bug, but since it is not possible to replicate it and it is...

Hello, @Colonel36 . Please check /var/log/plesk/panel.log and let us know what errors/warnings are logged there.

Hello, @capps . We have a registered bug with ID PPP-44987 for this issue. At this point, I cannot provide any ETA for the fix. However, the workaround we can suggest is to extract the archive using 7z: You can install 7z by running:

Hello, Raf. As far as I can see, you can configure allow list for the SMTP addresses you are sending from. If that doesn't help, I would recommend reaching out to the external email provider and ask them to clarify why the IP address is greylisted. Apart from changing the IP address, I can't...

Hello, Raf. As far as I can see, you can configure allow list for the SMTP addresses you are sending from. If that doesn't help, I would recommend reaching out to the external email provider and ask them to clarify why the IP address is greylisted. Apart from changing the IP address, I can't...

@brother4 , please also check /var/log/plesk/installer/autoinstaller3.log for any errors logged.

Hey, @Jonathan B . That should be defined in /etc/httpd/conf/plesk.conf.d/server.conf:

Thank you for the update. I consulted with our team again and the other suggestion than connectivity issue is incorrect license. Hence, please execute the following command and let us know what the output is:

Hello, @LTUser . The issue should be sorted in the latest Plesk release - version 18.0.71. Could you please confirm if you are you still experiencing the issue after the update? There is mismatch between the Plesk versions specified in the report title and under "PRODUCT, VERSION", hence, I want...

@Ankebut , I am unable to replicate the issue on a test Ubuntu 24.04 environment. Just to be certain, could you please run the following command and let us know what the output is:

Thank you for the confirmation. Could you please try executing the following commands: This action should recrate the ModSecurity configuration and, hopefully, sort the entry logging issue.

Hello, Vincenzo. There are no known issues with Contabo ongoing in the moment. If you haven't heard from them yet what you can try is to connect to the server with RDP and execute the following command:

We have released an update today which fixes the log display issue. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.71:

We have released an update today which fixes the log display issue. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.71:

We have released an update today which fixes the issue with the predefined access control value. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.71:

We have released an update today which fixes the issue with the permission warnings. If you have automatic updates enabled this update should be installed automatically overnight. Plesk Obsidian 18.0.71:

This issue is related to a bug identified with ID PMT-5634. It has been fixed in version 2.29-1.

At this point, there is no known issue with temporary domains. @shago , can you please provide some more details on the issue you are experiencing? Steps to reproduce and the exact error message you see will be great.

@chris-design , it is still believed the errors result from connectivity issue on Dr.Web's update servers. Can you please try replacing the IP address in the hosts file with another one from the same article?

Hello, @Jonathan B . Is ModSecurity in detection only mode by any chance?