• 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

    Resolved Website not showing up

    @DigitalSplendid It is NOT recommended to turn off the Web Application Firewall. As an alternative, one could use the (less restrictive) ruleset from Comodo. As another alternative, one could tweak the OWASP rules - not the rules themselves, but add some exclusions, as @Maarten. pointed...
  2. T

    APT ISSUE and PUM ISSUE - Docker public key

    @Plesk Team, Also, please adjust the KB article : https://support.plesk.com/hc/en-us/articles/12377139806359-Plesk-update-fails-GPG-error-The-following-signatures-couldn-t-be-verified-because-the-public-key-is-not-available-NO-PUBKEY The aforementioned KB article is not the recommended way to...
  3. T

    APT ISSUE and PUM ISSUE - Docker public key

    Username: TITLE APT ISSUE and PUM ISSUE - Docker public key PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Product version: Plesk Obsidian 18.0.54.2 OS version: Ubuntu 20.04 x86_64 Build date: 2023/07/28 15:00 Revision: 7addc2cf386263ca7765584cff8c160141fcfd84...
  4. T

    Issue ModSecurity/AtomicCorp: Get rid of "N: Skipping acquire of configured file [...] doesn't support architecture 'i386'" (apt update)

    @King555, The solution provided only is intended to resolve those nasty notifications when running apt-get update or apt-get upgrade. In essence, it is the intention to make sure that updates are applied correctly. However, there are a lot of other issues related to Plesk with Atomicorp...
  5. T

    Issue ModSecurity/AtomicCorp: Get rid of "N: Skipping acquire of configured file [...] doesn't support architecture 'i386'" (apt update)

    @Peter Debik It can be safely assumed that it is the endresult of an orphan entry in /etc/apt/sources.list ...... see my post. In essence, the tortix-common.list file will only yield errors, while the entry in sources.list does not use the "arch=amd64" restriction. Kind regards....
  6. T

    Issue ModSecurity/AtomicCorp: Get rid of "N: Skipping acquire of configured file [...] doesn't support architecture 'i386'" (apt update)

    @King555 I have done some research on this and other "aum related" issues. The issue with respect to apt update can be solved in the following way. The major part of the solution is adding "ARCH=AMD64", but I have also added some explanation and an additional step to add an Apt Keyring...
  7. T

    Issue Synchronize system time (on Ubuntu 20.04)

    @brainforge ( and @Myrlo, @stevendegroote, @Aytalina ) Ubuntu 20.04 LTS uses timedatectl and timesyncd for synchronising time, installed automatically as part of systemd. Stated differently, time is synchronized by default ....... and there is no need to configure synchronization via Plesk...
  8. T

    Resolved nginx protocol options redefined

    @Tim_Wakeling To be honest, I am pretty sure that you only had ONE error. It seems to be the case that you tried to reconfigure domains, but that failed with the nginx -t test. On its turn, the nginx -t test failed, thanks to and only thanks to the Nginx default config files not being in...
  9. T

    Resolved nginx protocol options redefined

    @Tim_Wakeling In essence, it is not about "duplicate directives", even though it can seem like that. I did a quick inspection and it seems to be the case that specific types of default templates (used to generate Nginx config files for different "types of Hosting") are treating ssl...
  10. T

    Resolved nginx protocol options redefined

    @Peter Debik Could you be so kind as to get this https://support.plesk.com/hc/en-us/articles/15476324656151 "support" article offline? It is a completely overengineered "support" article that does not make any sense ....... (fuzzy) scripts, event handlers in order to change Nginx config...
  11. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @Maksim To be honest, the answer to your question is not straightforward, since log output and hence available information is limited to modsec_audit.log entries. Stated differently, with ModSec being on the Apache level, any hit on xmlrpc.php or "altered" xmlrpc.php can be the result of (a)...
  12. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @Anthony With respect to the statement it has to be emphasized that this is not true : the changes to the nginx config files are of such a nature that common and slightly altered requests are still being handled by Nginx, as opposed to blocking handling of requests (as intended by the...
  13. T

    Input Plesk with Centralized Database

    @AYamshanov I have seen the post, but did not have the time to have a good look and/or some time to do some (simple) tests. Nevertheless, it seems like a very welcome addition! By the way, I was wondering how certificate (for secure MySQL) renewals are dealt with - after all, one would not...
  14. T

    Resolved SFTP to Azure issue - EXTPLESK-3418 issue again?

    Is not really relevant. I can recall that I have investigated the topic in a recent past and that the SSH bug was signalled, but also outshadowed by a plethora of articles. It is essentially a "one-cause-many-consequences" issue that has been dealt with / discussed on the "symptom" level ...
  15. T

    Resolved Question to Plesk Backups

    @MartinT As a result of the post of @mow, I have another question : are you perhaps using PhPMyadmin to make changes to the database?!?? In essence, if the server runs (properly or not so properly), then admin@localhost (and root@localhost) are working and admin should be specificied in the...
  16. T

    Resolved Question to Plesk Backups

    @MartinT This caught my eye : and the question is : why? There is no need at all to mess with the database in order to do something with Nginx. Kind regards....
  17. T

    Resolved SFTP to Azure issue - EXTPLESK-3418 issue again?

    Peter, The limitations of Azure are well-known, but this is a bug that is not related to Azure limitations. It is all related to a well-known bug in SSH ....... and it is an issue on the client-side (Plesk) and not on the server-side (Azure, AWS etc). In most cases, this bug can be worked...
  18. T

    Issue Unable to make updates (Plesk Obsidian 18.0.51 on Ubuntu 18.04.5)

    @Vendito24 Solution has been given in : PUM Failure You only need to change contents of file /etc/apt/sources.list.d/plesk-ext-kaspersky-av.list to : deb [arch=amd64 signed-by=/etc/apt/keyrings/plesk.gpg] "http://autoinstall.plesk.com/KAV_8.5.1" bionic all without the " and " in the line...
  19. T

    WP Toolkit - Product News

    @custer I have been probably missing some of the new developments with respect to WPT, but is there any support for the wc cli (WooCommerce command line) utility that normally is supported by the wp cli (WordPress command line) utility? I could not find that in the release notes - after a very...
  20. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @Peter Debik Bypassing Nginx is sometimes desirable for specific applications and even necessary for certain old-skool applications. Nevertheless, a "necessity" is less and less prominent and a "desirability" is often an answer to the wrong question : one can always add some custom Nginx...
Back
Top