• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue pp-nginx fails to install

Sid

New Pleskian
Ive just tried to install the release version of Plesk Onyx and when I do a "vzpkg update cache centos-7-x86_64" I get:

# vzpkg update cache centos-7-x86_64
Update OS template cache for centos-7-x86_64 template
Loaded plugins: rpm2vzrpm
Cleaning repos: pp-nginx0
0 metadata files removed
0 sqlite files removed
0 metadata files removed
Loaded plugins: rpm2vzrpm
http://autoinstall.plesk.com/NGINX/dist-rpm-CentOS-7-x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.


One of the configured repositories failed (pp-nginx0),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:


Anyone else hitting this?
 
Yep, I followed that KB, that's where the error comes from :)

Anyway I logged a support ticket (my first one!) and it's a fault in the installer and you guys have now fixed it in our systems, I'm sure an update will come out shortly.

Thx

Sid
 
Back
Top