In this guide, the so-called server has been invaded or hacked means that unauthorized people or programs log in to the server for their own purposes and use its computing resources, which usually has a bad impact. Disclaimer: If your server is invaded by a state organ like NSA or a criminal group, you will not notice any problems, and these technologies cannot detect their existence. However, most of the compromised servers are intruded by programs like automatic attack programs or cheap attackers like "script kids", as well as stupid criminals. Such attackers will abuse server resources while accessing the server, and seldom take measures to hide what they are doing
Read on →
Problem details: 'Mixed Content: The page at' XXXX 'was loaded over HTTPS, but requested in secureXMLHttpRequest endpoint' XXXX ' Thisrequesthasbeenblocked; thecontentmustbeservedoverHTTPS.’ The reason is that the current website is the interaction mode of HTTPS protocol, but HTTP appears on the page
Read on →
1. Modify the/etc/hosts. deny file. The command is as follows: sudovi/etc/hosts. deny 2. Rules for writing content: # Deny specifying IPsshd: 127.0.0.1 # Deny IP segment (wildcard symbol '.') sshd: 127.0.0
Read on →
The command is as follows: tail-10000/nginx_log_path. log | awk vFS='|' '{print $2}' | sort | uniq-c | sort-k1-nr | head-n20
Read on →
If the server uses Nginx and CDN is nested upstream, it is inevitable to encounter a problem: "CDNIP is recorded in the request log instead of the actual request IP". As we all know, this is not conducive to website management, or it is difficult to avoid some malicious risks. It is not complicated to solve this problem. Just add the following configuration to the Http section of Nginx: set_real_ip_from0.0.0.0/0; real_ip_headerX-Forwarded-For; Take the pagoda panel as an example. In the "Software Store>Installed>Ngin..."
Read on →
