• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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