Title: The loopback request returned an unexpected status code 400 Last modified: June 19, 2018 --- # The loopback request returned an unexpected status code 400 * [binaryfabric](https://wordpress.org/support/users/binaryfabric/) * (@binaryfabric) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/) * Hey Guys, * Im getting a weird loopback error: **The loopback request returned an unexpected status code 400** * That error comes from the Health Check plugin v.1.1.0 in troubleshoot mode. * Ive seen that lots of people have been getting the errors when trying to save PHP files with the editor, and I have been getting the same(CSS works, but I understand they are saved differently). Upon further investigation I have unable to find a solution for the 400 error. * While in troubleshoot mode the issue still happens with no plugins active (Still getting the 400) * Here is a copy of the health log (Ive edited some sensitive info): * ``` ### WordPress ### Version: 4.9.6 Language: he_IL Permalink structure: /%postname%/ Is this site using HTTPS?: Yes Can anyone register on this site?: Yes Default comment status: closed Is this a multisite?: No User Count: 2 Communication with WordPress.org: WordPress.org is reachable Create loopback requests: The loopback request returned an unexpected status code, 400, this may affect tools such as WP_Cron, or theme and plugin editors. ### Installation size ### Uploads Directory: 32.54 MB Themes Directory: 19.10 MB Plugins Directory: 64.57 MB Database size: 25.08 MB Whole WordPress Directory: 144.65 MB Total installation size: 169.73 MB ### Active Theme ### Name: Twenty Seventeen Version: 1.6 Author: the WordPress team Author website: https://wordpress.org/ Parent theme: Not a child theme Supported theme features: automatic-feed-links, title-tag, post-thumbnails, menus, html5, post-formats, custom-logo, customize-selective-refresh-widgets, editor-style, starter-content, custom-header, widgets ### Other themes (2) ### Binary Fabric Child (binaryfabric-ultra-child): By Binary Fabric Themify Ultra (themify-ultra): Version 2.0.1 by Themify ### Must Use Plugins (1) ### Health Check Troubleshooting Mode: Version 1.4 ### Active Plugins (1) ### Health Check: Version 1.1.0 by The WordPress.org community ### Media handling ### Active editor: WP_Image_Editor_GD Imagick Module Version: Imagick not available ImageMagick Version: Imagick not available GD Version: 2.1.1 Ghostscript Version: Not available ### Server ### Server architecture: Linux 4.4.0-1060-aws x86_64 PHP Version: 7.0.30-0ubuntu0.16.04.1 (Supports 64bit values) PHP SAPI: apache2handler PHP max input variables: 1000 PHP time limit: 30 PHP memory limit: 512M Max input time: 60 Upload max filesize: 256M PHP post max size: 20M cURL Version: 7.47.0 OpenSSL/1.0.2g SUHOSIN installed: No Is the Imagick library available: No htaccess rules: Your htaccess file only contains core WordPress features ### Database ### Extension: mysqli Server version: 5.6.39-log Client version: mysqlnd 5.0.12-dev - 20150407 - $Id: b5c5906d452ec590732a93b051f3827e02749b83 $ Database prefix: wp_ ### WordPress Constants ### ABSPATH: /var/www/html/ WP_HOME: Undefined WP_SITEURL: Undefined WP_DEBUG: Disabled WP_MAX_MEMORY_LIMIT: 512M WP_DEBUG_DISPLAY: Enabled WP_DEBUG_LOG: Disabled SCRIPT_DEBUG: Disabled WP_CACHE: Disabled CONCATENATE_SCRIPTS: Undefined COMPRESS_SCRIPTS: Undefined COMPRESS_CSS: Undefined WP_LOCAL_DEV: Undefined ### Filesystem Permissions ### The main WordPress directory: Writable The wp-content directory: Writable The uploads directory: Writable The plugins directory: Writable The themes directory: Writable The Must Use Plugins directory: Writable ``` - This topic was modified 7 years, 12 months ago by [binaryfabric](https://wordpress.org/support/users/binaryfabric/). Viewing 6 replies - 1 through 6 (of 6 total) * Moderator [Marius L. J.](https://wordpress.org/support/users/clorith/) * (@clorith) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10416249) * Hiya, * In this case I would reach out to your hosting provider actually, I can see that you are hosted with AWS, and they have a loadbalancer in place which appears to be stripping the loopback requests, and treating them as malformed (and thus discarding the requests). * Without knowing the configuration etc of this setup, it’s not possible for us to give good advise beyond this unfortunately, but your host should be able to figure things out in a reasonable time. * [edwardyves2](https://wordpress.org/support/users/edwardyves2/) * (@edwardyves2) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10416298) * We used AWS and never had that issue what you are having. * Either you have a permission issue or something else. * You should used the last backup of database (wordpress) for your website. Uninstalled the current version and reinstall a new version of wordpress. Then upload your backup database and that should fixed the issue. * Thread Starter [binaryfabric](https://wordpress.org/support/users/binaryfabric/) * (@binaryfabric) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10416507) * Do you guys know what the URL for the loopback request is? Does it happen on a certain port, does it happen on HTTP or HTTPS. * I would like to debug the issue a little bit, before I open up a support request. * Also on this specific server config, i do not have a load balancer setup, weird that you see that. * Thank you, - This reply was modified 7 years, 12 months ago by [binaryfabric](https://wordpress.org/support/users/binaryfabric/). * Moderator [Marius L. J.](https://wordpress.org/support/users/clorith/) * (@clorith) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10417339) * AWS generally sites behind a load balancer, it’s how you can scale up/down on the fly, I’m unable to see if you ahve one right this instance but it’s less likely than not. * The loopbacks are requests to your websites front page, and to the wp-admin page you are currently viewing, made using the URL you are currently using (so https if you are using https etc), they are essentially a dummy connection the website makes to it self to trigger events, and check that it’s still accessible and that the changes you made won’t break everything. * Thread Starter [binaryfabric](https://wordpress.org/support/users/binaryfabric/) * (@binaryfabric) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10419886) * So I just wanted to update… Maybe this is 1. A Bug or 2. An issue on my end. * When I add the sub-domain www to **WP_HOME** & **WP_SITEURL** the loopbacks work. * `Loopback request: The loopback request to your site completed successfully.` * This isn’t necessarily a huge problem if I need to leave it like this, but any idea on where I can go from here? * Maybe something in my Route 53 Settings? * Moderator [Marius L. J.](https://wordpress.org/support/users/clorith/) * (@clorith) * [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10423331) * I’m afraid I don’t know, but it sounds like there might be rules in place that allow certain domains through, I honestly can’t say for sure though. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘The loopback request returned an unexpected status code 400’ is closed to new replies. ## Tags * [loopback](https://wordpress.org/support/topic-tag/loopback/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 6 replies * 3 participants * Last reply from: [Marius L. J.](https://wordpress.org/support/users/clorith/) * Last activity: [7 years, 12 months ago](https://wordpress.org/support/topic/the-loopback-request-returned-an-unexpected-status-code-400/#post-10423331) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics