• 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

Search results

  1. M

    Resolved Slave DNS manager do not transfer new domain zone

    Version 18.0.59 fixed this issue.
  2. M

    Resolved Slave DNS manager do not transfer new domain zone

    No. I was greped all logs by new domain name. I think serial is not a problem. It's looks like Slave DNS extension don't send rndc query. On slaves server I don't see any sign about new domain. If my rndc key was wrong I won't update zone manually. It's right?
  3. M

    Resolved Slave DNS manager do not transfer new domain zone

    When I add new domain to Plesk server, DNS zone do not transfer to slave DNS server via Slave DNS manager extension. After manual update in domain DNS settings transfer is completing correctly. Here is full log from adding i manual update.
  4. M

    Issue Can't confirm firewall rules from CLI

    I suppose problem is in nginx check in /usr/local/psa/admin/sbin/modules/firewall/rules script. Try restart nginx before firewall apply and confirm. Chance for correctly confirmation is much more but not 100%. May be very long timeouts counted in minutes should workaround this issue.
  5. M

    Issue Can't confirm firewall rules from CLI

    This solution doesn't work. I have error message:
  6. M

    Issue Can't confirm firewall rules from CLI

    I don't think so is only my bad luck. I have 9 servers with Plesk on CentOS 7, Alma 8 and 9 and all of them with new firewall have this issue. Sometimes firewall reload correctly but I don't know when. I can't reproduce problem with 100% sure.
  7. M

    Issue Can't confirm firewall rules from CLI

    When I try start manually command: /usr/local/psa/admin/sbin/modules//firewall/rules --activate --rules-file /usr/local/psa/tmp/ext-firewall-rules-KhZNmg I have error message: Activation token is absent . This message appears much time before timeout.
  8. M

    Issue Can't confirm firewall rules from CLI

    It's looks like fail2ban doesn't matter. Is any other log except panel.log where I can see what is doing firewall?
  9. M

    Issue Can't confirm firewall rules from CLI

    Yes, timeout do not change anything. I can wait 1 second or 90 second with the same effect. Maybe problem is in another iptables app like fail2ban? What happens when fail2ban add something to firewall before confirmation?
  10. M

    Issue Can't confirm firewall rules from CLI

    I wonder why I have message like this: when in process list is: This process works to timeout from panel.ini. Is it process for firewall activation?
  11. M

    Issue Can't confirm firewall rules from CLI

    As you can see in my first post I already set higher timeout. I would like to note problem exists only in cli.
  12. M

    Issue Can't confirm firewall rules from CLI

    I can't confirm firewall rules from cli after last update. From Plesk interface is ok. As you see I tried rise timeout but this is not change anything. I tried wait 1 second or 60 seconds without success. After apply command nothing in iptables rules was added so nothing was to confirm.
  13. M

    Issue ERROR: pm_Exception: Unable to get server IP.

    Yes. Problem exists only during domain adds. For test I disabled firewall but It doesn't change anything. I wonder why in logs is bad license key message. Slave DNS plugin is checking license everytime I add domain?
  14. M

    Issue ERROR: pm_Exception: Unable to get server IP.

    Problem exists before 18.0.52. I installed this fix. Without it slave DNS manager doesn't work completly.
  15. M

    Issue ERROR: pm_Exception: Unable to get server IP.

    Slave DNS manager do not work when I add new domain. After add I must apply zone manual in DNS settings. Here is panel.log: Logs are in Polish. It's license error message. My license is correct, everything else works good. This is my first installation on Alma 9. The same configuration on...
  16. M

    Forwarded to devs Missing translation strings in English language (en-US)

    I solve this problem. :) Answer is: package-cleanup --cleandupes You can check duplicated packages: plesk sbin pum -c
  17. M

    Forwarded to devs Missing translation strings in English language (en-US)

    Are you solve this problem? I have the same after upgrade from Onyx to Obsidian on CentOS 7.
Back
Top