Using uninitialized "redirecttoindex" variable - wordpress

Suddenly out of nowhere I can not log in into my WordPress site. The site is working but wp-admin is not. In the error log I get:
2022/07/04 23:45:58 [warn] 31793#31793: *300658 using uninitialized "redirecttoindex" variable, client: ip.000.000.000, server: mydomain.com, request: "GET /wp-admin/HTTP/2.0", host: "mydomain.com"
How can I debug this? I have just got this site for maintenance and I am not very familiar with WordPress. Should I diff it with the original version and see if files are modified?
I scanned the code and there are no redirecttoindex variables. Is something up with nginx?
I also can not find anything on google with such a query.
Server API: FPM/FastCGI
PHP Version 7.4.26
nginx/1.20.2

You confirm the other pages in the sites this working well ? If the answer is Yes, you need the check if exists some plugin what redirect the route of wp-admin for new route. First we have to activate the debug mode in the wordpress in the file wp_config find de const WP_DEBUG and set true.
P.S: Don´t activate the DEBUG in the product view.

Related

Apache to Litespeed Wordpress Migration

I’m hoping I can find some help here. I have setup cyberpanel/litespeed and I’ve migrated my Wordpress site using Duplicator over from an Azure App Service (Apache based server). Since I’ve migrated over to Litespeed, I have been inundated with errors all over the site, most of them include these two:
Uncaught Error: Call to undefined method …
Parse error : syntax error, unexpected ‘endforeach’ (T_ENDFOREACH)
Why would my site run seamlessy on Apache, but after migration all these errors are produced? Is there some kind of configuration I need to do?
Here are the server details:
Apache Server: PHP Version 7.4.26
Litespeed Server: PHP Version 7.4.29
Any help is appreciated.
Many thanks
Kahl

Directory Forbidden Neat Bourbon in Wordpress Editor

We are creating a theme on Wordpress that makes use of Neat Bourbon. On the frontend everything works great. On the backend we are trying to display the content the way it will look so we also call Neat Bourbon. Our issue is Neat bourbon throws an error in nginx that the directory is forbidden. This is the only directory showing this error.
[error] 11438#0: *290 directory index of "/var/www/wp-content/mu-
plugins/folder/bower_components/neat/core/neat/" is forbidden, client:
XX.XX.XX.XXX, server: www.example.com, request: "GET /wp-content/mu-
plugins/folder/bower_components/neat/core/neat/ HTTP/2.0", host:
"www.example.com", referrer:
"https://www.example.com/wp-admin/post.php?
post=1318&action=edit"
Permissions are all the same:
List of folders and their permissions
Any help would be greatly appreciated.
Seems like your GET url is incorrect. The last neat is a sass file and not a directory.
Depending on how you are running your imports, the path should be one of the following.
/wp-content/mu-
plugins/folder/bower_components/neat/core/neat
/wp-content/mu-
plugins/folder/bower_components/neat/core/_neat.scss
See: https://github.com/thoughtbot/neat/blob/master/package.json#L28

Moving Wordpress website to another server

A friend of mine asked me to move wordpress website from development server to production. I've copied all the files, backed up and restored database. After that I'd changed sitename and home values in database (_options table) to new domain and it started. Though only home page is working fine. When I navigate to any other page it gives me 500 error. In error_log I got following errors:
1423021301: /home1/crankst1/public_html/fish-dev-site/ssv3_payload_extractor-r0Xkqq2xFD.php startup
[24-Feb-2015 19:16:59 UTC] PHP Warning: require_once(/home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/include/classes/core/class-vc-sort.php): failed to open stream: No such file or directory in /home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/js_composer.php on line 168
[24-Feb-2015 19:16:59 UTC] PHP Fatal error: require_once(): Failed opening required '/home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/include/classes/core/class-vc-sort.php' (include_path='.:/usr/php/54/usr/lib64:/usr/php/54/usr/share/pear') in /home1/crankst1/public_html/fish-dev-site/wp-content/plugins/js_composer_theme/js_composer.php on line 168
Paths that cause errors are related to development server and I can't find where to change them. I'm not very good with wordpress, so I suppose that solution should be very simple.
I'm sure there is an issue with a plugin http://codecanyon.net/item/visual-composer-page-builder-for-wordpress/242431/comments?page=149 try to see if there are any hardcoded paths on the plugin dashboard.
Delete your .htaccess file then go to the permalinks page change to another permalink type save page then change back to permalink you had this will force wordpress to recreate the .htaccess file and it will allow all pages you have to show correctly on the site. :-)

Symfony2.5.0 fresh install - No route found for "GET /", 404 Not Found - NotFoundHttpException

Hi I am new to symforny2
I have just installed symfony2 on my easyphp server. When I open web directory symfony try to open app.php. For some reason I got this output:
No route found for "GET /"
404 Not Found - NotFoundHttpException
1 linked Exception: ResourceNotFoundException »
[2/2] NotFoundHttpException: No route found for "GET /" +
[1/2] ResourceNotFoundException: +
Logs -
Stack Trace (Plain Text) +
When I open app_dev.php, everything looks normal.
Why do I get this 404 error on app.php ? Is that normal or is this a bug in symfony2.5.0
(demos in app_dev.php are working well)
Thank You for your support.
Regards
See one of my previous answer: symfony2 - how to switch from "dev" to "prod"?
Symfony wraps multiple environment. When you access the app.php front controller, you're on the prod environment whereas when you access app_dev.php, you're on the dev environment.
Knowing that, the demo bundle shipped with the standard edition is only enable on the dev environment according to the AppKernel. So, it is normal you can access the demo page on the dev front controller and get a 404 on the prod front controller.

Apache 2.2.16: client denied by server configuration

I have problem with my server configuration. I use Apache 2.216, PHP 5.3.3 and wordpress 3.4.2 with Shopperpress. Time to time I receive error "client denied by server configuration: path/to/file" in apache log file. It is path to _tbs.php file, but it is not problem in rights of file, because this file is called 12 times on page for getting thumbs of photos and there is error only several times. I think that it has no connection to concrete photo, because once this photo is displayed corectly and next time same photo produce error.
Do you have any idea what can be reason?
Thank you for all advices.
Viktor
I think thats a problem by the configuration of MaxClients or MaxRequestsPerChild.
Try to restore the default configuration and try it again. If that not works, reinstall Apache and purge the old configuration.
You have given very little information. It is not clear under what conditions do you work (OS, installed modules, Log entrys,...).
WordPress 3.4.2 is very old and safety-relevant. Please update WordPress and your WP-Plugins.
Go to you VHOST-file and replace:
Deny from all
Allow from 127.0.0.0/255.0.0.0
with:
Require all granted
This cause for old Config-Files and newer Apache-Version. Since Apache 2.4.3 a new security feature is added.

Resources