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

Question 8443 is indexed in google

Bogdan1

Regular Pleskian
Hi,

Is it a bug or it's on purpose that admin panel( :8443) allows crawlers to index itself?

There is no robots tag or file..
 
Well I think this is not a bug it is up to you..

so if you like to avoid this place the robots.txt in /usr/local/psa/admin/htdocs or /opt/psa/admin/htdocs the path depends on the OS you use
 
Last edited:
Well I think this is not a bug it is up to you..
I beg to (partially) disagree: the admin panel is provided by Plesk "as is" and we (users) are not supposed to patch it in any way (unless directed by Plesk Support to do so, maybe), so I think it is Plesk responsibility to protect those pages with adequate robot.txt and/or "meta" tags (which I don't see in the admin panel pages...)

I have anyway a couple of questions for @Bogdan1:
  • is your a theoretical case, or you have hard evidence of the indexing of the admin panel having happened?

  • what pages have you seen indexed? I hardly can think of anything more than the login page as all other pages should be inaccessible to crawlers as they are (expected to be) password protected

  • I cannot think of any other reason for the indexing of those pages on port 8443 having happened beside the existence of a "normal" (ports 80 or 443) web page of yours having links to them. If that's the case (and I don't think this is a good idea...), it is your responsibility (or at least a "best practice") to protect those links with rel="nofollow" attributes
 
Last edited:
I think that the index is create (and active) for the port 80 or 443 of the server. So, like write Brujo, the location is depended by OS that Bogdan1 use.
Anyway, I think that this isn't so good, so it's a good practice to use robot or any other method to block this access to the root directory of server
 
I think that the index is create (and active) for the port 80 or 443 of the server.
Ouch! Missed that as I use my own template for default domain pages and of course I didn't make the mistake to put a link to the admin panel on those... ;)

P.S.: Then it is sole Plesk responsibility to fix this!
 
Don't see the big deal...

Yes, Google will index both login_up.php and get_password.php on port 8443.

Compare it to Wordpress - you know when you see a Wordpress site, you can access 90% of them by going to wp-admin....
 
Don't see the big deal...
I agree, but nonetheless I think this should be fixed because:
  • It requires a very minor intervention in Plesk code
  • I don't see anything breaking backward compatibility in doing that
  • there is no sense in having the admin panel login page indexed
  • once indexed it would be (marginally...) difficult to get the admin page out of Google and the likes
Compare it to Wordpress ...
don't get me started on that!! :rolleyes:

Cheers!
 
Back
Top