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

    Input Cloudflare Whitelist Scripts for Fail2ban and NGINX

    Since first using the script to add Cloudflare IPs to the ignore list, fail2ban was ignoring ALL ips. The problem is here: cat $LOCALIPSV4 $LOCALIPSV6 > cloudflare-ips.txt If the ipv4 list from Cloudflare doesn't end with a newline, you end up with something like...
  2. J

    Input Cloudflare Whitelist Scripts for Fail2ban and NGINX

    Thanks for sharing this. I made a small change so that each IP added has a description: #!/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin # The goal of this script is to download and check the current list of Cloudflare IP-addresses and prepare a script that will add them to the Plesk Fail2ban...
  3. J

    Resolved Docker Proxy Rules - Getting 404 on the URL set

    Plesk's customer service helped out on this one, I just wanted to share in case anyone came across this in the future. From Taras @ Plesk: When the proxy rule is created for the domain's root the requests for the domain's root are proxied to the application's root in the container. Thus...
  4. J

    Resolved Docker Proxy Rules - Getting 404 on the URL set

    I have this partially working using a custom nginx directive, but something is still not right and I don't know what... # Custom docker reverse proxy settings begin location /portainer/ { proxy_http_version 1.1; proxy_set_header Connection ""; proxy_pass http://0.0.0.0:39000/; }...
  5. J

    Resolved Docker Proxy Rules - Getting 404 on the URL set

    I have a Docker container set up and running (Portainer). I set the port mapping to manual, 9000 to 39000. The service is available and running at domain.com:39000 I went to: Domain> Docker Proxy Rules I added a rule using these settings: URL: domain.com/portainer Container: portainer Port...
Back
Top