Hi @rockstar_tom, glad you reached out!
There isn’t a way to manually whitelist endpoints via Solid Security’s settings, as the plugin only accepts IPs for whitelisting.
Can you try allowing Default Access to the REST API in Security > Settings > Features > Advanced > WordPress Tweaks or disabling the Default Ban List in Security > Settings > Features > Firewall > Ban Users and check if one of them would help resolve the permissions issue for Download Monitor?
Please let us know how it goes.
Thread Starter
Tom
(@rockstar_tom)
Hi there, thanks for your reply. I have tried both of these suggestions within Solid Security’s settings and there is no change.
What else can I try?
Hi @rockstar_tom,
What exact errors do you get?
I guess (temporarily) deactivating the SolSec plugin resolves the errors instantly?
Is this issue happening while using the latest version of the Solid Security plugin (9.3.3)?
+++ To prevent any confusion, I’m not SolidWP +++
-
This reply was modified 1 year, 9 months ago by
nlpro.
Thread Starter
Tom
(@rockstar_tom)
Hi @nlpro, @shanedelierrr
I get these two errors in the browser console:
reports.min.js?ver=4.9.14:1
GET https://mywebsite.co.uk/wp-json/download-monitor/v1/user_reports?_wpnonce=ac813e16e3&user_can_view_reports=1&offset=0&limit=40000 500 (Internal Server Error)
reports.min.js?ver=4.9.14:1
Uncaught (in promise) Error: Something went wrong! Reports response did not come OK -
at DLM_Reports.fetchUsersReportsData (reports.min.js?ver=4.9.14:1:4639)
Yes, temporarily deactivating the SolSec plugin resolves the errors instantly.
Yes, this issue happening while using the latest version of the Solid Security plugin (9.3.3).
Hi @rockstar_tom,
Please activate the SolSec plugin and then try to add the ITSEC_DISABLE_MODULES constant to the wp-config.php file as described in the Solid Security FAQ post below:
How Do I Disable All Features If I Can’t Access My Site?
Note this is not a solution. Just a debugging step. Interested to hear the result.
Thread Starter
Tom
(@rockstar_tom)
Thanks for all your replies and help. This issue has now been resolved with an update to the Downloads Monitor plugin.