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

    Issue upgrade to plesk onyx + automatic system updates websites now inaccessible

    - m4 1.4.16-10.el7 from base repo (previous version: 1.4.16-9.el7 from unknown repo) - mailx 12.5-19.el7 from base repo (previous version: 12.5-12.el7_0 from unknown repo) - make 1:3.82-23.el7 from base repo (previous version: 1:3.82-21.el7 from unknown repo) - mesa-libEGL 17.2.3-8.20171019.el7...
  2. A

    Issue upgrade to plesk onyx + automatic system updates websites now inaccessible

    - kmod 20-21.el7 from base repo (previous version: 20-5.el7 from base repo) - kmod-libs 20-21.el7 from base repo (previous version: 14-10.el7 from unknown repo) - kpartx 0.4.9-119.el7 from base repo (previous version: 0.4.9-85.el7 from base repo) - krb5-devel 1.15.1-19.el7 from updates repo...
  3. A

    Issue upgrade to plesk onyx + automatic system updates websites now inaccessible

    Also, here is the list I got in the email this morning about what updates were run automatically and may have caused the issue (?). The following packages were successfully updated: - ImageMagick 6.7.8.9-15.el7_2 from base repo (previous version: 6.7.8.9-10.el7 from base repo) - acl...
  4. A

    Issue upgrade to plesk onyx + automatic system updates websites now inaccessible

    I'm starting a new thread because I realize I was posting in one technically marked as resolved. I upgraded to Plesk Onyx yesterday - everything went smoothly, so it seemed. The system automatically updated this morning and restarted, apparently, because when I got into the office I realized...
  5. A

    Resolved Unable to update Plesk - without error

    in /user/lib/systemd/system there is also no named-chroot.service there is only named.service Edit: note that because of this, there seems to also be no /var/named/chroot folder, which is giving the error in when I run plesk repair dns... I am not sure how to solve this issue, and I'm not sure...
  6. A

    Resolved Unable to update Plesk - without error

    Upon further investigation, I can't even complete the final step of starting named-chroot.service because apparently it does not exist? I tried looking for the file /etc/systemd/system/multi-user.target.wants/named-chroot.service -- and it does not exist. .... I am not sure why? Do I need to...
  7. A

    Resolved Unable to update Plesk - without error

    I looked at this thread but the named.conf line 10 directory says directory "/var/named"; (and not "/var/named/chroot/var")
  8. A

    Resolved Unable to update Plesk - without error

    we don't really have much on the server... available space is 571G (out of 600)
  9. A

    Resolved Unable to update Plesk - without error

    Just tried that, didn't work. Error: Restore the DNS configuration file from '/var/named/chroot/etc/named.conf.default'? [Y/n] Y Restoring the DNS configuration file '/var/named/chroot/etc/named.conf' .............................. [2018-08-01 10:21:37.973] ERR [util_exec]...
  10. A

    Resolved Unable to update Plesk - without error

    Can you tell me how you fixed this issue?: The NS configuration file '/var/named/run-root/etc/named.conf' is absent ............................................................ [ERROR] I am getting the same set of errors. I upgraded Plesk Onyx successfully yesterday, then went home, and when...
  11. A

    Question Nginx - configure service on domain root

    I have Apache Solr running on port 8983 of the domain root (i.e. http://domain:8983/solr/#/), and all I want nginx for is to reverse proxy so I can set up user authentication ONLY for the solr admin console. (I can't do basic authentication directly in the solr files because that then prevents...
  12. A

    Question Setting up a reverse proxy for solr from within Plesk panel

    Will the above work if I'm on a VPS? I need to Reverse Proxy because I still want to be able to access the admin console from anywhere. I don't want it ONLY accessible to a single IP.
  13. A

    Question Setting up a reverse proxy for solr from within Plesk panel

    I don't quite understand - the port 8983 is open for the solr admin console/panel. It works fine. The problem is that this means the whole world can also access it if they just add 8983 to the address. I want to make the admin console secure so the outside world can NOT see it, ever.
  14. A

    Question Setting up a reverse proxy for solr from within Plesk panel

    Hi, I need to set up a reverse proxy for the solr admin console (solr 5.3.1), which is on a separate port (8983) but totally open to the outside world (yikes). I can't just firewall the port or solr basic authentication because a site on port 80 accesses it (php scripts use it search the index)...
  15. A

    Resolved Suddenly started with odd behavior and 401 errors last week

    Well, it's not a huge deal, so I think I won't do anything about it right now. Could you just explain to me where the fullchain.pem could be found?
  16. A

    Resolved Suddenly started with odd behavior and 401 errors last week

    Hi, finally have another chance to work on this issue. I tried the above and not sure why, but it didn't work. First, when I open the downloaded certificate and copy the contents to create an SSL to secure Plesk, it saves it using the domain initially associated with it, and not the one I...
  17. A

    Resolved Suddenly started with odd behavior and 401 errors last week

    I forgot to mention that I did try that - I downloaded and tried to upload the certificate another time. However, when I go to upload I run into this error: "Unable to find the appropriate private key for the certificate." ...I agree that we should eventually upgrade to Onyx. Unfortunately I...
  18. A

    Resolved Suddenly started with odd behavior and 401 errors last week

    Ah ha. That seems be the problem. There are no certificates to choose from besides default (which doesn't work). Are they automatically supposed to be here? (And yes SSL support is enabled in the domains) I see them within the domain hosting settings, so the certificate is there but not in the...
  19. A

    Resolved Suddenly started with odd behavior and 401 errors last week

    I appreciate your help, it fixed the first problem, but I am very confused now. So, we do have a unique domain name, it's the one I mentioned earlier in this thread. I am able to secure that through Let's Encrypt without a problem. It's just the Plesk panel I can't figure out...
  20. A

    Resolved Suddenly started with odd behavior and 401 errors last week

    Thanks for this - just getting to making the change now. Can I ask a follow-up? When you say create a subdomain with "/etc/hostname" do you mean go to "Domains" and choose "Add a subdomain"? It then forces me to add it under the only domain I have on this server... or am I missing a step? Or is...
Back
Top