bradkamradt

Turns out this is 100% related to my host’s web application firewall. Currently working with them on an IP-based whitelist/exclusion solution for admin-ajax.php and a couple of other files that we’ve discovered are also being blocked. Thanks for the help and input!

AND MORE:

This really does seem to be specific to the “Insert image into post action.”

Here’s a screenshot of that shows what I believe are two unsuccessful image insertion attempts (404s) mixed with normal “heartbeat” activity (200s).

https://drive.google.com/file/d/0B45kVJQNbZhoNTM3M0JsbUNiWkk/view?usp=sharing

Seriously, WTF?!?!?!?

FOOTNOTE: Compounding this mystery is that I have an already established WordPress multisite instance on a second, supposedly identical server where I do NOT have this issue.

Is it possible this has to do with starting fresh using 4.7.3 for these most recent sites whereas the fully functional instance was launched some time ago and upgraded?

Can’t change hosting due to organizational constraints.

Just created a new account on the server and built up a fresh WP install. Tested image insert. All was well. Converted to multisite. All was well. Created first subsite in the network and I’m back to ajax-admin.php being 404 not found within that subsite when I try to insert an already uploaded image into a page or post.

Still wonder if this is because the WP install is looking for admin-ajax.php at https://dev.www.nau.edu/insert-test1/wp-admin/admin-ajax.php instead of https://dev.www.nau.edu/wp-admin/admin-ajax.php. Even if that’s the case, I still don’t know how to fix the problem.

Any other ideas out there? I’m in a real jam here and need a solution ASAP.

Still having this problem where images cannot be inserted using WYSIWYG/GUI in, pages and posts. May not actually be a multisite issue — I set up a fresh single-site install and am now experiencing the same issue there.

I’m going to reach out to our host and see if they’re perhaps blocking access to admin-ajax.php due to excessive calls or related high CPU usage. Still have no idea what’s actually going on here or how to fix it.

??

We have a VPS arrangement. This particular website will be used for training, and needs to mirror a WordPress course via Lynda.com to the extent possible.

I just tested in an already established multisite instance with the same hosting environment, and everything works as it should. Methinks it’s time to try a fresh install to see if this problem is replicable.

Thanks, Fairy-Rider, for the input!

Yes, still having trouble. Adding/uploading media to library is not the problem. Inserting into a page or post still is due to that 404 not found error.

Good idea re: reinstalling WordPress. Just did that but unfortunately have same poor results.

I’m still left feeling like the issue to be addressed is the inclusion of the site slug in the path to admin-ajax.php. Just not sure how to correct for that.

Tempted to blow away this instance entirely and reinstall WP and multisite from scratch. Don’t want to go there unless we’re at the end of the road re: other options.

Appreciate your time and input so far, Fairy Rider!

Ah, I see. Looks like you may have uploaded a WAV file. Problem may be specific to images?

And were you able to successfully insert media? When we try, nothing happens and console indicates that admin-ajax.php isn’t found: https://drive.google.com/file/d/0B45kVJQNbZhoRW5PUHhVVFBUTFU/view?usp=sharing

Steps to reproduce:

1) Head to sandbox.www.nau.edu/wp-signup.php
2) Create a user account and site for yourself (blocking search-engine traffic, please)
3) Open console and get ready to see error(s)
4) Try to add an image to a page or post on your site using “Add Media” and “Insert into…”
5) admin-ajax.php will show up as 404 not found, presumably due to your site slug being inserted in the path to admin-ajax.php

THANKS!

• This reply was modified 8 years ago by bradkamradt.

Site is at sandbox.www.nau.edu. Appreciate the thought re: workaround, but that may not give us what we need since it doesn’t match training materials we have access to from Lynda.com. Hoping there’s a non-core way to remove the /SITEURL/ from the admin-ajax.php file path that currently yields 404 error. Or rewrite via .htaccess. Or something. Thoughts? THANKS SO MUCH!

Still looking for ideas and/or solutions on this. THANKS!

(Sorry, just realized I should not have bumped this. Don’t seem able to delete it.)

• This reply was modified 8 years ago by bradkamradt.
• This reply was modified 8 years ago by bradkamradt.