Search results

In the past, I tried, and it worked without any issues.

Hi! I am not sure that I understood the scenario correctly, some real example or screenshots would help. Anyway, I will try to reproduce the scenario how I understood it, To be precise, there are two different domains: one of them "example.com", the second one is "com.next" (or 3rd level...

2678400 (in seconds), it is 31 days.

What about DNSSEC, is it enabled/configured/configured correctly? Try to check with DNSViz | A DNS visualization tool.

Processing the logs for the first time may consume extra server resources. Afterward, the extension will process only changed data every hour. If you kill the process before it finishes the first pass through the logs, the service will try again next time. I would recommend you to decrease the...

To keep you updated. We have found and fixed the issue on the Plesk 360 side, as I said it was false-positive notification and I hope it will not happened again. Thank you for the bug-report one more time, it helped us to find and fix the issue quickly.

A new version of the Log Browser extension has been released, it contain a new feature and a few bug-fixes, Let us know please if you have any feedback!

JFYI. A new version of the Log Browser extension has been released, it also contains a fix for this bug (the bug was registered with id EXTPLESK-5700).

A few minutes ago, a new version of the Log Browser extension was released, it contains fixes to reduce CPU usage and fixes for other known issues. Let us know if it does not help.

A few minutes ago, a new version of the Log Browser extension was released, it contains fixes to reduce CPU usage, and it also provides an additional `panel.ini` option to customize for what period data should be processed (if required).

Thank you for the provided details, It seems the message "server is unsupported" is a false-positive, we continue investigating why it happened. I would like to add that Plesk Obsidian on Debian 10.x is supported. (c) Plesk Lifecycle Policy

Hi @jmar83, could you please provide a little bit more details on where exactly the error/warning/notice was shown? If it possible, could you please attach a screenshot to provide us with a little bit more context?

Thank you for the report. I have filled a bug report, the ID of the issue is EXTPLESK-5713. Let us know if you also know/found steps to reproduce the issue.

If you use FTP, then I do not understand why in the provided logs "22" port is used, it is related to SSH/SFTP, not FTP. FTP uses the 21 port to initiate the first connection to a server.

It depends on how Linux (not Plesk) works with users, id, files, etc. Anyway, it could be changed (have checked on my VM) via reorder records in the `/etc/passwd` file. With `ls -lan` you will see the real ids of owner/group (in my example, it is "example.org_rml0af4imc". After reordering, the...

I think this is because of the difference between "FTP", "FTPS", and "SFTP". sFTP FTP Access to Your Websites (Plesk for Linux) Configuring Passive FTP Mode https://support.plesk.com/hc/en-us/articles/12377599650455-How-to-enable-secure-FTP-FTPS-connections-in-Plesk-for-Linux

I guess you have FTP user(s) in the domain's settings (https://docs.plesk.com/en-US/obsidian/administrator-guide/website-management/ftp-access-to-your-websites/adding-ftp-accounts.65153/); they use the same user_id as a user who owns the file to avoid any permission issues. Based on the logs you...

Thank you @OverWolf, we were able to reproduce the issue and can confirm the bug. Currently, the plan is to fix the bug together with the next release.

As I can see, the bug was fixed in the version 1.8.2, Could you confirm that these errors continue appearing after the upgrade? Could it be you see errors that happened before the upgrade?

Likely, it also should be possible to figure out the used version based on a set of other files and their sizes like html, css, js, etc. Anyway, I understand your question now better, let's wait for other comments.