• 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 many 403 error for the server ip itself

Gasim Omer

New Pleskian
Hello everyone,

here is my problem :
start real-time monitoring (most of errors ) related to my server ip itself with code (403 ) for one of my sites Logo image (wordpress )

my server ip ( 37.XX.XX.XX )

2018-06-27 11:40:51 Error 37.XX.XX.XX 403 GET /wp-content/uploads/2017/11/logo1.png HTTP/1.0 1.43 K Apache SSL/TLS access


when trying to access the file from browser its exist and work very fine.


i've ( firewall - ip2ban - Web Application Firewall (ModSecurity) ) and one that site ( itheme-security + wordfence ).
 
403 headers can be returned from scripts and with your server IP appearing in the log as it does in your snippet, it sounds like a a script running on the server that is causing that entry to be written . You would likely see a bunch of other requests for this at the same time, all with 403 response codes and your server IP.

Can you check your log and see if that's the case?
 
yes there is other 403 code with ( some) wordpress posts also . only on one site as seen here.

other sites doen't have alot of visits so no error at all .

as google reported today on my console ( Googlebot found an increase in authorisation permission errors on https://www.samesite.com/)
 
Back
Top