Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Remove php and plesk panel info
- Thread starter bulent
- Start date
bulent
Regular Pleskian
@trialotto
there are extensions like Wappalyzer for Firefox or Chrome an with this extension is possible to see some info for the web server, used cms, php version info, used panel info and so on.
Will it be possible to hide php version info and plesk panel info?
Regards
there are extensions like Wappalyzer for Firefox or Chrome an with this extension is possible to see some info for the web server, used cms, php version info, used panel info and so on.
Will it be possible to hide php version info and plesk panel info?
Regards
@bulent,
Yes, it is possible, but the question whether it is wise or even necessary to do so.
Consider, for instance, the identification of Plesk: Wappalyzer identifies
- Plesk Panel by analyzing the URL: scripts, icons etc.
- Plesk driven sites by analyzing the headers: "Powered by PleskLin" or "Powered by Plesk"
that is, if I am not mistaken, since it has been a while since I tackled this extension.
So, changing the default Nginx template or creating a custom Nginx template without the before mentioned headers would or could do the trick.
With respect to the php information, I believe to recall that it was as simple as introducing expose_php=off in the php.ini file.
In short, you can try both for a particular domain.
Please let me and all of us know whether this actually solved your problem and/or answered your question.
Regards......
PS Forgot the following: when testing the before mentioned "solution", clear and/or bypass browser cache, otherwise you will get "old" results that are stored in cache!
Yes, it is possible, but the question whether it is wise or even necessary to do so.
Consider, for instance, the identification of Plesk: Wappalyzer identifies
- Plesk Panel by analyzing the URL: scripts, icons etc.
- Plesk driven sites by analyzing the headers: "Powered by PleskLin" or "Powered by Plesk"
that is, if I am not mistaken, since it has been a while since I tackled this extension.
So, changing the default Nginx template or creating a custom Nginx template without the before mentioned headers would or could do the trick.
With respect to the php information, I believe to recall that it was as simple as introducing expose_php=off in the php.ini file.
In short, you can try both for a particular domain.
Please let me and all of us know whether this actually solved your problem and/or answered your question.
Regards......
PS Forgot the following: when testing the before mentioned "solution", clear and/or bypass browser cache, otherwise you will get "old" results that are stored in cache!
bulent
Regular Pleskian
@trialotto
Yepp,
I have added expose_php=off to global php ini and it removed php version info.
Probably I will leave the nginx template files, I don't want ot modify them
Thank's
Yepp,
I have added expose_php=off to global php ini and it removed php version info.
Probably I will leave the nginx template files, I don't want ot modify them
Thank's
bulent
Regular Pleskian
@trialotto
I can't say there is sensitive data.Just if there is option to hide, it's better to hide, that's all.
Regards
I can't say there is sensitive data.Just if there is option to hide, it's better to hide, that's all.
Regards
@bulent
Ok, clear and confirmed.
I get the idea that extensions like Wappalyzer are annoying and give a hint to what is used (and can be attacked), but Plesk is fairly well-protected against this kind of extensions.
I will have a look at the question whether it is better to "hide information" (even insensitive data), from a security´s point of view.
Keep you posted!
Regards.....
Ok, clear and confirmed.
I get the idea that extensions like Wappalyzer are annoying and give a hint to what is used (and can be attacked), but Plesk is fairly well-protected against this kind of extensions.
I will have a look at the question whether it is better to "hide information" (even insensitive data), from a security´s point of view.
Keep you posted!
Regards.....
Similar threads
