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

Port 8880 PCI Compliance problem

B

bobthemaster

Guest
Hi,

I have a site on a dedicated server. The server spec is below:

Plesk: 9.0.1
Apache: 2.0.54-10.4
PHP: 5.0.4-10.5
O/S: Linux 2.6.16.27-061216a (FC4)

I'm trying to make it PCI compliant and stuck on a vulnarability. Plesk appears to allow access to the Plesk control panel via port 8880 without being secure (https). This appears to be the case regardless of the domain used, ie.

http://domain-nameA.com:8880/
http://domain-nameB.com:8880/
http://domain-nameC.com:8880/

etc.

I need to redirect port 8880 access to at least a secure (https) connection if possible. Failing that, to block the port but from reading various posting accross the web, Plesk uses port 8880 for things.

Please could some kind soul help me before I loose any more hair.

Thanks
 
I am having the same issue for PCI compliance... I have gotten myself into doo doo though. I was trying to edit the file to see if I could add a redirect to https:// and it broke my login_up.php.... and now I get an error.

I have tried to copy the file from another server, with the same version of plesk and still get the error... did I monkey something up?

Also any help on PCI compliance issue would be great.
 
Back
Top