Cornerstone editing error after updating WP

Support
#1

Hi,

I am experiencing this type of error once i am about to create or edit a page using cornerstone.

Stated:
"A conflict on the front end of your site has prevented the preview from loading."

I am suspecting the error came after updating WP.

Also another error is in the media library where no images i uploaded are being showed.

Hope somebody can help… tried updating other pluggin but doesn’t fixed the issue…

#2

Hi there,

Thanks for writing in.

It could be your hosting environment issue, but I’m not sure. Would you mind providing your URL, admin, and FTP login credentials in a secure note.

I like to gather information first to determine if it’s theme or plugin related, else, you’ll have to contact your hosting.

Thanks!

#3

Hi there,

Please provide the admin login credentials as well, that’s the most important :slight_smile:

Thanks!

#4

Hi Sir, sent to you on secure note…

#5

Hi There,

Upon investigating this issue further, I see 500 internal server error when performing actions on your site. For example, when trying to install a new plugin or updating a new plugin.

Could you please contact your hosting provider and ask them to check the error logs for you.

Thanks!

#6

Hi Sir,

We’ve got some response from the hosting support and here’s a thing they need;

"I do see a number of 500 errors under that domain, mostly related to ModSecurity. So that I don’t whitelist an actual threat, may I have the theme developer’s IP address so I can whitelist only the safe items? Thank you!

Regards,
Josh Escobedo"

#7

Hi There,

Please ask them to white-list any request to the domain theme.co. Server IP: 34.199.208.181

Thanks!

#8

Hello,

the hosting support responded from the Server IP given, please check below:

"Hello,

I found no matches for those IPs. ModSecurity is a web application filter which observes incoming requests and matches them against known attack signatures. The IPs that get logged are the end user’s IP. I can best resolve the issue if I can duplicate the errors, or have the IP address of an end user that’s triggered them.

It’s also possible that the issue isn’t related at all to ModSec, and that the errors I found for the domain are entirely legitimate attack interceptions.

If you can send me appropriate login credentials, I’d be happy to try an update to trigger the issue myself and view the logs in realtime."

#9

Hello,

thanks for the help. Upon checking, i think all is working fine now with the web.

#10

Glad this is not sorted our Marc!

Cheers.