• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved ssl_log question?

Richard Follett

Basic Pleskian
can someone please explain these entries?

213.248.211.195 - - [28/May/2017:11:55:24 +0100] "\x15\x03\x03\x00\x02\x02(" 400 166 "-" "-"
213.248.211.193 - - [29/May/2017:03:14:29 +0100] "\x15\x03\x03\x00\x02\x02(" 400 166 "-" "-"
 
also these in the access_log_processed:

47.203.93.185 - - [28/May/2017:23:49:08 +0100] "\x04\x01\x00P\xC0c\xF660\x00" 400 166 "-" "-"
47.203.93.185 - - [28/May/2017:23:49:08 +0100] "\x04\x01\x00P\xC0c\xF660\x00" 400 166 "-" "-"
47.203.93.185 - - [28/May/2017:23:49:09 +0100] "\x05\x01\x00" 400 166 "-" "-"
 
This looks either like a wrong URL call (someone entered non-ASCII characters as a page name) or a hacking attempt by adding a certain URL encoded special character sequence to a URL.

Error code 400 "bad request" means that the data stream sent from a client was malformed. This can be a technical issue of the client or a deliberately sent request by someone who thinks that with a certain byte order he can compromise your server security.

Nothing to worry about, it's not an error on the system.
 
Back
Top