Many word press errors are warnings or notifications of problems with your site. But this page cannot be accessed. The notice is actually intended to help you. There are many reasons for errors. In most cases, some basic technologies are needed to solve them. After zooming out and resolving the problem, you can immediately recover and run. This post provides 7 ways to correct the failure to access this page. Before that, we will provide more information about what the error is. Unable to access this page. Unlike many other word press errors, you cannot access this page. Notifications do not warn about site problems. The
In fact, for the end user, any changes to the experience may not be displayed. However, you will not be able to access the site until the problem is resolved. This problem is related to a configuration error. As you can see from the notification, user permissions are usually the main reason. With this in mind, you usually find this error after changing the site backend. The update may also be wrong. Sorry, we need to use a tool before we can resolve the failure to access this page. Unable to access this page, there are several tools and elements to work with before correcting the error. The following is a brief summary of what is required: The
The administrator has at least server access to the root directory. SFTP (Secure File Transfer Protocol) clients, such as Cyberduck or FileZilla. Before you begin, you may need to hone your FTP skills. You can use the text or code editor for the site file. The default text editor is usually fine, but a code editor such as atom or notepad++ is a better option. If these elements are still there, it’s time to break the knuckle and jump in! This page cannot be accessed. The following seven ways to correct errors cannot be accessed. Let’s look at seven different ways to correct mistakes. The following is a brief analysis of the methods we will deal with. The
Check the WordPress error log. Please check whether the file permissions are correct. WP config Make sure that the PHP file is not changed. Disable the plug-in to verify that there are no errors. To check for problems, activate the default theme. Birds. Create an htaccess file. Please check the user role. There are many things to be passed. Let’s start! 1. check for clues in the WordPress error log. The first step is to check the error log. You can often find pointers below that help you choose one of the other methods. The
Some hosts provide access to the word press error log through the dashboard. Otherwise, we have a simple solution. First, use the credentials in the managed control panel to access the site through SFTP. Your site is usually located in the public_html or www directory. However, the site name may be in a different folder. After entering, the list of core word press files will be displayed. Male debug here. Navigate to the log file. It can also be in the WP content folder. Unfortunately, if you are not there, you have to go through the other 9 steps below. You can activate debug mode and retest, but you can use the same method to solve the problem. The
When you find it, open it and have a look: you may not understand many parts of the content, but you should confirm whether there is any content related to the recently executed work. If so, you can skip to one of the other related methods described below. 2. check whether the file permissions are correct, and internally check other aspects of the site during the use of SFTP
You can do it. File permissions cannot access this page. This will be the main cause of the error. It is recommended that you check it first. In the SFTP Client, select the WP content, WP include, and WP admin folders. Then right-click to browse to file permission settings. FileZilla has explicit options, but Cyberduck hides the settings in the information panel. The
In the dialog box, if possible, make sure that the following permissions are set: The value is set to 755. You have selected apply to directory only. Recurse selection to subdirectories. When finished, accept the changes, select all other files in the site directory, and then enter the file permissions dialog box again. This time, check the apply to files only and recurse to subdirectory boxes, and set the numeric value to 644. The semantics behind these numbers and options are beyond the scope of this document. However, make sure that valid file permissions are set to allow access to the site. The
Make sure the error disappears. Otherwise, move as follows: 3. WP config Simply put, make sure that the PHP file has no errors WP config. The. PHP file contains all the configuration settings for the WordPress web site. Therefore, it is necessary to ensure that it is not damaged or changed. Right click the file within the SFTP Client and open it in a text editor. Then scan the file for any protrusions. You may not know what you are looking at. In this case, unless you see something strange, it will be all right. File integrity monitoring will be a good supplement to provide security in the future. The
However, remember a setting of this file for later use$ Before finding the table\u prefix setting, WP config. Scroll down the PHP file. Record values here. Often wp_. The following sections will compare this value with the data contained in the phpMyAdmin tool. 4. check whether the plug-in has errors. Considering that the errors we are dealing with are based on user permissions, we recommend that you check the plug-in and the topic. Permissions may have changed due to recent updates. The
In other words, we must use SFTP to be located in your site directory. After entering, please navigate to the WP content folder and browse the plugins directory. Changing the folder name to another name instead of the plug-in can quickly check for problems. After this operation, please check the site for errors. If it disappears, the error is on a plug-in. To continue, rename and open the plug-in folder. Internal directory containing all installed plug-ins. Here, you must change the name of each plug-in folder in turn and check the site for errors. The
Once the problem plug-in is found, a decision must be made. You can delete them together, find alternatives, or consult the developer for modifications. However, if there are no changes to the site, it may be the subject of the problem. 5. like the default theme activation plug-in, recent theme updates may cause site downtime. Fortunately, it is tested almost the same as the plug-in. Summary: browse to the WP content \/ themes folder. Rename and check the front end of the site. If the error disappears, rename the theme folder and view each individual theme until you find the killer. In other words, if the topic is the core of the site and workflow, the developer is required to modify it
Very good. However, finding other suitable topics may be a better choice. Finally, if the error persists, rename the topic folder and go to another step. 6. birds. You can also try restarting and running the site before exiting SFTP to create the htaccess file The htaccess file is the Apache server configuration file, which may be the cause of the problem. To verify, navigate to the root directory of the site through SFTP. If we can get to this point. Browse the htaccess file. If not found, the hidden file or the server (usually nginx) on the host does not exist. For the latter, you can go to another step. But once found, right-click and rename. Htaccess- perfect backup. Then right-click and the file to your computer. Now open the file in a text editor, clear the contents, and add the following code:# Begin WordPress rewriteengine on rewritebase \/ RewriteRule ^index\ Php$- [l] rewritecond%{request\u filename}- F rewritecond%{request\u filename}- D RewriteRule\/ Index Php[l]\end word press this is the default. This is the htaccess file. Save the changes and upload them to the server. Check the site again. If you continue to encounter errors, please continue. 7. the last step to ensure that the user roles and table prefixes are correct is to use tools to access the WordPress database, such as phpMyAdmin, to get rid of SFTP. The database includes almost all the contents of the WordPress site, including user roles. If you make changes in the administrator role, you may not be able to access specific parts of the site. You must be able to access the database tools from the managed control panel, so you must go here. Location varies by hosting provider, but there must be a link. In short, once you enter, please find the database. The name must match the name in the control panel. Next, look at the table, the various entries in the database. All prefixes must be the same. Male recorded the $table\u prefix value in step 3. In phpMyAdmin, WP config is used in other cases. Return to the PHP file and check the site before changing the value and continuing. To continue, click the wp_users table, look up the user name and ID in the list on the right, and record. Next, go to the wp_usermeta table and view the wp_capability row. The user role is displayed in the meta_value field. If anything other than the administrator is displayed, you can click the edit link and change the statement without modifying the surrounding text. Finally, check the site again to make sure the error disappears. The error is that if it still cannot be resolved, the page will not be accessible in the next step. If you are still having trouble solving this problem, you can take several different steps. But each depends on the impact of the error on the site, your access rights, and the access rights provided by the host. In short, there are three ways to solve mistakes. Restore the site from the most recent backup. This can be difficult if the site does not have dashboard access. However, there may be server backups performed by the host. Our suggestion is to confirm and understand with them. Upgrade the PHP version of the server. If recent changes may have had an impact, but have not been implemented directly, there is little chance of this. But the host has upgraded the PHP version
