• 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

Recent content by Raul A.

  1. R

    Question Managing Bot/Crawler Attacks on wp-login Across Multiple Plesk Servers - Your Solutions?

    What do you consider a real firewall? Did you try Imunify360?
  2. R

    Question Google Cloud Abuse from their entire IP space and Fail2ban Unable block it

    We also observed high traffic volumes from that huge subnet. The simplest approach is to block it since you don't expect traffic from a different hosting company. In your case, firewall blocking won't help since your firewall will see only Cloudflare IP addresses. You can block in nginx but it...
  3. R

    Issue Template_Exception: nginx: [emerg] duplicate listen options

    Interesting. Taking another look at my /etc/nginx/plesk.conf.d/server.conf, it's exactly the same as yours. If you reconfigure, do you still get the error message? plesk sbin httpdmng --reconfigure-all
  4. R

    Issue Template_Exception: nginx: [emerg] duplicate listen options

    Do you use a custom template? What do you have in: ls /usr/local/psa/admin/conf/templates/
  5. R

    Issue Template_Exception: nginx: [emerg] duplicate listen options

    What is the output of the following? plesk bin server_pref -s | grep ssl
  6. R

    Issue Template_Exception: nginx: [emerg] duplicate listen options

    I ran into a similar issue. In my case, it pointed out that I didn't have TLS1.3 enabled: plesk bin server_pref -s | grep ssl Since ssl-protocols didn't have TLSv1.3, I used: plesk bin server_pref -u -ssl-protocols 'TLSv1.2 TLSv1.3' Afterwards, I reconfigured the webserver and I had HTTP/3...
  7. R

    Question Best practice to migrate

    If you have 2 servers, just perform a migration with Plesk Migration Manager. The restore approach should also work.
  8. R

    Resolved Can not re issue Lets Encrypt SSL Certificat

    The domain DNS zone. Some registrars provide IPv6 by default in the hosted DNS zone. You changed only the A record while you still have AAAA records without having an IPv6 address on your server.
  9. R

    Resolved Can not re issue Lets Encrypt SSL Certificat

    Interesting. Check the User-Agent used by the Let's Encrypt server. In the logs section of the website in Plesk, look for requests to /.well-known/. Please share the requests made while the certificate issue is attempted.
  10. R

    Resolved Can not re issue Lets Encrypt SSL Certificat

    The Let's Encrypt error indicates you have a redirect loop. If you can access https://www.mydomain.com/.well-known/acme-challenge/gyFnutZ4Z6AHoPukt7ReBVgqd9Pkomcmu-0zKF_WKMU Let's Encrypt will also be able to access it. Once an attempt failed the challenge file remains in place. Thus the above...
  11. R

    Issue SSL/TSL error after updating to PLESK Version 18.0.72 Update #2

    Hi, Check /var/log/plesk/panel.log when the error is displayed. It should provide additional information.
  12. R

    Resolved Problem mail (localhost [IPv6:::1])

    Please provide all log entries related to 4577F8B8F9 grep 4577F8B8F9 /var/log/maillog
  13. R

    Question I thought i install LAMP docker image to isolate php version

    Hi, Plesk is set up in such a way that PHP scripts can't reach other webspaces/subscriptions. Along with the symlink protection, it offers good access separation between websites. You can also use CGroups to limit resources per subscription. Using Docker Proxy (can't reach the Docker...
  14. R

    Issue Additional IPs Not Working After Migrating Plesk CT to Proxmox v8 (OVH)

    Hi, Is the additional IP routed via 51.195.xx.xxx/32 by your provider, or is it within the same broadcast domain as the main IP?
Back
Top