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

Recent content by Rho-Man

  1. R

    Apache Server Directly Public Accessable Via Ports 7080 & 7081

    Thanks for your help Abdi, I worked out how to write the firewall rule to do this for a server with hosts on dedicated IP's. The Nginx proxy_pass works very much like Apache's mod_proxy. The request IP is the proxy_pass IP. Therefore, the firewall rule becomes: Allow incoming from...
  2. R

    Apache Server Directly Public Accessable Via Ports 7080 & 7081

    Thanks. That's way I didn't want to try without more assurance (I don't fully see the IP relationships). Nevertheless, my understanding is that proxy_pass directive sets the address of the proxied server, not the IP from which the request is made. I thought the request from Nginx comes from...
  3. R

    Apache Server Directly Public Accessable Via Ports 7080 & 7081

    Thanks. Actually, my host .conf's read, server { listen 50.23.xxx.xxx:80; ... location / { # IPv6 isn't supported in proxy_pass yet. proxy_pass http://50.23.xxx.xxx:7080; ... and similar for listen on port 443 with proxy pass to host ip on port 7081. Where...
  4. R

    Apache Server Directly Public Accessable Via Ports 7080 & 7081

    Hi, I realize that Nginx passes requests to Apache via ports 7080 and 7081, however why are these ports publicly accessible? Would this still work if I write the firewall rules (for these ports): Allow incoming from 127.0.0.1 Deny incoming from all others I am looking for a way to ensure...
Back
Top