I had a similar problem recently with this 406 Not Acceptable error occurring when trying to update permalinks in WordPress. I also had the same problem when submitting any changes to the editor, etc. Google Webmaster tools would yield the same result. The solution is to disable the mod_security firewall within your .htaccess file. My … Read more
RewriteRules none in that directory’s .htaccess file should stop mod_rewrite from inheriting WordPress’ rewrite rules.
Most of the time this problem gets solved after flushing the permalinks. By that I mean, one just needs to hit ‘Save changes’ on ‘Permalink settings’ page on backend. However you said that you tried pretty permalinks and its not working. Under “Settings > General”, please confirm that you have updated “WordPress Address (URL)” and … Read more
The E flag is being used for LiteSpeed as opposed to ENV for Apache. Where did you get this from? The LiteSpeed docs appear to show that LiteSpeed is the same as Apache in this respect and require env=, not E=, on the Header directive in order to conditionally set the HTTP response header based … Read more
Your server does not have mod_rewrite enabled Or you do not have AllowOverride set correctly to allow your .htaccess file to operate correctly. You will need AllowOverride set to at least FileInfo. I’d bet on the latter, as mod_rewrite is pretty ubiquitous. Based on your edit, the issue is that Nginx doesn’t use .htaccess files. … Read more
Your URL http://domain.com/server should work without problems. Most likely you have activated an HTTPS redirection for your website. You should check: If you have a security or other type of plugin that forces the HTTPS redirection and deactivate the redirection. (Most likely they will edit your .htaccess file in order to force the HTTPS) Check … Read more
I would recommend to define this constant in your wp-config.php to force HTTPS on admin: define(‘FORCE_SSL_ADMIN’, true); Also, there is a function called is_admin() which could be helpful in your case. if ( is_admin() ) { $_SERVER[‘HTTPS’] = ‘on’; } However, if you have a rule in your web server forcing all wp-admin and wp-login.php … Read more
It appears that you don’t have the mod_rewrite module enabled in apache. This explains why you can access the dashboard found at wp-admin/index.php, but not the main index.php. Your .htaccess is depending on the rewrite module to do its work, which isn’t active. To enable it in your http.conf file you need to find the … Read more
Assuming you have already changed the permalinks structure as @RickHellewell suggests, then you can do something like the following near the top of your .htaccess file (before the existing WP front-controller) to redirect the old URLs (with the stated format) in order to preserve SEO. RewriteRule ^\d{4}/\d\d/([a-z-]+\.html)$ /$1 [R=301,L]
If you want your WP site to function completely in subfolder, just set it up there as usual (including .htaccess) and do not add any directives to the root. Setup of .htaccess in root, while WP is in subfolder, is only necessary if you want to have core files (and so admin area) there, but … Read more