SJON error

Hi @thenoxx, glad you reached out!

It sounds like you’ve encountered two issues: getting a JSON error when saving settings & getting a site lockout.

About the site lockout, it should be lifted after 15 minutes, allowing you to log in again. Can you confirm if you can access the site now? If you had multiple failed login attempts that would lead to a lockout; you can check what triggered the lockout by going to Security > Logs.

Regarding the JSON error, it might be related to a REST API problem. Solid Security requires access to the REST API to work properly. Please contact your hosting provider and ask them to enable all the REST HTTP request methods on your server: GET, POST, PUT, PATCH, DELETE, and OPTIONS.

After ensuring that your server allows all the REST HTTP request methods, try saving the plugin settings again to see if the error is resolved.

Let us know what you can find.

L.S..

Thank you for your response

The strange thing is that i have another website with this provider and better-security plugin installed with no problems

As you can see there are more errors and I have know idea how to solve this

Kind regards,

TheNoxx

Hi @thenoxx,

Since your posted screenshot is too blurry to read (and also translated in Dutch) could you please provide the missing details indicated by the 2 question marks (?) below?

The REST API encountered an unexpected result (Performance)

The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

When testing the REST API, an unexpected result was returned:

REST API Endpoint: ?

REST API Response: ?

Perhaps it’s best to temporarily switch WordPress to language English (United States), then recreate the Site Health screenshot (with a higher resolution) and post that into this topic.

+++ To prevent any confusion, I’m not SolidWP +++

• This reply was modified 8 months, 3 weeks ago by nlpro.
• This reply was modified 8 months, 3 weeks ago by nlpro.
• This reply was modified 8 months, 3 weeks ago by nlpro.

Hi NLPro

Thank you for you response

Sorry for the inconvenience ; I’m a fool on the hill

REST API Endpoint: https://fcoptiekgopirle.nl/wp-sjon/wp/v2/types/post/context=edit

REST API Response: (403) Forbidden

Kind regards,

TheNoxx

Hi @thenoxx,

No worries, we all make mistakes (live & learn) ??

After correcting the 2 typos in the endpoint url and then trying it out I got the following result:

{“code”:”itsec_rest_api_access_restricted”,”message”:”Je hebt onvoldoende rechten om dit endpoint te benaderen. Toegang tot REST API aanvragen is beperkt door Solid Security instellingen.”,”data”:{“status”:401}}

This means this particular REST API endpoint is restricted by the Solid Security plugin API Access -> REST API setting (Restricted Access).

( Full navigation path: Security > Settings > Advanced > WordPress Tweaks).

Strangely on my test site I have the same plugin setting but no REST API recommended improvement in the Site Health page.

I did swap out your domain for my domain. Basically tested the same endpoint on my test site and I got exactly the same message (at least that is consistent).

You might try (if possible) and set the REST API setting to Default Access. Would be interesting to see whether this removes the REST API recommended improvement entry in the Site Health page.

Hi @thenoxx,

Further testing allowed me to reproduce the Site Health REST API recommended improvements entry.

Turns out it is not caused by the Solid Security REST API setting (which in a way makes sense). In fact it’s not caused by the Solid Security plugin at all!

The true cause is that the user you are logged in with when accessing the Site Health page does not have a role assigned that includes the edit_posts (possibly other capabilities) capability.

All I needed to do is (temporarily) remove the edit_posts capability from the (WordPress core) administrator role. Log into the WordPress Dashboard as a user which has the administrator role assigned and then navigate to the Site Health page.

Adding the edit_posts capability back to the (WordPress core) administrator role cleared the Site Health REST API recommended improvements entry instantly ??

To @nlpro

Thank you for your response, sorry I responded not sooner but this weeksnd is/was the dutch TT in Assen. And I am a Motogp fanatic

Strange solution because I was logged in as administrator en checked the health page.

It is possible because anyher user has administror rights and always write the posts information for all users.

I will try your solution en let you know if it works.

Kind regards,

TheNoxx

Hi @thenoxx,

Ah right, it definately was a busy sportsweekend (EK soccer, Tour de France, Formula 1, TT etc). Phew, I’m more tired now than at the start of the weekend ??

If the user has the administrator role assigned then it’s always possible that the edit_posts capability is (dynamically) removed for that user at WordPress init when logging in. Another possibility is that this user has a custom administrator role assigned which does not include the edit_posts capability. Are there any custom roles defined or is there any roles management plugin installed?

WordPress by default only uses the following 5 roles:

• administrator (beheerder)
• editor (redacteur)
• author (auteur)
• contributor (bijdrager)
• subscriber (abonnee)

By default only the subscriber role does not include the edit_posts capability.

Interested to hear what you can find.

• This reply was modified 8 months, 3 weeks ago by nlpro.
• This reply was modified 8 months, 3 weeks ago by nlpro.

Hi?@thenoxx,

If you require no further assistance, please mark this topic as ‘Resolved’.

+++ To prevent any confusion, I’m not SolidWP +++

Thanks for the response from you all????

Greetings

TheNoxx