• 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. T

    Plesk and the heartbleed bug/ security vulnerability

    Most likely because they haven't updated OpenSSL. The issue is not a Plesk issue as IgorG points out. It's an issue with OpenSSL.
  2. T

    Plesk upgrade but no Roundcube

    Hate to ask, but is it enabled/installed? Tools & Settings > Updates and Upgrades > Add/Remove Components > Plesk webmails support > Roundcube webmail support
  3. T

    Plesk and the heartbleed bug/ security vulnerability

    You also need to run: service sw-cp-server restart We have a documented upgrade proceedure on our website for those looking to protect Plesk: How to Update Plesk for the Heartbleed Bug
  4. T

    SPAM attack

    I've voted on that months ago. Even if it does become integrated into Plesk there's no telling if it will have full integration with the Panel login vs the services on the server. The filters and jails change according to the flavor of OS and on installed options, logging locations etc...
  5. T

    SPAM attack

    If there's a script that's causing this then identifying that script and stopping it would be top priority. There could have been a customer that had a very insecure password as well that allowed a bot to eventually gain access. I would suggest using something such as Fail2Ban in order to...
  6. T

    Planel does not use the whole certificate chain

    Well if you are using Nginx, which by the way is enabled by default under 11.5+, then you might want to refer to the link that I posted as it's a known issue. The certificates aren't being sent with the CA, which is what you are describing. The reason you got a 400 on the domain you listed is...
  7. T

    Planel does not use the whole certificate chain

    I guess what I'm trying to determine here is if you setup the certificate correctly in the panel. I have multiple Plesk installs and all of them have SSL certificates securing the panels. I haven't seen this issue and I attempted to re-create the issue on a demo box we have and it installed...
  8. T

    Planel does not use the whole certificate chain

    Ok sorry, Let's try this then. nano /usr/local/psa/admin/conf/httpsd.pem make sure that your certificate looks like this -----BEGIN RSA PRIVATE KEY----- (Your Private Key: your_domain_name.key) -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- (Your Primary SSL...
  9. T

    Planel does not use the whole certificate chain

    I think this is a duplicate of: http://forum.parallels.com/showthread.php?289546-NGINX-SSL-needs-to-be-fixed
  10. T

    Firewall configuration changes not applied

    Michele, What version and OS are you using? That version of iptables is from 2006. Are you attempting to track connections of netbios sessions? Seems odd that the module is enabled. If this is something that you didn't intend I would disable it my changing it to: IPTABLES_MODULES="" The...
  11. T

    Firewall configuration changes not applied

    Michele, Is this a virtual machine in a Virtuozzo container? If it is make sure that the firewall in the VZ Control Panel is disabled. Enabling them both will cause neither of them to work. We noticed that this was happening on some of our clients VPS servers in the 11.0 series. If...
  12. T

    NGINX + SSL needs to be fixed.

    If anyone is looking to create a custom template in order to apply the changes to all domains on the account you can do so by visiting our blog post which has more detailed instruction on how to fix this. We also have many other suggestions for PCI compliance on Plesk if anyone is interested...
  13. T

    Turning NGINX on breaks SSL Chain

    The reason his solution works is because it adds the trusted cert which is missing from the configuration. The problem with this approach is multifaceted. 1 - When, and if, Parallels decides to add the trusted cert to the config your server will fail to initialize nginx, which could be in the...
  14. T

    Turning NGINX on breaks SSL Chain

    No it is not fixed yet and I haven't seen any official response from Parallels regarding it either. I wouldn't recommend this because it still doesn't resolve the PCI compliance issues. If you're going to install a certificate with server vulnerabilities then what's the point of having one...
  15. T

    SFTP on Plesk 10?

    Glad it worked for you! The only thing I can think of is the old webspace was upgraded through various versions of plesk and something got messed up along the way.
  16. T

    SFTP on Plesk 10?

    The reason the client session is terminated is because it doesn't see that the userid is in the list allowing it to access the chrooted environment. This is by design and there's nothing in the debug that's surprising. The question is why if you have added permissions for that userid to...
  17. T

    SFTP on Plesk 10?

    Isaac, I'm not asking you how you log into the server I'm asking if you can log into the server via SSH using the username gv? I'm also not asking if you can SFTP using the username gv. Using a SSH terminal can you log in? The same way you would with root. Did you happen to add the user to...
  18. T

    SFTP on Plesk 10?

    Well everything looks correct. It's sometimes hard to diagnose things that aren't on your server because you don't have access to the machine, don't know what has been side-updated etc. Can you try logging in with an SSH Terminal (i.e. Putty) with that username and password and see what...
  19. T

    SFTP on Plesk 10?

    Isaac, Just to double check you do have the follow set correctly right? In the Service Plan on the Hosting Parameters tab SSH access to the server shell under the subscription's system user chose "/bin/bash (chrooted)"
  20. T

    Turning NGINX on breaks SSL Chain

    I have successfully made SSL certs work with nginx and Plesk, but yes it does require the work around. In addition, if you are using a SSL certificate with domain.tld and not www.domain.tld it will fail on many browsers that don't support SNI due to nginx. To be fair this is a limitation with...
Back
Top