• 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 Heppi75

  1. H

    Question Upgrade CentOS 7.9 to Alma Linux python errors

    Yes, I already find this option. But it doesn't work for me, the to_install and to_remove section is maybe ignored? Doesn't make any difference? This are the packages, one epel and the other from plesk ... Installierte Pakete Name : openssl11-libs Architektur : x86_64 Epoche...
  2. H

    Question Upgrade CentOS 7.9 to Alma Linux python errors

    To clarify, there are two conflicting packages: openssl11-libs-1:1.1.1k-3.el7.x86_64 python36-PyYAML-3.13-1.el7.x86_64
  3. H

    Question Upgrade CentOS 7.9 to Alma Linux python errors

    I try to upgrade a plesk server running on CentOS 7.9 to Alma Linux with leapp. But the upgrade breaks each time with the following error. Maybe someone could help me to get rid of this python errors or can explain what is going wrong here? Error: Transaction test error: file...
  4. H

    Issue Unable to start apache

    journalctl outpout: Mai 02 18:43:23 host.mydomain.com systemd[1]: Starting The Apache HTTP Server... -- Subject: Unit httpd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit httpd.service has begun starting up...
  5. H

    Issue Unable to start apache

    Hi, for some reason I couldn't start apache anymore. I am working on CentOS 7.9 with Plesk Obsidian 18.0.43 and the setup with the nginx as reverse proxy. Nginx is started and running an listening on ports 80 and 443. Apache could not be startet, here are some outputs from the error log. [Mon...
  6. H

    Resolved Whitelist email address ends up in spam folder

    It was a sieve problem. I traced the logs of the sieve rules with "sieve_trace_level". That shows in detail what is going on ... - Thank you all for you help.
  7. H

    Resolved Whitelist email address ends up in spam folder

    Here is an additional detail I found in the logs. Mails from the whitelisted domain in my example are processed by dovecot sieve and are moved to spam: sieve: msgid=<msgid.outlook.com>: fileinto action: stored mail into mailbox 'INBOX.Spam' But I don't have a sieve rule, which could be...
  8. H

    Resolved Whitelist email address ends up in spam folder

    Of course the folder in webmail (on the server).
  9. H

    Resolved Whitelist email address ends up in spam folder

    I have an entry on my plesk whitelist spam configuration like *@mywhitelistdomain.com. Here are headers from a current mail that ends up in the spam folder, but shouldn't not be there. What is going wrong? X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on myhost X-Spam-Level...
  10. H

    Resolved Remote Backup failed since update to 18.0.37

    Hi Peter, this saved my day. In my case, on a vsftpd server, it is the option: require_ssl_reuse=NO All is working fine now. Thank you very much!
  11. H

    Resolved Remote Backup failed since update to 18.0.37

    Hi Peter, but it is very strange, before this update the backup to this server was working on both plesk servers without problems. After installing the Update on both servers the backup is not working anymore. We didn't change anything on the backup server? I activated now the FTP logs. Maybe...
  12. H

    Resolved Remote Backup failed since update to 18.0.37

    Sorry, was a little bit to fast with the entry. The command line falls automatic back to a local backup, not stored remote. So the case is still not solved and not working to the remote server!
  13. H

    Resolved Remote Backup failed since update to 18.0.37

    Update: Today I tried the backup via the console command: /usr/local/psa/bin/pleskbackup server -v --ftp-login=ftpuser --ftp-password='password' --ftp-passive-mode This was working as expected and the backup was created on the remote server. But the automatic backup, which was setup in the...
  14. H

    Resolved Remote Backup failed since update to 18.0.37

    Hi, yesterday I made the update on two plesk servers to version 18.0.37. Since this update remote backups to an ftp(s) server are not working anymore. The following message is shown on both servers: Unable to create the remote backup: Transport error: Unable to create the directory...
  15. H

    Question Sysconfig Spamassassin

    Hi, we installed spamassassin version 3.4.4 instead of 3.4.0 on a CentOS 7 machine. All is working fine until we make changes in the plesk admin panel. If we change settings from the spam configuration, plesk is modifying the script /etc/sysconfig/spamassassin and add the --daemonize parameter...
Back
Top