This issue again. At the risk of being redundant, I am just going to create a secure note with login credentials to my site. There are too many posts about this, and too many variables to ever thread the needle to a solution.
And yes, I’ve tried.
Hi there,
Unfortunately, the given URL/User/Pass is not working for us. WOuld you please kindly double check and see if it is ok?
It can be caused by several reasons which you need to rule out one by one for your environment. Please kindly follow the steps mentioned in the article below:
In addition please make sure that the PHP memory limit is enough to operate the website and the theme. To change the PHP memory limit please kindly read the article below:
https://theme.co/apex/forum/t/troubleshooting-customizer/196 (Not Working or Showing a White Screen section.)
You may need to contact your hosting service provider for some of the steps mentioned above.
Thank you.
Thanks Christopher.
- The memory has been updated in the php file, with the addition of the second line; the first was already present.
- Cloudflare has the exceptions for /x/ added with a cache level bypass and performance disabled as per the notes above, and additional instructions found here: https://xthemetips.com/using-cloudflare-rocket-loader-with-x-pro-and-x5/928/
The error is now only occurring in Chrome and Firefox - Safari is working as expected (which seems odd).
I will update the login details in a private note.
note: clicking on that url doesn’t take me to the intended location; it appears that the forum is rendering the link strangely
Hi there,
It’s because of CloudFlare, I still can see that your added page rules are not in effect. Please provide your CF login credentials in a secure note and I’ll check what you added.
Thanks!
Hi there - adding a secure note. I should add that from what I can see in CF, this isn’t an issue (I can see the records in CF)
It’s important to add that I am also having the same issue on a staging server on WP Engine that has no caching enabled at all. The login credentials for that website are the same as previously supplied. The URL is http://livingnow1.staging.wpengine.com
The attached screenshots show what I see when attempting to use Cornerstone on the staging site. The first image is what we see on the first effort (note the preview in the background). The second image shows what we get once we click ‘try again’.
Hi there,
I added the correct page rules in your CF, and you may delete the other page rules.
*livingnow.com.au/x/*
*livingnow.com.au/*cornerstone*
Now I don’t see CF and RocketLoader in the builder sides. And upon more checking, the preview of the builders is loaded in HTTP instead of HTTPS (Your staging is inaccessible and I can’t test it). And it could be due to your hosting’s internal cache + multi-site. The builder only uses the URL supplied by the system, and then because the browser will not allow the mix of HTTP, HTTPS, or External URL then the browser will block the request.
Would you mind contacting your hosting provider to make sure all URLs including the one in cache uses HTTPS? Plus, maybe switching to staging retains the same URL, example the http://example.staging.wpengine.com/ still loads the https://example.com.au which also the browser can’t allow/
Thanks!
Thanks for the detailed response.
I’m not entirely sure what you’re saying, however. I have deleted the additional page rules from CF and left yours in place.
WP Engine has confirmed that the entire domain, with the exception of some mixed content we need to resolve (images) is running on a secure certificate.
What else can you recommend?
We have SSL setup at WP Engine, Cloudflare, and a shared certificate on KeyCDN
Hi there,
It’s not just because of images if you’ll check the error, it says
Mixed Content: The page at 'https://livingnow.com.au/x/#/content/22251/layout/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://livingnow.com.au/'
It means in the preview (which the builder is loaded through HTTPS) is loading the HTTP version of the page. Hence, resulting in a mixed content issue that browsers blocked.
How about turning off HTTPS first from all the places you set them up (eg. WP Engine, Cloudflare, and a shared certificate on KeyCDN ) ? Just need to test it with its clean setup to narrow down the specific cause of this.
Thanks!
HI there - we have now resolved this issue.
Glad this is now sorted out for you.
Cheers!