| Server IP : 121.121.20.254 / Your IP : 216.73.216.142 Web Server : Microsoft-IIS/10.0 System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64 User : IUSR ( 0) PHP Version : 8.3.28 Disable Function : NONE MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/inetpub/wwwroot/KnowledgeBase/wp-content/languages/plugins/ |
Upload File : |
�� G T �$ �0 & �0 1
1 1 1 &1 i X1 �1 { �1 � ^2 �2 3 Y 3 ( j3 �3 - �3 q �3 f J4 6 �4 � �4 � �5 � r6 7 & 7 ;7 M7 _7 D q7 ? �7 � �7 � �9 � �; , �= V �= � )> � �> � l? � �? / �@ � �@ > �A � B � �B � ]C [ /D � �D b ?E �E �E �E ' �E , �E F #F )F 5F MF
dF oF + xF H �F
�F �F G G 7 &G � ^G � .H # I C =I 0 �I � �I � MJ � �J � �K � eL � M � �M � |N O O
O 3 ,O ; `O �O �O
�O . �O \ �O F VP �P . �P �P �P 4 �P 4Q SQ `Q D qQ �Q 2 �Q R R R � $R � �R �U �U �U �U �U �U �U
V l V h V H �V
1W ?W EW LW UW oW yW E �W �W
�W �W G X 4 HX 5 }X �X �X �X �X �X Y Y $Y 4Y
EY SY XY sY
yY �Y �Y �Y �Y �Y �Y U �Y =Z YZ J mZ � �Z � D[ � �[ O\ M f\ �\ K �\ ] M -] {] B �] �] - �] ! ^ q )^
�^ M �^
�^ _ _
,_ 7_ I_ $ ^_ �_ �_ �_ �_ �_
�_ 5 �_ L ` L h` 6 �` p �` ]b cb ub |b �b �b �b �b �b �b �b �b
c c 'c " Dc gc qc {c �c " �c � �c �d �d �d �d
�d 2 �d e M 4e E �e �e �e �e f f )f Bf Rf af nf �f �f �f 6 �f
g g g 1g Og Yg _g |g �g �g
�g T �g h (h 9h
Oh ]h U jh �h �h
�h � �h �i > �i
�i �i j j /j 8j Lj _j
ij
tj j $ �j �j �j �j �j f �j Ak ]k yk k �k �k C �k , �k $l -l - 4l bl jl h �l �l �l m
.m & <m cm ? pm d �m n n "n 3n Hn bn
nn yn ' �n �n �n �n �n
�n �n
o o 2o W >o � �o M p | fp �p � �p X �q
Kr Yr ]r er rr I �r Z �r ,s 5s Ms Ys `s ( vs ^ �s �s t
t G *t d rt �t
�t �t �t u u u $u 6u Mu Ru _u ku zu �u �u �u �u �u �u v (v @v Lv Uv ov xv �v
�v �v
�v �v f �v :w Nw Ww hw |w �w �w �w = �w �w x /x Nx jx
�x �x �x �x �x �x �x
�x � �x � �y � z M �z
{ ' *{ * R{ H }{ �{ @ �{ $ (| - M| " {| g �| h } F o} � �} g~ � �~ 2 � B � � B ,� N o� Y �� p � h �� Z � p M� a �� � f <� l �� } � v �� f � a l� � Ά U S� [ �� \ � c b� H ƈ � = +� - i� � �� ^ (� H �� B Њ � � l �� � , � � E� l � ? Y� " �� * �� c � h K� u �� d *� h �� h �� j a� � ̑ k� W �� � � # x� % �� G � M )� H w� 8 �� �� E � � W� ܕ � W � g C� � �� F� [� h� r� � �� >� C� � G� > � N 3� P �� 4 ә � � 6 �� , � � � � �
� w �� � � � �� V U� � �� U� ]� " ~� �� ߠ @ � 2 0� c� h� u� �� �� �� �� ! ϡ
� �� � \ � l� y� �� �� �� �� ̢ �
� �� � � D � , d� 3 �� # ţ ' � � )� E E� I �� ե � � � (� 7� + ?� k� �� � �� @ � B M� ! �� M �� # � Y $� ~� " �� " �� ' � 6 � ?� K� _� |� �� �� �� © ک % � u � �� �� �� � ' � 0 � M� W� f� 4 v� M �� �� 6 � N N� �� �� K �� � � ' +� ^ S� V �� 0 � � :� � ű n t� � � � � ,� A A� A �� � ų � w� _ �� * [� K �� ~ Ҹ � Q� ` �� � V� ! �� � !� / �� � � � x� �
� A �� � �� \ ��
� �� � � ' 0� X� e� o� �� �� �� �� $ ÿ E � .� ;� P� ]� < p� � �� � H� " � 4 $� $ Y� � ~� � � � �� � 2� � �� � \� � �� p ��
� � � 0 1� - b� �� �� �� * �� N �� < 1� n� 0 {� �� �� 6 �� � (� 8� : E� �� - �� �� �� �� � �� ! �� �� �� �� �� �� � � $� c 7� _ �� E �� A� N� U� \� c� v� �� 3 �� �� �� �� J �� 0 :� 3 k� �� �� �� �� �� �� �� � � (� 5� <� [� b� q� �� �� �� �� �� B �� � )� L ?� s �� q � s r� �� V � Z� S v� �� U �� =� = N� �� 2 �� �� } �� c� A j� �� �� �� �� �� � $ � >� E� X� h� �� �� = �� B �� B !� - d� ` �� �� �� � � %� 2� P� ]� r� y� �� �� �� �� ! �� ' �� � #� -� :� " S� � v� C� M� W� a� q� > {� �� D �� A � W� d� �� �� �� �� �� �� �� # � )� <� - U� 9 �� �� �� �� ��
� � � 7� V� u� x� N �� �� �� �� � � B )� l� y� �� � �� b� 3 o� �� �� �� �� �� �� � � ,� 9� F� $ P� u� |� �� �� T �� ' �� ' � H� O� U� b� < i� 0 �� �� �� - �� � #� l 6� �� �� �� �� ! �� � ) !� r K� �� �� �� �� �� � � %� $ 8� ]� p� w� �� �� �� �� �� �� @ �� n � @ �� q �� :� � O� N C� �� �� �� �� �� B �� W � j� s� �� �� �� - �� ^ �� =� M� Z� 3 g� Z �� �� �
� � .� 5� 9� M� ]� y� �� �� �� �� �� �� �� � � 2� K� d� }� �� �� �� �� �� �� �� �� �� l � u� �� �� �� �� �� �� �� 3 � D� ]� w� �� �� �� �� �� �� �� � � � &� w �� ~ � P �� �� '
� ! 2� A T� ' �� > �� ' �� - %� S� ` r� ` �� 9 4� � n� r � { y� �� ( � 6 4�
k� B v� C �� ? �� ` =� N �� ? � c -� G �� � M � \ @� d �� q � Q t� M � e � z� ' �� ! � $ � 8 � B� ? Y� $ �� } �� O <� 0 �� 3 �� x � Z j� � ' � � � J �� ' �
$ T E ^ � [ � Q U U � U � N S 6 � � R � r H ! � � � 3 . 7 b - � � E � { ! � � B � ` � � R � � � � � � � 3 4 = h = � - � �
- �
' �
� �
� � t � v
� �
� K � u � W ^ % } � � � > � 3 ' [ b o � � � � ! � � � ] l � � �
� � � � : ( * c < � ! � � ! . W M & � � � � , ) 4
^ l j p 3 � C S = l � N � % ! > ` 3 � � � � 5 M 9 b \ � � 1 R � � c A $ � � � K P � � � � � " � [ ] � u � p
& � , � 3 � v * � s � /
� B W % � � f � � 0 � E � � � d % A ( � � n > � 5 a � � � Z � � h � . � 9 q � L T o ` 6 � � � . � & � , � � ] � � 8 f � � � � _ � b S B � F ? [ ; � G
� � � w � r � K k l H � � � � � & � e � � � * D � g � o � v � H d ! � j 4 7
t � 5 � � : � D C � � : � � � � = O � � s � � w � z � � � h � � � U { � ) G � k � < � P T � u � � � 1 � � � � $ Y � � J � 1 � � Q Q � � � @ x X . C � � � � � E � t � R
� � � + N � l � O < � � � � E = @ A 8 F } } � \ � z � � 5 � i 2 { � 2 a � � � � � F � � � � � ; � � � * > ! Y ) ; � 7 - � + 9 B @ / e � � ~ > � � 0 g � y 8 � � � m � � L � � � ( : � ^ U � � 6 � � � " � � 9 � � I � | � y � � % � � � � = � � V / # � � M ' � � � _ � � i � � ( 3 - � � � � � ` � j \ q � � 4 � I � + G $ p � � � � M � � � � � � C � | � < � � x � � � � ^ � � � � � # ~ � � b � � � � � 7 3 r ' m � � � � X 2 � � ) � 1 6 � ' , � � � � � c ? V � � - � D J S � ! � N � W ? � " 4 � n � R � # Z 0 %1$d Added, %2$d Removed, %3$d Changed %1$s %2$d %1$s (%2$s) %1$s - %2$s ago %1$s <span class="itsec-error-code">(%2$s)</span> %1$s Migrating log entries from an older format. This message will update when the migration is complete. %1$s is enabled as recommended. %1$s is the input name. %2$s is the error message.The directory supplied in %1$s cannot be used as a valid directory. %2$s %1$s is the input name. %2$s is the error message.The file path supplied in %1$s cannot be used as the parent directory cannot be created. %2$s %1$s plugin %2$s %1$s theme %2$s %1$sHide Backend%2$s will notify the chosen recipients whenever the login URL is changed. %s approved comment %s approved comments %s comment %s comments %s could not be read due to an unknown error. %s could not be read. Both the fopen/feof/fread/flock and file_get_contents functions are disabled on the server. %s could not be read. Both the opendir/readdir/closedir and glob functions are disabled on the server. %s could not be read. It does not appear to be a file. %s could not be written as a file. The requested path already exists as a directory. The directory must be removed or a new file name must be chosen before the file can be written. %s could not be written. Both the fopen/fwrite/flock and file_put_contents functions are disabled on the server. This is a server configuration issue that must be resolved before iThemes Security can write files. %s could not be written. This could be due to a permissions issue. Ensure that PHP runs as a user that has permission to write to this location. %s item %s items %s pending comment %s pending comments ← Back to %s <b>Host:</b> %1$s <b>User:</b> %1$s <strong>ERROR</strong>: Invalid email address or incorrect password. <strong>ERROR</strong>: Invalid username or incorrect password. A "internal server" error prevented the request from completing as expected. The server returned a 500 status code, indicating that the server was unable to complete the request due to a fatal PHP error or a server problem. This could be due to a plugin/theme conflict, a server configuration issue, a temporary hosting issue, or invalid custom PHP modifications. Please check your server's error logs for details about the source of the error and contact your hosting company for assistance if required. A "not found" error prevented the request from completing as expected. The server returned a 404 status code, indicating that the server was unable to find the requested admin-ajax.php file. This could be due to a plugin/theme conflict, a server configuration issue, or an incomplete WordPress installation. Please try refreshing the page and trying again. If the request continues to fail, you may have to alter plugin settings, alter server configurations, or reinstall WordPress. A "request forbidden" error prevented the request from completing as expected. The server returned a 403 status code, indicating that the server configuration is prohibiting this request. This could be due to a plugin/theme conflict or a server configuration issue. Please try refreshing the page and trying again. If the request continues to fail, you may have to alter plugin settings or server configuration that could account for this AJAX request being blocked. A File Change scan is currently in progress. A Nickname is required. Please choose a nickname or fill out your first and last name. A file (or files) on your site have been changed. Please review the report below to verify changes are not the result of a compromise. A file or directory already exists at <code>%s</code>. No Directory Name changes have been made. Please choose a new Directory Name or remove the existing file or directory and try again. A nonce security check failed, preventing the request from completing as expected. Please try reloading the page and trying again. A parser error prevented the request from completing as expected. The site sent a response that jQuery could not process. This could be due to a plugin/theme conflict or a server configuration issue. A password change is required for your account. A permissions security check failed, preventing the request from completing as expected. The currently logged in user does not have sufficient permissions to make this request. Please try reloading the page and trying again. A query failure prevented the log data from being accessed: %s A scan is already in progress. Please check the <a href="%s" target="_blank" rel="noopener noreferrer">logs page</a> at a later time for the results of the scan. A timeout error prevented the request from completing as expected. The site took too long to respond. This could be due to a plugin/theme conflict or a server configuration issue. A validation check for %1$s failed. The %2$s value is missing. This could be due to a problem with the iThemes Security installation or an invalid modification. Please reinstall iThemes Security and try again. A validation function for %1$s received data that did not have the required entry for %2$s. A validation function for %1$s received data that does not match the expected data type for the %2$s entry. A data type of %3$s was expected, but a data type of %4$s was received. A validation function for %1$s received data that has an entry for %2$s when no such entry exists. API Key Action Actions (%s) Activate Network Brute Force Protection Activating Network Brute Force Protection... Active Lockouts Added Added Files Added by W3 Total Cache Additional information Admin User Advanced Advanced Entries for Support and Developers Advanced feature to rename the wp-content directory to a different name. All Events All Events (%s) All dates Allow Data Tracking Allow iThemes to track plugin usage via anonymous data. An "invalid format" error prevented the request from completing as expected. The format of data returned could not be recognized. This could be due to a plugin/theme conflict or a server configuration issue. An attempt to register the %1$s module failed since the supplied path (%2$s) is invalid. This could indicate an invalid modification or incomplete installation of the iThemes Security plugin. Please reinstall the plugin and try again. An empty ip argument was submitted. An invalid sanitize type of "%1$s" was received for the %2$s input. An unknown error occured. Please try again later An unknown error prevented the API key request from succeeding. The request for an API key returned an empty key. Please wait a few minutes and try again. An unknown error prevented the API key request from succeeding. The request for an API key returned an unrecognized response. Please wait a few minutes and try again. An unknown error prevented the API key request from succeeding. This problem could be due to a server configuration or plugin compatibility issue. Please wait a few minutes and try again. An unknown error prevented the API key secret request from succeeding. The request for an API key secret returned an unrecognized response. Please wait a few minutes and try again. An unknown error prevented the API key secret request from succeeding. The request for an API key submitted an empty key. Please wait a few minutes and try again. An unknown error prevented the API key secret request from succeeding. This problem could be due to a server configuration or plugin compatibility issue. Please wait a few minutes and try again. An unknown error prevented the API key secrete request from succeeding. The request for an API key secret returned an empty key secret. Please wait a few minutes and try again. An unknown error prevented the request from completing as expected. This could be due to a plugin/theme conflict or a server configuration issue. Analytics Apply Are you lost? Attached is the database backup file for your site. Automatically ban IPs reported as a problem by the network. Backup Interval Backup Location Backup Method Backup complete. The backup was saved locally. Backup complete. The backup was sent to the selected email recipients and was saved locally. Backup complete. The backup was sent to the selected email recipients. Backups to Retain Ban Hosts - Security > Settings > Banned Users Ban Reported IPs Ban User Agents Ban User Agents - Security > Settings > Banned Users Banned Use of "admin" Username Banned Users Block Expiration Block specific IP addresses and user agents from accessing the site. Blocked Host Attempted Login Blocked Host Attempted Login With Good Credentials Both Brute Force Bulk Actions By default, WordPress allows users to log in using either an email address or username. This setting allows you to restrict logins to only accept email addresses or usernames. CRITICAL ERROR: The <code>%1$s</code> directory was successfully renamed to the new name (<code>%2$s</code>). However, an error occurred when updating the <code>wp-config.php</code> file to configure WordPress to use the new content directory. iThemes Security attempted to rename the directory back to its original name, but an unknown error prevented the rename from working as expected. In order for your site to function properly, you will either need to manually rename the <code>%2$s</code> directory back to <code>%1$s</code> or manually update the <code>wp-config.php</code> file with the necessary modifications. The error that prevented the file from updating is as follows: %3$s Cancel Cannot get lock. Change Content Directory Change Database Table Prefix Change User ID 1 Change WordPress Salts Changed Changed Files Changed the Authentication Methods Available to Users setting in Two-Factor Authentication to "All Methods". Changed the Multiple Authentication Attempts per XML-RPC Request setting in WordPress Tweaks to "Block". Changed the REST API setting in WordPress Tweaks to "Restricted Access". Changes Found Clean Colors Comments Community Lockout Message Complete! Compress Backup Files Configure basic settings that control how iThemes Security functions. Confirm new password Contact Forms Cookies Could not rename table %1$s. You may have to rename the table manually. Could not update prefix references in options table. Could not update prefix references in usermeta table. Critical Issue Critical Issues Critical Issues (%s) Current Page Custom Login Action Daily Daily Security Digest Database Backup Database Backups Database Only Date Days to Keep Database Logs Debug Debug (%s) Debug info (source page): %s Default Access Description Details Disable Disable Directory Browsing Disable Directory Browsing - Security > Settings > System Tweaks > Directory Browsing Disable Extra User Archives Disable File Editor Disable File Editor - Security > Settings > WordPress Tweaks > File Editor Disable PHP execution in the plugins directory. This blocks requests to PHP files inside plugin directories that can be exploited directly. Disable PHP execution in the themes directory. This blocks requests to PHP files inside theme directories that can be exploited directly. Disable PHP execution in the uploads directory. This blocks requests to maliciously uploaded PHP files in the uploads directory. Disable PHP in Plugins Disable PHP in Plugins - Security > Settings > System Tweaks > PHP in Plugins Disable PHP in Themes Disable PHP in Themes - Security > Settings > System Tweaks > PHP in Themes Disable PHP in Uploads Disable PHP in Uploads - Security > Settings > System Tweaks > PHP in Uploads Disable Pingbacks Disable XML-RPC - Security > Settings > WordPress Tweaks > XML-RPC Disabled Disabled the File Editor in WordPress Tweaks. Do not modify or remove this line Do not remove. Removing this line could break your site. Added by Security > Settings > Change Content Directory. Documentation During periods of heavy attack, iThemes Security can generate a LOT of email. Email Address Email Address Only Email Address: %1$s Email Only Email Send Failed Email Send Succeeded Embedded content from other websites Enable Enable Ban Lists Enable Redirection Enable the hide backend feature. Enabled Enabled %1$s. Enabled the Enable Ban Lists setting in Banned Users. Enabled the Vulnerable Site Protection setting in Two-Factor Authentication. Enabled the Vulnerable User Protection setting in Two-Factor Authentication. Enabled the Write to Files setting in Global Settings. Enables secure SSL connection for the front-end (public parts of your site). Turning this off will disable front-end SSL control, turning this on "Per Content" will place a checkbox on the edit page for all posts and pages (near the publish settings) allowing you to turn on SSL for selected pages or posts. Selecting "Whole Site" will force the whole site to use SSL. Error Error Message: %s Error. Errors (%s) Excerpt View Failed to insert log entry: %s Fatal Error Fatal Errors (%s) File File Change File Change Detection File Change Warning File Changes File Created File Created and Emails Sent File Created but Email Send Failed File Hash File Only File Permissions File Scan Report for %s File changes detected on the site. File types listed here will not be checked for changes. While it is possible to change files such as images it is quite rare and nearly all known WordPress attacks exploit php, js and other text files. Files addedAdded Files modifiedModified Files removedRemoved Filter by date First page For more details, %1$svisit your security logs%2$s Force Unique Nickname Force users to use strong passwords as rated by the WordPress password meter. Forces all dashboard access to be served only over an SSL connection. Four Times per Day Free WordPress Security Guide Front End SSL Mode Get Free API Key Get Support Get iThemes Security Pro Global Settings Help & Support Hide Backend Hide Backend – New Login URL Hide Current Entries Hide Raw Details Hide Security Menu in Admin Bar Hide existing entries from view without deleting them. Host Host Lockout Host Lockout Message Host Lockout: <code>%s</code> Host/User Hosts How long we retain your data How should event logs be kept How we protect your data ID IP Blocked If you contact support about this error, please provide the following debug details: Ignore File Types Important Events Important Events (%s) Invalid Login Invalid User Join a network of sites that reports and protects against bad actors on the internet. Last Run Last page Learn More Learn simple WordPress security tips — including 3 kinds of security your site needs and 4 best security practices for keeping your WordPress site safe with our <a href="%s">free guide</a>. List View Lists file and directory permissions of key areas of the site. Loading... Local Brute Force Protection Lockout Lockout in Effect Until Lockouts Log entries hidden. Log entries shown. Login Now Login Page Login Slug Login Source Login with Email Address or Username Logs Magic Links Malware Manage Settings Manage and configure email notifications sent by iThemes Security related to various settings modules. Max Login Attempts Per Host Max Login Attempts Per User Media Megabytes of memory used%s MB Memory Used Messages Migration complete. Please refresh the page to see all log entries. Minutes to Remember Bad Login (check period) Modified Module Monitor the site for unexpected file changes. Monthly Monthly Security Digest Multiple versions of iThemes Security are active. Please disable all extra versions of iThemes Security. NGINX Conf File Network Brute Force Network Brute Force Protection New Login URL New Notification from iThemes Security New Password New notifications available in the %1$sNotification Center%2$s. New! Take your site security to the next level by activating iThemes Brute Force Network Protection. Next page No No Changes Found No approved comments No changes were detected. No comments No events. No items found. No lockouts since the last email check. No pending comments Notice Notices (%s) Notification Center Notifications Number of items per page: Pagination Path to Log Files Permanently Permissions for the directory %s could not be read as the directory could not be found. Permissions for the directory %s could not be read as the fileperms() function is disabled. This is a system configuration issue. Permissions for the file %s could not be read as the file could not be found. Permissions for the file %s could not be read as the fileperms() function is disabled. This is a system configuration issue. Powered by WordPress Prevent public access to readme.html, readme.txt, wp-config.php, install.php, wp-includes, and .htaccess. These files can give away important information on your site and serve no purpose to the public once WordPress has been successfully installed. Prevents users from seeing a list of files in a directory when no index file is present. Previous page Pro Process Process (%s) Protect System Files Protect System Files - Security > Settings > System Tweaks > System Files Protect your site against attackers that try to randomly guess login details to your site. REST API REST API Authentication Raw Details Reason Receive Email Updates Redirect All HTTP Page Requests to HTTPS Redirect users to a custom location on your site, instead of throwing a 403 (forbidden) error. Redirection Slug Refresh Page Register Slug Release lockouts from the Active Lockouts section of the settings page. Release the permanent host ban from Ban Hosts list in the Banned Users section of the settings page. Removed Removed Files Require SSL Rescheduling Results SSL SSL for Dashboard Save Locally Only Save Locally and Email Scan Scan Details Scan Failed Scan Files Now Scan Performance Scan Summary Scanning admin files... Scanning content files... Scanning files... Scanning includes files... Scanning media files... Scanning plugin files... Scanning theme files... Scanning... Schedule Schedule Database Backups Security Security Check Security Digest Security Logs Security error! Select All Select bulk action Select what we should do with your backup file. You can have it emailed to you, saved locally or both. Server Config Rules Settings Show All Entries Show Debug entries. Show Details Show Error Codes Show Process entries. Show Raw Details Show all entries, including ones that were previously hidden. Show more details Show only entries for this %s Show only entries for this day Site Database Backup for %s Site Lockout Notification Site Lockouts Site: %s Strength indicator Strong Password Enforcement Strong Passwords Support System Files System Tweaks Take the guesswork out of WordPress security. iThemes Security offers 30+ ways to lock down WordPress in an easy-to-use WordPress security plugin. The "Write to Files" setting is disabled in Global Settings. In order to use this feature, you must enable the "Write to Files" setting. The "Write to Files" setting is disabled. Manual configuration for the <code>%s</code> file can be found on the Security > Settings page in the Advanced section. The %1$s email list must be a string with each entry separated by a new line. The %1$s value cannot be empty. The %1$s value is not a valid username. The %1$s value must be a positive integer. The %1$s value must be a string with each entry separated by a new line. The %1$s value must be a string. The %1$s value must be a valid date in the format of YYYY-MM-DD. The %1$s value must be a valid date. The %1$s value must be a valid email address. The %1$s value must be an integer. The %1$sDatabase Backup%2$s module will send a copy of any backups to the email addresses listed below. The %1$sFile Change Detection%2$s module will email a file scan report after changes have been detected. The %s module is a Core module and cannot be activated or deactivated. The ITSEC_DISABLE_MODULES define is set. All iThemes Security protections are disabled. Please make the necessary settings changes and remove the define as quickly as possible. The Security Digest reduces the number of emails sent so you can receive a summary of lockouts and file change detection scans. The Security Digest reduces the number of emails sent so you can receive a summary of lockouts, file change detection scans, and privilege escalations. The URL to your website. The WordPress salts were successfully regenerated. The content directory cannot be changed to a blank directory name. The data validator for %1$s is missing. Data for the module cannot be saved without the validator. This error could indicate a bad install of iThemes Security. Please remove the plugin and reinstall it. If this message persists, please contact support and send them this error message. The direction argument must be either "add", "clear", or "remove". The directory %s could not be created as a file with that name already exists. The directory %s could not be created as an existing parent directory could not be found. The directory %s could not be created as the mkdir() function is disabled. This is a system configuration issue. The directory %s could not be created due to an unknown error. This could be due to a permissions issue. The directory %s could not be protected from file listing as the directory does not exist. The directory %s could not be removed as the rmdir() function is disabled. This is a system configuration issue. The directory supplied in %1$s is not writable. Please select a directory that can be written to. The email value is missing. The file %1$s could not have its permissions updated as non-integer permissions were sent: (%2$s) %3$s The file %s could not be removed as the unlink() function is disabled. This is a system configuration issue. The file %s could not have its permissions updated as the chmod() function is disabled. This is a system configuration issue. The file path supplied in %1$s cannot be used as it already exists but is not a file. Please supply a valid file path. The file path supplied in %1$s could not be created. Please supply a file path that can be written to. The file path supplied in %1$s is not writable. Please supply a file path that can be written to. The file path supplied in %1$s was successfully created, but it cannot be updated. Please supply a file path that can be written to. The following IP in %1$s is invalid: %2$l The following IPs in %1$s are invalid: %2$l The following email in %1$s is invalid: %2$l The following emails in %1$s are invalid: %2$l The following entry in %1$s is invalid: %2$l The following entries in %1$s are invalid: %2$l The following extension in %1$s is invalid: %2$l The following extensions in %1$s are invalid: %2$l The following is a summary of security related activity on your site: %s The ip argument is missing. The log entry migration failed. Reload the page to try again. The log file can be found at: <code>%s</code> The login address for {{ $site_title }} has changed. The new login address is {{ $login_url }}. You will be unable to use the old login address. The message to display to a user when their IP has been flagged as bad by the iThemes network. The message to display to a user when their account has been locked out. The message to display when a computer (host) has been locked out. The new directory name cannot be an absolute path. Please supply a path that is relative to <code>ABSPATH</code> (<code>%s</code>). The new directory name cannot be the same as the current directory name. Please supply a new directory name. The new login link. The number of days between database backups. The number of login attempts a user has before their host or computer is locked out of the system. Set to 0 to record bad login attempts without locking out the host. The number of login attempts a user has before their username is locked out of the system. Note that this is different from hosts in case an attacker is using multiple computers. In addition, if they are using your login name you could be locked out yourself. Set to 0 to log bad login attempts per user without ever locking the user out (this is not recommended). The number of minutes in which bad logins should be remembered. The password has not been updated. The scan failed to properly scan the site. The security logs are retained since they may be required as part of analysis of a site compromise. The server did not receive a valid request. An unknown "method" argument was supplied. Please try again. The server did not receive a valid request. The required "data" argument for the module is missing. Please try again. The server did not receive a valid request. The required "id" argument is missing. Please try again. The server did not receive a valid request. The required "method" argument is missing. Please try again. The server did not receive a valid request. The required "module" argument is missing. Please try again. The settings could not be saved. Due to an unknown error. Please try refreshing the page and trying again. The settings could not be saved. Please correct the error above and try again. The settings could not be saved. Please correct the errors above and try again. The settings saved successfully. The slug to redirect users to when they attempt to access wp-admin while not logged in. The supplied email address (%s) is invalid. A valid email address is required in order to sign up for the Network Bruteforce Protection by iThemes. The updates_optin value is missing. The user changes have not been saved. The user has not been created. The valid value for %1$s is: %2$l. The valid values for %1$s are: %2$l. There was an error returned from the Network Brute Force Protection API: %1$s This email was generated by the iThemes Security plugin on behalf of %s. This email was generated by the iThemes Security plugin. This has been disabled. This is a test file generated by iThemes Security. It can be removed. This path must be writable by your website. For added security, it is recommended you do not include it in your website root folder. Time Timestamp To unsubscribe from these notifications, please %1$scontact the site administrator%2$s. To unsubscribe from these updates, visit the %1$sSettings page%2$s in the iThemes Security plugin menu. To view logs within the plugin you must enable database logging in the Global Settings. File logging is not available for access within the plugin itself. Too large to display Total Memory Tutorials Two-Factor Authentication Two-Factor Authentication greatly increases the security of your WordPress user account by requiring additional information beyond your username and password in order to log in. Type URL Unable to create a backup at this time since a backup is currently being created. If you wish to create an additional backup, please wait a few minutes before trying again. Unable to create the backup directory due to an unknown error. Unable to find a valid settings object for %s. Setting was unable to be saved. Unable to find a valid settings object for %s. Settings were unable to be saved. Unable to read %1$s due to the following error: %2$s Unable to read the <code>wp-config.php</code> file in order to update the salts. You will need to manually update the file. Error details as follows: %1$s (%2$s) Unable to remove %1$s due to the following error: %2$s Unable to remove %s due to an unknown error. Unable to rename the <code>%1$s</code> directory to <code>%2$s</code>. This could indicate a file permission issue or that your server does not support the supplied name as a valid directory name. No config file or directory changes have been made. Unable to set the permissions of the new Directory Name (<code>%1$s</code>) to match the permissions of the old Directory Name. You may have to manually change the permissions of the directory to <code>%2$s</code> in order for your site to function properly. Unable to strip comments from the source code as the token_get_all() function is disabled. This is a system configuration issue. Unable to strip comments from the source code as the token_get_all() function returned an unrecognized value (type: %s) Unable to update the <code>wp-config.php</code> file in order to update the salts. You will need to manually update the file. Error details as follows: %1$s (%2$s) Unable to update the <code>wp-config.php</code> file. No directory or config file changes have been made. The error that prevented the file from updating is as follows: %1$s Unable to write the backup file. This may be due to a permissions or disk space issue. Unable to write to the log file. This could indicate that there is no space available, that there is a permissions issue, or that the server is not configured properly. Unknown Unknown contacts for %1$s, %2$l. Unknown error type received: %1$s. Unknown schedule for %1$s, %2$s. Unknown tags for %1$s, %2$l. Update Password Updates to <code>wp-config.php</code> are disabled via a filter. Use colors to indicate the severity of each entry. User User Lockout User Lockout Message User Lockout: <code>%s</code> User Logging Username Username Lockout Username Lockout: <code>%s</code> Username Only Usernames Users Various modules send emails to notify you when a user or host is locked out of your website. View Details View Logs View Mode Visit Banned Users Settings Visit Settings Page WP-CLI Command WP-Cron Scheduled Task Warning Warnings (%s) Website Weekly Weekly Security Digest What automated decision making and/or profiling we do with user data What data breach procedures we have in place What personal data we collect and why we collect it What rights you have over your data What third parties we receive data from Where we send your data Who we share your data with Why go Pro? <a href="%s">Check out the Free/Pro comparison chart.</a> With Network Brute Force Protection, your site is protected against attackers found by other sites running iThemes Security. If your site identifies a new attacker, it automatically notifies the network so that other sites are protected as well. To join this site to the network and enable the protection, click the button below. WordPress Core %s WordPress Login Address Changed WordPress Salts WordPress Tweaks Write to Files XML-RPC XML-RPC services are disabled on this site. XMLRPC Authentication Yes You do not have sufficient permission to access this endpoint. Access to REST API requests is restricted by iThemes Security settings. You have been locked out due to too many invalid login attempts. You must restart your NGINX server for the changes to take effect. Your Daily Security Digest for %s Your IP address has been flagged as a threat by the iThemes Security network. Your Monthly Security Digest for %s Your Nickname must be different than your login name. Please choose a different Nickname. Your Security Digest for %s Your Weekly Security Digest for %s Your profile has not been updated. Your screen options saved successfully. Your site is now using Network Brute Force Protection. [%1$s] %2$s https://ithemes.com https://ithemes.com/security https://wordpress.org/ iThemes iThemes Security iThemes Security Logs iThemes Security Plugin iThemes Security Settings iThemes Security can log events in multiple ways, each with advantages and disadvantages. Database Only puts all events in the database with your posts and other WordPress data. This makes it easy to retrieve and process but can be slower if the database table gets very large. File Only is very fast but the plugin does not process the logs itself as that would take far more resources. For most users or smaller sites Database Only should be fine. If you have a very large site or a log processing software then File Only might be a better option. iThemes Security preserved the following settings as removing them could prevent the site from functioning correctly. paging%1$s of %2$s too many bad login attempts user tried to login as "admin." wp-config.php Rules PO-Revision-Date: 2018-05-27 08:49:00+0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=1; plural=0;
X-Generator: GlotPress/4.0.0-alpha.7
Language: zh_CN
Project-Id-Version: Plugins - iThemes Security - Stable (latest release)
%1$d 已添加，%2$d 已移除，%3$d 已更改 %1$s %2$d %1$s（%2$s） %1$s - %2$s 前 %1$s<span class="itsec-error-code">（%2$s）</span> %1$s 从旧格式迁移日志条目，迁移完成后，此信息将更新。 %1$s 已启用（推荐）。 %1$s 提供的目录不能用作有效的目录。%2$s %1$s 提供的文件路径无法使用，因为无法创建父级目录。%2$s %1$s 插件 %2$s %1$s 主题 %2$s %1$s隐藏后台%2$s 会在更改登录网址时通知选定的收件人。 %s 条批准评论 %s 条评论 由于未知错误，%s 无法读取。 无法读取 %s。在服务器上禁用 fopen/feof/fread/flock 和 file_get_contents 函数。 无法读取 %s。在服务器上禁用了 opendir/readdir/closedir 和 glob 函数。 无法读取 %s。其似乎不是一个文件。 %s 不能写为文件。请求的路径已经作为目录存在。在写入文件之前，必须移除此目录或选择新的文件名。 无法写入 %s。服务器上禁用了 fopen/fwrite/flock 和 file_put_contents 函数。这是 iThemes 安全可以写入文件之前必须解决的服务器配置问题。 无法写入 %s。这可能是由于权限问题。确保 PHP 以有权写入此位置的用户身份运行。 %s 个项目 %s 条待定评论 ← 返回到 %s <b>主机：</b>%1$s <b>用户：</b>%1$s <strong>错误</strong>：无效的邮箱地址或密码错误。 <strong>错误</strong>：无效的用户名或密码不正确。 "内部服务器" 错误阻止了请求按预期完成。服务器返回了 500 状态码，表明服务器由于致命的 PHP 错误或服务器问题而无法完成请求。这可能是由于插件/主题冲突，服务器配置问题，临时主机问题或无效的自定义 PHP 修改。请检查您的服务器的错误日志，以获取有关错误来源的详细信息，并在需要时联系您的主机公司寻求帮助。 "未找到" 错误阻止了请求按预期完成。服务器返回了 404 状态码，表明服务器无法找到请求的 admin-ajax.php 文件。这可能是由于插件/主题冲突，服务器配置问题或不完整的WordPress 安装。请尝试刷新页面并重试。如果请求继续失败，则可能需要更改插件设置，更改服务器配置或重新安装 WordPress。 "请求禁止" 错误阻止了请求按预期完成。服务器返回了 403 状态码，表明服务器配置正在禁止此请求。这可能是由于插件/主题冲突或服务器配置问题。请尝试刷新页面并重试。如果请求继续失败，则可能需要更改可能导致此 AJAX 请求被阻止的插件设置或服务器配置。 文件更改扫描目前正在进行中。 昵称是必需的。请选择一个昵称或填写您的姓氏和名字。 您站点上的一个文件（或多个文件）已被更改。请查看下面的报告以验证更改不是妥协的结果。 文件或目录已存在于 <code>%s</code>。目录名称更改未能完成。请选择一个新的目录名称或移除现有的文件或目录，然后重试。 现时安全检查失败，阻止请求按预期完成。请尝试重新加载页面并重试。 解析器错误阻止了请求按预期完成。该站点发送了一个 jQuery 无法处理的响应。这可能是由于插件/主题冲突或服务器配置问题。 您的账号需要更改密码。 权限安全检查失败，阻止请求按预期完成。当前登录的用户没有足够的权限来提出此请求。请尝试重新加载页面并重试。 查询失败阻止了日志数据被访问：%s 扫描已在进行中。请稍后查看<a href="%s" target="_blank" rel="noopener noreferrer">日志页面</a>以获取扫描结果。 超时错误阻止了请求按预期完成。该站点花了很长时间回应。这可能是由于插件/主题冲突或服务器配置问题。 对 %1$s 的验证检查失败。%2$s 值缺失。这可能是由于 iThemes 安全安装出现问题或修改无效造成的。请重新安装 iThemes 安全并重试。 %1$s 的验证函数收到的数据没有 %2$s 所需的条目。 %1$s 的验证函数收到的数据与 %2$s 条目的预期数据类型不匹配。预计会有 %3$s 的数据类型，却接收到 %4$s 的数据类型。 当不存在这样的条目时，%1$s 的验证函数接收到具有 %2$s 条目的数据， API 密钥 操作 操作（%s） 激活网络暴力攻击保护 正在激活网络暴力攻击保护... 活动锁定 已增加 已添加的文件 已由 W3 Total Cache 添加 附加信息 管理员用户 高级 支持和开发人员的高级条目 通过将 wp-content 目录重命名为不同名称的高级功能。 所有事件 所有事件（%s） 所有日期 允许数据跟踪 允许 iThemes 通过匿名数据跟踪插件使用情况。 "无效格式" 错误阻止了请求按预期完成。返回的数据格式无法识别。这可能是由于插件/主题冲突或服务器配置问题。 由于提供的路径（%2$s）无效，因此尝试注册 %1$s 模块失败。这可能表明 iThemes 安全插件有无效修改或安装不完整。请重新安装插件并重试。 提交了一个空的 ip 参数。 已收到 %2$s 输入的无效清理类型 "%1$s"。 出现未知错误。请稍后再试 未知错误阻止了 API 密钥请求的成功。对 API 密钥的请求返回了一个空密钥。请稍等几分钟，然后重试。 未知错误阻止了 API 密钥请求的成功。对 API 密钥的请求返回了无法识别的响应。请稍等几分钟，然后重试。 未知错误阻止了 API 密钥请求的成功。这个问题可能是由于服务器配置或插件兼容性问题。请稍等几分钟，然后重试。 未知错误阻止了 API 隐私密钥请求的成功。对 API 隐私密钥的请求返回了无法识别的响应。请稍等几分钟，然后重试。 未知错误阻止了 API 隐私密钥请求的成功。对 API 密钥的请求提交了一个空密钥。请稍等几分钟，然后重试。 未知错误阻止了 API 隐私密钥请求的成功。这个问题可能是由于服务器配置或插件兼容性问题。请稍等几分钟，然后重试。 未知错误阻止了 API 隐私密钥的请求成功。对 API 隐私密钥的请求返回了一个空的隐私密钥。请稍等几分钟，然后重试。 未知的错误阻止了请求按预期完成。这可能是由于插件/主题冲突或服务器配置问题。 分析学 应用 您迷路了吗？ 附件是您的站点的数据库备份文件。 自动禁止向网络报告为问题的 IP。 备份间隔 备份位置 备份方法 备份完成。备份已保存在本地。 备份完成。备份已发送至选定的邮件收件人并保存在本地。 备份完成。备份已发送到选定的邮件收件人。 备份保留 禁止主机 - 安全 > 设置 > 禁止的用户 禁止报告的 IP 禁止用户代理 禁止用户代理 - 安全 > 设置 > 禁止的用户 禁止使用 "admin" 用户名 禁止的用户 阻止到期 阻止访问该站点指定的 IP 地址和用户代理。 已阻止主机尝试登录 已阻止主机尝试使用良好证书登录 两者 暴力攻击 批量操作 默认情况下，WordPress 允许用户使用邮箱地址或用户名登录。此设置允许您将登录限制为只接受邮箱地址或用户名。 严重错误：<code>%1$s</code> 目录已成功重命名为新名称（<code>%2$s</code>）。但是，更新 <code>wp-config.php</code> 文件以将 WordPress 配置为使用新 content 目录时发生错误。iThemes 安全尝试将目录重命名为其原始名称，但未知错误阻止重命名按预期工作。为了让您的站点正常运行，您需要手动将 <code>%2$s</code> 目录重新命名为 <code>%1$s</code> 或手动更新 <code>wp-config.php</code> 文件进行必要的修改。阻止文件更新的错误如下：%3$s 取消 无法锁定。 更改 Content 目录 更改数据库数据表前缀 更改用户 ID 1 更改 WordPress Salts 已更改 已更改的文件 将双重身份认证中设置的用户可以使用的身份认证方法更改为 "所有方法"。 将 WordPress 微调中的每个 XML-RPC 请求设置的多重认证尝试更改为 "阻止"。 将 WordPress 微调中的 REST API 设置更改为 "限制访问"。 发现更改 清理 颜色 评论 社区锁定信息 完成！ 压缩备份文件 配置控制 iThemes 安全功能的基本设置。 确认新密码 联系人表单 Cookies 无法重命名数据表 %1$s。您可能需要手动重命名数据表。 无法更新选项数据表中的前缀引用。 无法更新用户元数据表中的前缀引用。 严重问题 严重问题 严重问题（%s） 当前页 自定义登录操作 每日 每日安全摘要 数据库备份 数据库备份 仅数据库 日期 保留数据库日志的天数 调试 调试（%s） 调试信息（源页面）：%s 默认访问 描述 详细信息 停用 禁用目录浏览 禁用目录浏览 - 安全 > 设置 > 系统微调 > 目录浏览 禁用额外用户归档 禁用文件编辑器 禁用文件编辑器 - 安全 > 设置 > WordPress 微调 > 文件编辑器 禁用 plugins 目录中的 PHP 执行。这阻止了可以直接利用 plugins 目录内的 PHP 文件的请求。 禁用 themes 目录中的 PHP 执行。这阻止了可以直接利用 themes 目录内的 PHP 文件的请求。 禁用 uploads 目录中的 PHP 执行。这阻止了可以直接利用 uploads 目录内的 PHP 文件的请求。 禁用 Plugins 目录的 PHP 禁用 Plugins 目录的 PHP - 安全 > 设置 > 系统微调 > Plugins 目录的 PHP 禁用 Themes 目录的 PHP 禁用 Themes 目录的 PHP - 安全 > 设置 > 系统微调 > Themes 目录的 PHP 禁用 Uploads 目录的 PHP 禁用 Uploads 目录的 PHP - 安全 > 设置 > 系统微调 > Uploads 目录的 PHP 禁用 Pingbacks 禁用 XML-RPC - 安全 > 设置 > WordPress 微调 > XML-RPC 已停用 在 WordPress 微调中已禁用文件编辑器。 不要修改或移除此行 不要移除。移除此行可能会破坏您的站点。是通过 安全 > 设置 > 更改 Content 目录 进行添加的。 文档 在重度攻击期间，iThemes 安全可能生成大量邮件。 电邮地址 只接受邮箱地址 邮箱地址：%1$s 只发送邮件 邮件发送失败 邮件发送成功 来自其他网站的嵌入式内容 启用 启用禁止列表 启用重定向 启用隐藏后台功能。 已启用 已启用 %1$s。 在禁止的用户中已启用 "启用禁止列表" 设置。 在双重身份认证中启用易受攻击的站点保护设置。 在双重身份认证中启用易受攻击的用户保护设置。 在全局设置中启用写入文件设置。 为前端（您的站点的公共部分）启用安全 SSL 连接。关闭此功能将禁用前端 SSL 控制功能，打开此功能后，"每项内容" 会为所有文章和页面（发布设置附近）的编辑页面设置一个复选框，以允许您为选定的页面或文章启用 SSL。选择 "整个站点" 将强制整个站点使用 SSL。 错误 错误信息：%s 错误。 错误（%s） 摘要视图 无法插入日志条目：%s 致命错误 致命错误（%s） 文件 文件更改 文件更改检测 文件更改警告 文件更改 文件已创建 文件已创建和邮件已发送 文件已创建，但邮件发送失败 文件校验码 仅文件 文件权限 %s 的文件扫描报告 在站点上检测到文件更改. 此处列出的文件类型将不会被检查更改。虽然可以更改图片等文件，但这种情况非常罕见，几乎所有已知的 WordPress 攻击都是利用 php，js 和其他文本文件。 已添加 已修改 已移除 按日期过滤 第一页 有关更多详细信息，%1$s请访问您的安全日志%2$s 强制唯一的昵称 强制用户使用 WordPress 密码强度表所评定的强密码。 强制所有仪表盘访问只能通过 SSL 连接进行服务。 每日四次 免费的 WordPress 安全指南 前端 SSL 模式 获取免费 API 密钥 获取支持 获取 iThemes 安全专业版 全局设置 帮助 & 支持 隐藏后台 隐藏后台 – 新的登录网址 隐藏当前条目 隐藏原始详细信息 在管理面板侧边栏中隐藏安全菜单 从视图中隐藏现有条目而不是将他们删除。 主机 主机锁定 主机锁定信息 主机锁定：<code>%s</code> 主机/用户 主机 我们保留您的数据多久 事件日志应该如何保存 我们如何保护您的数据 ID IP 已阻止 如果您联系有关此错误的支持，请提供以下调试详细信息： 忽略文件类型 重要事件 重要事件（%s） 无效的登录 无效的用户 加入站点的网络报告并防止互联网上的不良行为。 上次运行 最后一页 了解更多 学习简单的 WordPress 安全提示 — 包括您站点需要的 3 种安全性以及 4 种最佳安全实践，以便使用我们的<a href="%s">免费指南</a>保护您的 WordPress 站点的安全。 列表视图 列出站点关键区域的文件和目录权限。 正在加载... 本地暴力攻击保护 锁定 锁定生效直到 锁定 日志条目已隐藏。 日志条目已显示。 立即登录 登录页面 登录别名 登录源 使用邮箱地址或用户名登录 日志 魔法链接 恶意软件 管理设置 管理和配置 iThemes 安全发送的与各种设置模块相关的邮件通知。 每个主机的最大登录尝试次数 每个用户的最大登录尝试次数 媒体 %s MB 内存占用 信息 迁移完成。请刷新页面以查看所有日志条目。 记住不良登录的分钟数（检查周期） 已修改 模块 监视站点是否有意外的文件更改。 每月一次 每月安全摘要 由于 iThemes 安全的多个版本都处于活动状态。请停用 iThemes 安全的所有额外版本。 NGINX 配置文件 网络暴力攻击 网络暴力攻击保护 新的登录网址 来自 iThemes 安全的新通知 新密码 %1$s通知中心%2$s提供新的通知。 新功能！通过激活 iThemes 暴力攻击网络保护，将您的站点安全性提升到一个新的水平。 下一页 否 未发现更改 无批准的评论 没有检测到更改。 暂无评论 没有事件。 未找到项目。 自上次邮件检查后未锁定。 无待定的评论 通知 通知（%s） 通知中心 通知 每页的项目数量： 分页 日志文件的路径 永久 无法找到目录 %s 的权限，因为无法找到该目录。 由于 fileperms() 函数被禁用，因此无法读取目录 %s 的权限。这是一个系统配置问题。 无法找到文件 %s 的权限，因为无法找到该文件。 由于 fileperms() 函数已被禁用，因此无法读取文件 %s 的权限。这是一个系统配置问题。 由 WordPress 提供 阻止公众访问 readme.html，readme.txt，wp-config.php，install.php，wp-includes，和 .htaccess。这些文件可以把您站点上的重要信息泄露出去，一旦 WordPress 成功安装了，就不会对公众有任何意义了。 当没有索引文件存在时，防止用户看到目录中的文件列表。 上一页 专业版 处理 处理（%s） 保护系统文件 保护系统文件 - 安全 > 设置 > 系统微调 > 系统文件 保护您的站点免受尝试随机猜测您站点的登录详细信息的攻击者。 REST API REST API 认证 原始详细信息 原因 接收邮件更新 将所有 HTTP 页面请求重定向到 HTTPS 将用户重定向到您站点上的自定义位置，而不是抛出 403（禁止）错误。 重定向别名 刷新页面 注册别名 从设置页面的活动锁定部分释放锁定。 在设置页面的禁止用户部分，从禁止主机列表中释放永久主机禁止。 已移除 已移除的文件 需要 SSL 重新安排中 结果 SSL 仪表盘使用 SSL 只保存本地 保存本地和发送邮件 扫描 扫描详细信息 扫描失败 立即扫描文件 扫描性能 扫描摘要 扫描管理文件中… 扫描 content 文件中… 扫描文件中… 扫描 includes 文件中… 扫描媒体文件中… 扫描插件文件中… 扫描主题文件中… 正在扫描... 计划 计划数据库备份 安全 安全检查 安全摘要 安全日志 安全出错！ 选择所有 选择批量操作 选择我们应该如何处理备份文件。您可以通过邮件发送给您，保存在本地或两者。 服务器配置规则 设置 显示所有条目 显示调试条目。 显示详细信息 显示错误代码 显示处理条目。 显示原始详细信息 显示所有条目，包括之前隐藏的条目。 显示更多详细信息 只显示这 %s 的条目 只显示这一天的条目 站点数据库备份为 %s 站点锁定通知 站点锁定 站点：%s 强度指示表 强制强密码 强密码 支持 系统文件 系统微调 排除 WordPress 安全的臆测。iThemes 安全提供 30+ 方法锁定 WordPress 的一个易用的 WordPress 安全插件。 "全局设置" 中的 "写入文件" 设置已禁用。为了使用此功能，您必须启用 "写入文件" 设置。 "写入文件" 设置被禁用。<code>%s</code> 文件的手动配置可在 安全 > 设置 页面中的高级部分找到。 %1$s 邮箱地址列表必须是一个字符串，每个条目用新行分隔。 此 %1$s 值不能为空。 此 %1$s 值不是有效的用户名。 此 %1$s 值必须是正整数。 %1$s 值必须是一个字符串，每个条目用新行分隔。 此 %1$s 值必须是一个字符串。 此 %1$s 值必须是格式为：YYYY-MM-DD 的有效日期。 此 %1$s 值必须是有效的日期。 此 %1$s 值必须是有效的邮箱地址。 此 %1$s 值必须是整数。 %1$s数据库备份%2$s 模块会将任何备份的副本发送到下面列出的邮箱地址。 %1$s文件更改检测%2$s 模块将在检测到更改后通过邮件发送文件扫描报告。 %s 模块是核心模块，无法进行启用或停用。 ITSEC_DISABLE_MODULES 定义已设置。所有 iThemes 安全保护功能均被禁用。请尽可能快地进行必要的设置更改并移除定义。 安全摘要减少了发送的邮件的数量，因此您可以收到锁定和文件更改检测扫描的摘要。 安全摘要可减少发送的邮件数量，因此您可以收到锁定摘要，文件更改检测扫描和权限提升。 您站点的网址。 WordPress salts 已成功重新生成。 此 content 目录不能更改为空白目录名称。 %1$s 的数据验证程序缺失。如果没有验证器，模块的数据将无法保存。这个错误可能表明 iThemes 安全安装不当。请移除插件并重新安装。如果此信息仍然存在，请联系支持人员并向他们发送此错误消息。 参数 direction 的值必须是 "add"，"clear"，或 "remove"。 目录 %s 无法创建，因为具有该名称的文件已存在。 无法创建目录 %s，因为找不到现有的父级目录。 由于禁用了 mkdir() 函数，因此无法创建目录 %s，这是一个系统配置问题。 由于未知错误，无法创建目录 %s。这可能是由于权限问题。 无法保护目录 %s，因为文件列表不存在此目录。 由于 rmdir() 函数已被禁用，因此不能移除目录 %s。这是一个系统配置问题。 %1$s 提供的目录不可写。请选择一个可以写入的目录。 此邮件内容缺失。 文件 %1$s 在发送非整数权限时不能更新其权限：（%2$s）%3$s 由于禁用了 unlink() 函数，文件 %s 无法移除。这是一个系统配置问题。 由于 chmod() 函数被禁用，文件 %s 不能更新其权限。这是一个系统配置问题。 %1$s 提供的文件路径无法使用，因为已经存在，但不是文件。请提供有效的文件路径。 无法创建 %1$s 提供的文件路径。请提供可以写入的文件路径。 %1$s 提供的文件路径不可写。请提供可以写入的文件路径。 %1$s 提供的文件路径已成功创建，但无法更新。请提供可以写入的文件路径。 %1$s 的以下 IP 无效：%2$l %1$s 的以下邮箱地址无效：%2$l %1$s 的以下条目无效：%2$l %1$s 的以下扩展名无效：%2$l 以下是您站点上与安全相关的活动摘要：%s 此 ip 参数丢失。 日志条目迁移失败。重新加载页面以再次尝试。 日志文件位于：<code>%s</code> {{ $site_title }} 的登录地址已更改。新的登录地址是 {{ $login_url }}。您将无法使用旧的登录地址。 当他们的 IP 被 iThemes 网络标记为不良时向用户显示的信息。 在账号被锁定时显示给用户的信息。 计算机（主机）被锁定时显示的信息。 新的目录名称不能是绝对路径。请提供一个与 <code>ABSPATH</code>（<code>%s</code>）相关的路径。 新的目录名称不能与当前目录名称相同。请提供一个新的目录名称。 新的登录链接。 进行数据库备份间隔的天数。 用户在其主机或计算机被锁定在系统之外之前的登录尝试次数。设置为 0 可记录不良登录尝试而不是锁定主机。 用户在其用户名被锁定在系统之外之前的登录尝试次数。请注意，这与攻击者使用多台计算机的情况下的主机不同。另外，如果他们使用您的登录名，您可能会被锁定。设置为 0 可以记录每个用户的不良登录尝试，而不会锁定用户（不建议这样做）。 应该记住不良登录的分钟数。 密码尚未更新。 扫描未能正确扫描该站点。 保留安全日志，因为它们可能需要作为站点折衷分析的一部分。 服务器没有收到有效的请求。提供了一个未知 "方法" 的参数。请重试。 服务器没有收到有效的请求。缺少模块所需 "数据" 的参数。请重试。 服务器没有收到有效的请求。缺少所需 "id" 的参数。请重试。 服务器没有收到有效的请求。缺少所需 "方法" 的参数。请重试。 服务器没有收到有效的请求。缺少所需 "模块" 的参数。请重试。 设置无法保存。由于未知的错误。请尝试刷新页面并重试。 设置无法保存。请更正上述错误并重试。 此设置已保存成功。 当用户尝试访问 wp-admin 而未登录时，将此别名重定向给用户。 提供的邮箱地址 (%s) 无效。需要有效的邮箱地址才能注册 iThemes 的网络暴力攻击保护。 此 updates_optin 的值缺失。 用户更改尚未保存。 用户尚未创建。 %1$s 的有效值为：%2$l。 从网络暴力攻击保护 API 返回错误：%1$s 此邮件是由 iThemes 安全插件代表 %s 生成。 此邮件是由 iThemes 安全插件生成。 这已被禁用。 这是由 iThemes 安全生成的测试文件。可以将其移除。 此路径必须由您的站点写入。为了增加安全性，建议您不要将其包含在您的站点的根文件夹。 时间 时间戳 要取消订阅这些通知，请 %1$s联系站点管理员%2$s。 要取消订阅这些更新，请访问 iThemes 安全插件菜单中的 %1$s设置页面%2$s。 要查看插件内的日志，您必须在全局设置中启用数据库日志记录。文件日志记录不可用于插件本身的访问。 过大而不能显示 总内存 教程 双重身份认证 双重身份认证通过要求登录用户名和密码之外的其他信息来大大提高 WordPress 用户账号的安全性。 类型 网址 由于当前正在创建备份，因此无法在此时创建备份。如果您希望创建额外的备份，请等待几分钟再重试。 由于未知的错误，无法创建备份目录。 无法找到 %s 的有效设置对象。设置无法保存。 无法找到 %s 的有效设置对象。设置无法保存。 无法读取 %1$s，由于以下错误：%2$s 无法读取 <code>wp-config.php</code> 文件以更新 salts。您将需要手动更新文件。错误的详细信息如下：%1$s（%2$s） 无法移除 %1$s，由于以下错误：%2$s 由于未知错误，无法移除 %s。 无法将 <code>%1$s</code> 目录重命名为 <code>%2$s</code>. 这可能表明文件权限问题, 或者您的服务器不支持提供的名称作为有效的目录名称. 配置文件或目录更改未能完成. 无法设置新目录名称（<code>%1$s</code>）的权限以匹配旧目录名称的权限。您可能必须手动将目录的权限更改为 <code>%2$s</code>，以使您的站点正常运行。 由于 token_get_all() 函数被禁用，无法从源代码中去除注释内容。这是一个系统配置问题。 由于 token_get_all() 函数返回无法识别的值，因此无法从源代码中去除注释内容（类型：%s） 无法更新 <code>wp-config.php</code> 文件以更新 salts。您将需要手动更新文件。错误的详细信息如下：%1$s（%2$s） 无法更新 <code>wp-config.php</code> 文件。目录或配置文件的更改未能完成。阻止文件更新的错误如下：%1$s 无法写入备份文件。这可能是由于权限或磁盘空间问题。 无法写入日志文件。这可能表明没有空间可用，存在权限问题，或者服务器配置不正确。 未知 未知联系人 %1$s，%2$l。 收到未知的错误类型：%1$s。 未知计划 %1$s，%2$s。 未知标签 %1$s，%2$l。 更新密码 通过过滤器禁用对 <code>wp-config.php</code> 的更新. 使用颜色来指示每个条目的严重程度。 用户 用户锁定 用户锁定信息 用户锁定：<code>%s</code> 用户记录 用户名 用户名锁定 用户名锁定：<code>%s</code> 只接受用户名 用户名 用户 当用户或主机被锁定在您的站点之外时，各种模块会发送邮件通知您。 查看详细信息 查看日志 视图模式 访问禁止的用户设置 访问设置页面 WP-CLI 命令 WP-Cron 计划任务 警告 警告（%s） 站点 每周一次 每周安全摘要 什么自动化决策和/或分析我们做的用户数据 什么数据违反程序我们已经到位 我们收集的个人数据以及我们收集的个人信息 您对您的数据有什么权利 我们从第三方接收数据 在那里我们发送您的数据 我们与谁分享您的数据 为什么要购买专业版？<a href="%s">查看免费版/专业版比较图表。</a> 借助网络暴力攻击保护，您的站点可以抵御运行 iThemes 安全的其他站点发现的攻击者，如果您的站点识别出新的攻击者，其会自动通知网络，以便其他站点也受到保护，要将此站点加入网络并启用保护，请点击下面的按钮。 WordPress Core %s WordPress 登录地址已更改 WordPress Salts WordPress 微调 写入文件 XML-RPC XML-RPC 服务在此站点上被禁用。 XMLRPC 认证 是 您没有足够的权限来访问此端点。访问 REST API 请求受到 iThemes 安全设置的限制。 由于登录尝试次数过多，您已被锁定。 您必须重新启动您的 NGINX 服务器才能使更改生效。 %s 的每日安全摘要 您的 IP 地址已被 iThemes 安全网络标记为威胁。 %s 的每月安全摘要 您的昵称必须与您的登录名不同。请选择一个不同的昵称。 %s 的安全摘要 %s 的每周安全摘要 您的个人资料尚未更新。 此屏选项已成功保存。 您的站点现在使用网络暴力攻击保护。 [%1$s] %2$s https://ithemes.com https://ithemes.com/security https://wordpress.org/ iThemes iThemes Security iThemes 安全日志 iThemes Security Plugin iThemes 安全设置 iThemes 安全可以以多种方式记录事件，每种方式都有优点和缺点。"仅数据库" 将所有事件放在数据库，包括您的文章和其他 WordPress 数据。这使得检索和处理变得很容易，但如果数据库数据表变得非常大，可能会变慢。"仅文件" 速度非常快，但此插件不会处理日志本身，因为这会占用更多的资源。对于大多数用户或较小的站点，"仅数据库" 应该没问题。如果您有一个非常大的站点或日志处理软件，则 "仅文件" 可能是更好的选择。 iThemes 安全保留了以下设置，因为移除它们可能会阻止站点正常运行。 第 %1$s 页，共 %2$s 页 太多不良的登录尝试 用户尝试登录为 "admin"。 wp-config.php 规则