• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. T

    Issue Plesk Email Security Pro, money back please!!!

    @Ankebut, Not necessary to respond that way, you are certainly not making friends or giving a good impression of yourself. Let's make a deal - if you stop spamming the Plesk forum with your disgruntlement, then I will stop responding to you and/or providing help when required. However, you...
  2. T

    Issue Single migration works, multiple do not

    @mr-wolf I think that you should focus on the source server, amongst others due to the fact that the pre-migration checks seem to be the bottleneck. Furthermore, it can be the case that the Plesk Obsidian version 18.0.27 (before MU1) caused some hardware damage (disks mostly) and/or caused...
  3. T

    Resolved Obsidian 18.0.27 update

    @Dave W In response to @IgorG's question you responded and the answer to the question of @IgorG should not be "no", but actually "yes" - it follows from your output that strencom based mirrors are used. The "game of patience" -as you called it- is more or less the "patience" required to...
  4. T

    Issue FTP Backup error

    @tizgal This is not the case - the backup is not to be trusted : any restore of backup files is very likely (but not certain) to cause issues. In essence, given the fact that you have updated Plesk Migrator, it should be possible to make a manual backup that can be trusted. In almost...
  5. T

    Issue DrWeb antivirus cannot start

    @Winnstorm Can you check the presence of /lib/systemd/system/drwebd.service - yes, it should be drwebd ! Also, can you give me information about your Plesk version? And which OS do you use? Kind regards..... PS It seems very likely that you run an old image - you should check the Plesk...
  6. T

    Issue Plesk Email Security Pro, money back please!!!

    @Ankebut Your statement is uncalled for and not very polite. Your question is rhetorical - you have entered an agreement with Plesk for a "subscription product" that can be cancelled at any time. Finally, a comment that is more for the general benefit of all forum members (and...
  7. T

    Resolved Fail2Ban bans me(admin) way too often.

    @Korkodilos_ I think that @Arashi is pointing you to the right direction : a connection originating from a (bad) "old style" mail client. At least, that might be one of the most feasible explanations for the log entries in fail2ban.log - nevertheless, you should check /var/log/maillog too...
  8. T

    Resolved Fail2Ban bans me(admin) way too often.

    @Korkodilos_ I just saw that @Arashi already gave you some good advice, please check that out. However, I want to mention the following - you should be able to have Fail2Ban whitelist one specific and static IP. In my humble opinion, it is not good practice to allow the sysadmin (read...
  9. T

    Issue Plesk Email Security Pro, money back please!!!

    @Ankebut, I first want to emphasize that it is not my intention to interfere with this thread - I simply want to make an important point about spam and spam solutions. In essence, you are trying to answer four (separate) questions by providing one simple answer, being "Plesk Email Security...
  10. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @Arashi, @IgorG, Problems should -at least in theory- be solved with the Plesk Obsidian 18.0.27 MU1 patch. I would kindly ask you to make sure that part of the problems solved with the MU1 patch are mentioned in the KB articles and in the forum posts. In addition, please be aware that the...
  11. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @karam Plesk Team released Obsidian 18.0.27, micro-update (MU) 1 - that MU1 should solve almost all of your problems. The biggest problem now is that your old servers are very likely to be flawed to some major or minor extent - it is always good to migrate to new & clean servers. Kind regards!
  12. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @karam This part is correct, to a huge extent. In essence, what you should do -to make your life more easy- is using Plesk Migrator to migrate subscriptions between the old and new (target) server. No manual procedures required, full pre-flight check and very convenient to use - but you...
  13. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @karam A small tip - it is recommended to allocate a new server and migrate all data to the new server, before doing something on the old (problematic) server. After all, the site data is or should not be compromised, the Plesk related (server-wide) data probably is. If you follow this...
  14. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    I suppose the update from Obsidian 18.0.26 to 18.0.27? It is a bit odd, because the issues are not really related to the update - a new fresh Obsidian 18.0.27 installation does not exhibit any problems at all. It becomes even more strange, since the problems are more or less the same when...
  15. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @Arashi Problem seems to have returned with a vengeance. I receive new messages with the text : API call failed: <urlopen error timed out> error: failed to collect system info The problem here is an issue that is very likely related to the firewall, given the facts that - Plesk Panel...
  16. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @karam, There is something odd going on with the firewall......... an important question to you : did you have Plesk Firewall extension installed? I would like to hear that, because it seems to be the case that some script or task is affecting iptables in such a way that it is not in line...
  17. T

    Resolved API call failed: HTTP Error 500: Internal Server Error

    @MicheleB (and @others), Problem might have returned - so keep a good look at your syslog entries. I have had this problem on one server, on the 22th of May 2020. The endresult? A completely wasted Plesk instance........ which instance shuts down randomly ...... and even though all...
  18. T

    Resolved Duplicates in apt

    @IgorG, Actually, that should be deemed "bad design". In essence, the "double" entries can also be removed by setting up a number of dependencies for one of the two packages. I really suggest that Plesk Team removes the "double" entries and creates proper dependencies. After all, there...
  19. T

    Issue ext://one-drive-backup/server: Microsoft OneDrive returns the error: Malware detected

    @Bobbbb It is not recommended at all to use password protected backups for any backup that is encrypted in remote storage, such as OneDrive amongst others. It is not necessary (read: double encryption) and it is dangerous (read: double encryption can compromise files when decrypted). Let's...
  20. T

    A special topic for chatter about Plesk in the Clouds.

    @MarkM, In essence, it is primarily a personal preference - at least, that is a reasonable assumption from my side. I have been running test and production servers on all types of clouds, including the three big ones : GCP (Google), AWS (Amazon) and Azure (Microsoft). The general...
Back
Top