|
Kevin Brooks
|
May 1, 2014 at 2:21 pm
In Firefox, I get: “This registration step could not be completed. Please refresh the page and try again.” when attempting to register.
I’ve narrowed this down to Firefox blocking non-HTTPS content on the registration page – specifically the call to /wp-admin/admin-ajax.php
Is there a way to make this call on HTTPS when HTTPS is being used instead of HTTP?
|
|
Lorenzo Orlando Caum
|
May 1, 2014 at 2:28 pm
Hi Kevin,
Are you using a plugin like WP HTTPS to force SSL?
Also, does this happen on the registration checkout page? If so, could you share a link?
—
Lorenzo
|
|
Kevin Brooks
|
May 1, 2014 at 2:40 pm
We are using WordPress HTTPS and this is happening on the registration checkout page. This is a good example page: http://www.ceimaine.org/workshops-and-events/owning-managing-residential-properties-hoe-7634/
Checkout is fine in Chrome, but it seems less sensitive to non-HTTPS connections.
|
|
Lorenzo Orlando Caum
|
May 1, 2014 at 3:04 pm
Thanks for that link. Are you running WordFence or any other security plugins?
—
Lorenzo
|
|
Kevin Brooks
|
May 1, 2014 at 3:08 pm
Yes, I do have WordFence running, as well.
|
|
Lorenzo Orlando Caum
|
May 1, 2014 at 4:42 pm
Hello,
Could you try temporarily deactivating that plugin or adjusting the security settings to see if the blocked resource issue goes away?
—
Lorenzo
|
|
Kevin Brooks
|
May 1, 2014 at 6:44 pm
I tried disabling WordFence and ran into the same error. It seems EE is calling admin-ajax.php somewhere as http not https?
|
|
Kevin Brooks
|
May 1, 2014 at 6:46 pm
I enabled force admin ssl in wordpress https and that seems to have solved the problem.
|
|
Lorenzo Orlando Caum
|
May 1, 2014 at 7:07 pm
Thanks for sharing how you solved the issue. Is the following the change that you made?
Wordfence is activated and you enabled forcing SSL for WP Https
—
Lorenzo
|
|
Kevin Brooks
|
May 1, 2014 at 7:45 pm
That’s exactly right – glad to have found a solution. Thanks!
|
|
Lorenzo Orlando Caum
|
May 1, 2014 at 7:47 pm
Thanks for confirming. I’ll keep that in mind if we run into this issue again.
Cheers
—
Lorenzo
|
