All I have is a blank screen for SSL dashboard
I am having the same issue as well. Updated to the plugin to latest version and still having issue. Seeing this error in the console.
GET https://website/wp-json/reallysimplessl/v1/fields/get?false=&nonce=fa264723e5&token=govbq&_locale=user 403 (Forbidden)
The forbidden 403 code means something is blocking the request.
This can be a security plugin or your hosting company. Removing the rule that blocks it will resolve the issue.
@amorales1214 please check in the console what the error is (right click, inspect, console).
Often it helps to re-save the permalinks.
@rogierlankhorst – issue resolved. thank you so much for your help. was driving me nuts. you the man 🙂
I am using Wordfence as the security plugin and it is not blocking the script. However, in browser console I am seeing 403 forbidden error and SSL dashboard doesn’t work. Could you help me with this? It happens in the admin dashboard. @rogierlankhorst
I haven’t changed any setting and all of a sudden seeing this error. Further clarification, this issue is happening in a multisite where the subsite can be either xyz.domain.com or xyz.sites.domain.com. We have a 2 set of wildcard SSL certs to cover both domains. The issue is happening in just xyz.sites.domain.com where the the wordpress admin is showing not secure and SSL dashboard doesn’t load.
@shrestharavee1 nothing we can do about 403’s generated by your website configuration I’m afraid.
As a possible work-around: I have created a version where the plugin will use a classic admin-ajax call if the rest api doesn’t work.
https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/show-error-message-on-blank-pages
You can try this branch, or wait for the update (probably next week), or alternatively check with your hosting company if they block the rest api.
If you try the above branch, let me know if it works!
i am seeing this problem, ie blank/empty SSL dashboard forms, when i installed on new site
no error message seen
deactivated and reactivated – same error
irt seems to have sort of resolved itself
will advise further as needed
