API Request has been blocked by CORS policy

Thank you for reaching out to us. I understand how frustrating CORS issues can be, especially after you’ve taken steps to configure the plugin correctly.

I wanted to let you know that we did test our plugin’s compatibility with the JWT Auth – WordPress JSON Web Token Authentication plugin, and unfortunately, it seems there are some compatibility issues. We’ve noted your issue and will prioritize making our plugin compatible in a future sprint.

In the meantime, here are some steps I would take if I were in your position:

1. Check Plugin Configuration:
   • Ensure that https://www.shirksllc.com and https://shirksllc.com/ is listed as an allowed origin and that the appropriate methods (GET, POST, etc.) are allowed.
2. Check Server Configuration:
   • If you’re using Nginx, make sure the server configuration includes the necessary Access-Control-Allow-Origin headers. For Nginx, you would need to update the server block configuration.
3. Verify WordPress Rest API Headers:
   • Ensure that the REST API endpoints, particularly https://shirksllc.net/wp-json/jwt-auth/v1/token/validate, are returning the correct CORS headers. This might involve adding custom headers through your theme’s functions.php or using a plugin to modify the response headers.
4. Cross-Domain Setup:
   • Since your frontend (https://www.shirksllc.com) and backend (https://shirksllc.net) are on different domains, consider setting up a proxy in your frontend application to route API requests through the same domain.
5. Caching Issues:
   • Sometimes, caching plugins or server-side caching can interfere with headers. Try clearing your cache to ensure that the correct headers are being sent.

If you prefer, you can uninstall our plugin and leave a one-star review—we completely understand your frustration and appreciate your feedback as it helps us improve.