• Resolved Lalit Jindal

    (@lalitjindal)


    Hi guys,

    I’m getting this error in the customizer. The URLs are set correctly in general settings.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hey @lalitjindal

    Do you happen to know if your hosting has enabled mod_security on your end? Also, noticing that you’re running Hummingbird, can you try disabling it so we can rule out if they’ve started “optimising” the backend, just like another popular caching has started to do and cause problems.

    Thanks.

    Thread Starter Lalit Jindal

    (@lalitjindal)

    I don’t know about mod_security. I’ll ask them.

    I’ve tried disabling Hummingbird, that doesn’t work. Neither does switching themes so It’s not a theme related problem.

    Thank you.

    • This reply was modified 4 years, 2 months ago by Lalit Jindal.

    Hey @lalitjindal

    Oh, if you’ve tried switching themes and the effect still occurs, then it is most likely a server configuration issue. I would recommend getting in touch with your hosting’s support representatives and asking about mod_security, as it’s been one of our biggest offenders yet. I would recommend completely disabling mod_security.

    I know this sounds a bit fishy, disabling something called “security”, but it’s actually for the best, as the module has stopped receiving support from their creators — https://www.modsecurity.org — and nobody knows what will happen to it, as the project has been open sourced. This can go horribly wrong or perfectly good, but it’s not up to us.

    Thanks.

    I still don’t know the cause and the solution of the problem, but I have found a patch, a solution. It is not ideal because the problem is reproduced again but while.

    It is simply a matter of reinstalling wordpress, in the update panel reinstall the same version that is installed.

    I think the problem has something to do with the API REST, because when it fails in the health of the site it also indicates that it has found a problem with the API_REST. When reinstalling the WP that alert disappears

    Hi @amanida

    Hmm… from the sounds of it, it might be something on the server end that’s blocking this. Have you tried checking this out with the hosting provider? They should be able to access all of the logs and check out what’s happening. This is usually something on the server side that’s blocking things.

    Hope this helps and let us know about your findings! 🙂

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Non-existent changeset UUID.’ is closed to new replies.