• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by W4ru

  1. W

    Resolved Extending the storage time for journald log retention does not work.

    It doesn't require any more time to verify. The number of log files is constantly increasing :cool: Excellent, now logging has a function! Many thanks to @Hangover2 ! This issue has now been resolved.
  2. W

    Resolved Extending the storage time for journald log retention does not work.

    Thannk You @Hangover2 ! The command in question returns 100. I have therefore changed the settings, restarted the service, and now there is a need to wait a little while.... I will inform as soon as changes are visible here.
  3. W

    Issue Permission issues after file restoration

    Thank You Peter! My reference was this post: https://support.plesk.com/hc/en-us/articles/12377826206231-Website-hosted-in-Plesk-or-some-sections-of-it-are-inaccessible-403-Forbidden-error-pcfg-openfile-unable-to-check-htaccess-file But I generally prefer 750 here as well.
  4. W

    Question Temporary backup files under /var/lib/psa/dumps/ after restore

    Scenario: The server backups to remote storage via SFTP in 2GB chunks. Total volume of the server backup is 90GB. When I trigger a restore of a larger subscription (40GB in the web root), the necessary files are copied to the server and the restore is performed. After the restore is complete...
  5. W

    Resolved The Monitoring extension reports wrong disk space

    I also had this on one of my servers. Changing the thresholds resulted in a red exclamation mark and two square brackets with no content being displayed. Long error messages like the ones above appeared in the Plesk log. The solution was as described here: Uninstall and reinstall grafana...
  6. W

    Issue Permission issues after file restoration

    I had the same problem yesterday (Plesk Obsidian 18.0.74 Update 2, Ubuntu 24.04.3 LTS). Scenario: Reconstructing the httpdocs folder of a subscription from the server backup. Error 403 was displayed when the website was accessed. The folder owner was correct. plesk filesystem check withplesk...
  7. W

    Resolved Extending the storage time for journald log retention does not work.

    Scenario: I use Warden and like to fine-tune the Amavis log files to further improve my filters. Unfortunately, I only have access to the last four to five days. After doing some research, I made changes that affect journal log retention. cat /etc/systemd/journald.conf [Journal]...
  8. W

    Resolved IPv6 configuration lost across the entire server, reinstallation of IPv6 fails

    I received an automatic reply from Ionos (after sending a scope log file yesterday) and my issue was marked as resolved. Ping6 from server to goole.com and ping6 to the server confirms: all OK like one week ago. I hope to get a little more background information over the phone... It now looks...
  9. W

    Resolved IPv6 configuration lost across the entire server, reinstallation of IPv6 fails

    Correction & addition: I wanted to send for IPv4 and IPv6, but the output above was from a different server... here is the correct output: root@v2:~# ip -6 neigh fe80::1 dev ens192 lladdr 82:01:1e:9d:xx:xx router STALE root@v2:~# ip -4 neigh 10.xxx.xxx.xxx dev ens192 lladdr 82:01:1e:9d:xx:xx...
  10. W

    Resolved IPv6 configuration lost across the entire server, reinstallation of IPv6 fails

    Thanks for your reply! I get the following output: root@mx:~# ip -6 neigh fe80::1 dev ens6 lladdr 82:01:d2:87:xx:xx router REACHABLE root@mx:~# ip -6 neigh fe80::1 dev ens6 lladdr 82:01:d2:87:xx:xx router REACHABLE This would suggest that there may be a different cause in your case. What...
  11. W

    Resolved IPv6 configuration lost across the entire server, reinstallation of IPv6 fails

    I have opened a ticket at IONOS. I will send the details to their support team and post here when I receive feedback from them.
  12. W

    Resolved IPv6 configuration lost across the entire server, reinstallation of IPv6 fails

    The firewall from Plesk was and is not in use. The output is attached I use the firewall in the backend of the V-Server. Identical to what I use on the other servers. This remains unchanged and applies identically to IPv4 and IPv6. But I have considered several times sending a support request...
  13. W

    Question Where on the disk does Plesk store Admin Custom Menu

    Yes, I just checked that specifically. However, system restore is not always effective... Ultimately, I have seen extensions in Plesk for years whose usefulness is rather questionable. Other features (such as automatic light/dark mode switching based on the operating system, which has been...
  14. W

    Question Where on the disk does Plesk store Admin Custom Menu

    It's strange that there is no option for transferring (importing/exporting) custom buttons. However, dumping the database is only half the solution: the stored images would then have to be set up manually. That's where the real work lies. These are located under...
  15. W

    Resolved IPv6 configuration lost across the entire server, reinstallation of IPv6 fails

    Upgrade to Ubuntu 24.04.3 LTS went smoothly. However, status remains unchanged: ping6 google.de from server remains unsuccessful, everything else based on ip4 as well.
Back
Top