“POST /wp-admin/admin-ajax.php HTTP/2.0” 404

Viewing 15 replies - 1 through 15 (of 15 total)
  • Moderator threadi

    (@threadi)

    1 year, 3 months ago

    404 means that the destination does not exist. If the URL (incl. domain) is actually correct, I would rather guess that the file is missing. Go to Updates in the backend and reinstall the core.

    If that doesn’t help, you can also try a manual update: https://wordpress.org/documentation/article/updating-wordpress/#manual-update

    If that doesn’t help either, a security tool (a firewall?) in your hosting might prohibit access.

    Thread Starter Jim Garrigan

    (@garrigan)

    1 year, 3 months ago

    The file does exist as demonstrated by the log entries with status “200”. The log entries show “200” until the last entry which shows “404” That “404” log entry is generated when I exit from the customize screen. I will be away from the Internet until Sunday afternoon (GMT – 4).

    Moderator threadi

    (@threadi)

    1 year, 3 months ago

    The log is formatted in such a way that it is somewhat difficult to read here. You are welcome to use the code block next time: https://wordpress.org/support/forum-user-guide/block-editor/#code-block

    In the event of an incorrect request, the AJAX interface would respond with a 400. I don’t see a 404 at this point in WordPress. Depending on what was requested there, it could of course also be the return of a plugin you are using. Deactivate all plugins and use a standard theme (TwentyTwentyOne is the last classic theme with customizer support).

    Thread Starter Jim Garrigan

    (@garrigan)

    1 year, 3 months ago

    I had conducted a test without any installed plugins. The issue existed.

    I put the posted log file entries into a code block as shown below.

    The last entry has the 404 response.

    Oct 17 17:39:43 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:43 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 611 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:43 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:43 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 660 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:43 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:43 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 611 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:49 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:48 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 611 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:49 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:49 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 611 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:49 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:49 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 660 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:49 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:49 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 611 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:39:49 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:39:49 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 660 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:40:02 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:40:01 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 37 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:40:03 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:40:03 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 6104 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:40:07 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:40:07 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 37 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:40:11 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:40:11 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 138 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:40:24 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:40:24 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 200 155 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    Oct 17 17:40:33 vm_hostname nginx: 2001:xxx:xxxx:x:xxxx:xxxx:xxxx:c6cc – – [17/Oct/2024:17:40:33 -0400] “POST /wp-admin/admin-ajax.php HTTP/2.0” 404 67 https://staging.mydomain.com/wp-admin/customize.php “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0” “-” staging.mydomain.com “POST https://staging.mydomain.com/”
    • This reply was modified 1 year, 3 months ago by Jim Garrigan.
    • This reply was modified 1 year, 3 months ago by Jim Garrigan.
    Thread Starter Jim Garrigan

    (@garrigan)

    1 year, 3 months ago

    I deactivated all the plugins, and I used the theme (TwentyTwentyOne. The same issue occurs.

    Thread Starter Jim Garrigan

    (@garrigan)

    11 months, 3 weeks ago

    Hi,

    What is the status please?

    Thank you

    Thread Starter Jim Garrigan

    (@garrigan)

    11 months, 2 weeks ago

    Feb 20 11:14:46 vm_hostname 2/20/2025 11:14:46 [error] 8523#8523: *70 FastCGI sent in stderr: PHP message: PHP Warning: Array to string conversion in /data-path/wp-includes/formatting.php on line 1096 while reading upstream, client: 2001:XXX:XXX:0:XXX:XXX:XXXX:XXXX, server: staging.mydomain.com, request: GET /wp-admin/customize.php HTTP/2.0, upstream: fastcgi://unix:/run/php-fpm/www.sock:, host: staging.mydomain.com, referrer: https://staging.mydomain.com/wp-admin/admin.php?page=neve-welcome

    Thread Starter Jim Garrigan

    (@garrigan)

    11 months ago

    https://core.trac.wordpress.org/ticket/63066

    Dennis Snell

    (@dmsnell)

    5 months, 4 weeks ago

    @garrigan if you add the lines mentioned in the Trac ticket to the top of the wp_check_invalid_utf8() function inside wp-includes/formatting.php, then repeat the issue that caused the 404, then it should print the data on the webpage somewhere (and this will likely be messed up. if you want, do this instead var_dump( "<plaintext>" ); var_dump( $text )) and it should still break the displayed page but be easier to see the output.

    the Error should produce a log message in the same place you saw the error above.

    Here’s a big warning though: don’t do this on a production site. Only do this is you are able to test the changes without interruption your own site or someone else’s.

    Thread Starter Jim Garrigan

    (@garrigan)

    5 months, 4 weeks ago

    Hi Dennis,

    Thank you – My background is in IT, but not this area. I supported Windows-based on-premises servers.

    I am on the same page. 😊

    I have test environments. I did work with folks who had no concerns with testing on live, AKA production, systems.

    Jim

    Dennis Snell

    (@dmsnell)

    5 months, 3 weeks ago

    @garrigan here’s a more complete patch to apply to see the errors. if you make this change, it should show the output on the rendered page in the browser and you should be able to copy/paste it from your browser to here to show the full error and stack trace.

    function wp_check_invalid_utf8( $text, $strip = false ) {
    	if ( ! is_string( $text ) ) {
    		echo "<plaintext>";
    		var_dump( $text );
    		echo "\n\n\n------------\n\n\n";
    		var_dump( debug_backtrace() );
    		die();
    	}

    	$text = (string) $text;
    	...
    }

    Thanks for your diligence in getting this information. It’s just a bit thorny trying to dig through what I think might be the server access logs

    Thread Starter Jim Garrigan

    (@garrigan)

    5 months, 3 weeks ago

    Hi Dennis,

    Thank you

    Thread Starter Jim Garrigan

    (@garrigan)

    5 months, 3 weeks ago

    Hi Dennis,

    I was not able to “see” the customizer. I did see the messages from your “patch”.

    I changed to a very simple NGINX configuration.

    I am still seeing the 404 error.

    I will repeat the steps with a different “patch”.

    Dennis Snell

    (@dmsnell)

    5 months, 3 weeks ago

    @garrigan I believe that the 404 is known and pointed out twice in the linked Trac ticket. You can watch Core-54435 if you want to be notified of updates on that one.

    I’m afraid I’m going to be limited in how much I can help you diagnose your particular issues, but maybe someone else with more helpful skills can help you figure this out. That being said, I’ll see updates here so if I notice something that makes sense I can jump in.

    Thread Starter Jim Garrigan

    (@garrigan)

    5 months, 3 weeks ago

    Hi Dennis,

    Thank you for providing assistance.

    I found plenty of other issues with WordPress …

    The importer / exporter has issues. The xml file fills itself with duplicate entries …

    With version 6.8, some images are not properly ingested into the media library. https://core.trac.wordpress.org/ticket/63708

    • This reply was modified 5 months, 3 weeks ago by Jim Garrigan.
Viewing 15 replies - 1 through 15 (of 15 total)

You must be logged in to reply to this topic.