Today, I met a netizen who mentioned that an error prompt of "405 Not Allowed" appeared on his website. Of course, it can be used before. I don't know which file to modify during operation and maintenance. In general, the 405 Not Allowed problem may be caused by the Nginx engine server, which causes the URL pseudo static problem when it is pseudo static. Here we need to check the pseudo static or Conf file configuration problem. Here, after I get his website server, I refer to other websites again in the configuration file to configure WordPress as pseudo static and restore the conf configuration file.
If it still fails, we can recompile the Nginx engine, uninstall and reinstall it. The final solution is that when he modifies the cache, he has moved the conf file configuration, causing the static settings to become invalid. Here we restore it to the original initial stage. It is his own problem which cache he uses later.
Scan the code to follow the official account
Get more news about webmaster circle!
Entrepreneurship, operation and new knowledge