Do you maybe have a tool active which blocks the rest api?
Thread Starter
Dan14
(@dan14)
Not that im aware of. I disabled almost all plugins and it persists. What do you recommend I look out for to fix it? Lines of codes etc.?
Hello, i’m having the same error as stated above.
Really Simple SSL setting page loads only as a BLANK page.
I will have to revert the plugin version for now. Can you please double check and find a fix ? (previous versions have worked like a charm until now).
Thank you very much !
Just to confirm. With latest version of WordPress. Really simple SSL 6.0.9 doesn’t work (setting page is fully blank). I reverted with version 5.3.1 and everything is back to normal.
There must be something with the update…
The settings page is now loaded using the rest_api. If the rest_api is blocked, the page shows as blank.
@sucyshop please make sure you also have 403 forbidden errors on the rest_api urls, otherwise it is not the same issue.
@dan14 Please check if the default WordPress rest api works by checking yourdomain.com/wp-json/wp/v2/posts (you can just post this url in your browser. The browser will then show a list of your posts in raw data format).
@dan14 can you also try re-saving the permalinks in the general WordPress settings, settings/permalinks?
Dear Rogier, thank you very much for quick answer and support (between i’m also a pro user so i purchased the pro pack for several sites).
#1. I’m not a developper so this is hard for me to tell if ‘rest api’ is working or not.
From your url i’m getting this result
0 {…}
1 {…}
2 {…}
3 {…}
4 {…}
5 {…}
6 {…}
7 {…}
what does it mean ?
#2. How can i be sure to also have 403 forbidden errors on the rest_api urls ? Is there any links or admin panel / url i should follow ? Can you please guide as well.
#3. This is just an opinion : You might have a very good reason to do the change as a developper but please also think about the users (clients). untill now i had no error, no hassle and i think the plugin name goes with my words => really simple. If you start bringing some hassles with rest a^pi things from the dev side… users won’t feel this is really simple any more. (just my opinion as pro customer).
Thank you very much again for help & support.
@sucyshop if you right click on the screen, then click ‘inspect’, ‘console’, you will see the developer console, with som errors. If you can email that screenshot to support(at)really-simple-ssl.com I can take a look.
just sent it, hoping i did it well.
Thank you very much for support !
I encountered a situation where having debugging enabled caused the php errors to get echoed into the Rest API response, causing script errors. Please also check if you have WP_DEBUG enabled, and if so, set it to false.
I’ve updated the article, and will continue to do so as we find configurations that cause this.
Based on the above I’ve made some adjustments which I think will improve this. If someone having this issue can check if this branch resolves the issue the would be great!
https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/change-rest-api-response-method
@dan14 the above change (6.0.10) does not apply to your case, as it applies to script errors caused by php errors echoed into the REST API response.
I’ve encountered a setup where the X-HTTP-NONCE key wasn’t set in the $_SERVER variable, but I’ve found a solution for this specific situation as well.
I suspect your issue has the same cause. You can check with this branch if that is the case.
https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/simplify-logged-in-check
I expect this to resolve the issue. It will get tested, and released next week.
As there has been no further activity here, and all responding users have reported the issue to be resolved with the current github version, I’m closing this thread.
6.0.11 will be released on November 22nd.
If anyone still has issues after installing 6.0.11, please start a new topic as it is likely a different issue with a different cause.
