• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Search results

  1. 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...
  2. 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...
  3. 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...
  4. 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...
  5. 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)...
  6. 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...
  7. 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...
  8. 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 ...
  9. 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...
  10. 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....
  11. 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...
  12. 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...
  13. 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...
  14. 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...
  15. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    I can safely say that the above is (and always was) the correct summary of the "objective". The exploits have been always present (and that has been mentioned in the past) and the objective has been partially reached by the Nginx "internal" directive. Listening on localhost would be probably...
  16. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @Peter Debik I am assuming that you are partially responding to me and partially to @mow . The statement is a bit biased - and that is an understatement : you should not test on a normal production server that is hardened in many ways. The whole point of proper testing is to take an...
  17. T

    Input Plesk with Centralized Database

    @AYamshanov As stated before, it is an absolute must that Plesk supports secure MySQL connections. Without that support, any centralized database system or, equivalently, a HA Database cluster, would be rather meaningless and even dangerous! In essence, I am only mentioning some of the...
  18. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @Peter Debik I think that @mow has made some valid points and, at the same time, has urged me to compare the Apache config with Nginx config. I was already aware of the fact that the location ~* xmlrpc.php { deny all; } directive is a bit flawed, given the facts that 1 - it only...
  19. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @mow If I am not mistaken and not reading your post wrongly, then you have a valid point : the Apache config can be simplified and more secure when Nginx is used as a full proxy with sufficient security related config. However, that is the theory that is not really coinciding with practical...
  20. T

    Resolved SECURITY - attack surface : ports 7080 and 7081

    @Peter Debik This is not the correct way or method to reproduce the issue. External "access" is passed on by Nginx by means of the "internal" directive, hence resulting in your conclusion : no connection possible. However, that is a "false positive" conclusion. Please follow the STR...
Back
Top