• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by Manfred Beck

  1. M

    Resolved SECURITY information for <server_name>. Problem with defaults entries ; TTY=unknown

    Thank you, I changed the file accordingly and wait a week to see what happens. Btw the .conf file was not touched since 2020.
  2. M

    Resolved SECURITY information for <server_name>. Problem with defaults entries ; TTY=unknown

    Once a week I receive tons of mails with: <server_name> : Dec 12 01:43:20 : <ssh_user_of_domain> : problem with defaults entries ; TTY=unknown ; PWD=/usr/local/psa/admin ; USER=root ; I presume it comes from VirusTotal Website Check, which I tested weeks ago and then switched it off completely...
  3. M

    Resolved How to update the e-mail address which is used for Let's encrypt?

    I have the same issue, Plesk now uses the SSL It! extension, the certificate has my admin email address but renewal reminder mails are also sent to the subscriber's admin account, which causes a lot of requests and troubles. As far as I can remember I deleted a certificate, issued a new one and...
  4. M

    Issue Awstats - No input file specified.

    I have the same issue "no input file specified" running PHP 7.4.30 on Obsidian 18.0.41. Still no solution for this problem available?
  5. M

    Resolved Awstats showing no icons, image file not loaded from /awstats-icon/other/...

    I did all the stuff on the mentioned page before but should have read further down, your solution worked perfectly, thanks!!!
  6. M

    Resolved Awstats showing no icons, image file not loaded from /awstats-icon/other/...

    Where can I modify the alias for /awstats-icon so icons will be displayed in statistics again. I tried Alias /awstats-icon /usr/share/awstats/wwwroot/icon in /var/www/vhosts/system/conf/xxxx/httpd.conf, but this seems not to work. Any suggestions?
  7. M

    Issue Web Statistics SSL/TLS File not found.

    Nobody here with an idea to solve the problem?
  8. M

    Issue Web Statistics SSL/TLS File not found.

    Thanks but setting locale did not solve the problem, *.webstat files still 0 bytes, so AWStats not building files correctly. Alma Linux on schedule
  9. M

    Issue Web Statistics SSL/TLS File not found.

    I am running Plesk Obsidian Version 18.0.41 Update #1, last updated on Feb 9 on CentOS 8.5 All domains set up years ago without certificate now (with certificate) have no more web statistics accessible. /usr/local/psa/admin/bin/statistics --calculate-one --domain-name example.net gives me...
  10. M

    Question Plesk migration with outdated PHP versions

    sorry, too tired from migration, did not see the checkbox, now things should run smootly. Thx
  11. M

    Question Plesk migration with outdated PHP versions

    Unfortunately I can only select PHP 7.4.14 powered by nginx, so html is not executable with this solution. Any suggestions?
  12. M

    Question Plesk migration with outdated PHP versions

    Thank you very much for your reply. I am migrating from CentOS 6.10 to 8.3, so PHP 5.3.3 hopefully should not be an issue, covered by "PHP from OS vendor" component I presume. Then I don't have to change application handler entries in .htaccess files. The entries mentioned abouve were tested...
  13. M

    Question Plesk migration with outdated PHP versions

    I intend to migrate but have a couple of websites on the old machine running PHP 5.3.3, source and target machines have Plesk obsidian installed. Will I have to face problems with the old PHP version? In addition in some .htaccess files application-handler enables html files to be executable...
  14. M

    Issue FastCGI errors in /var/log/sw-cp-server/error_log [error] 9941#0

    stopped Grafana, now I get log entries like: 2020/12/16 15:01:37 [crit] 8037#0: *27 connect() to unix:/var/run/plesk-web-socket/ws.sock failed (13: Permission denied) while connecting to upstream, client: MY-IP, server: , request: "GET /ws HTTP/1.1", upstream...
Back
Top