Novamira Troubleshoot reports HTTP 403 for anonymous REST requests, /.well-known/oauth-protected-resource, and POST /wp-json/novamira/v1/oauth/register (expected 201).
Other Information
I’m trying to connect the Novamira WordPress MCP plugin to ChatGPT at https://cuencaweb.xo.je/wp-json/mcp/novamira-oauth. No security plugin is active; W3 Total Cache is inactive; .htaccess has the standard WordPress rewrite rules, including Authorization header forwarding. Could you check whether a hosting firewall or other server-side security rule is returning these 403 responses, and whether REST/OAuth discovery and registration requests can be allowed for this domain? The affected paths are /wp-json/, /.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server, and POST /wp-json/novamira/v1/oauth/register. Thanks.
Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
This isn’t a firewall rule on your domain. It’s the browser security system that every free InfinityFree account has, and it blocks anonymous API requests. The article below lists “AI tools and MCP clients” and REST APIs among the things that can’t get through. ChatGPT connecting to Novamira’s OAuth endpoints is that kind of request.
The system only lets through clients that can run JavaScript and keep a cookie. Anything else, like the Novamira troubleshooter or ChatGPT’s connector, is stopped before WordPress sees the request. That fits the 403s you’re getting on /wp-json/, /.well-known/… and the POST to /oauth/register.
The article also says the check can’t be turned off for a specific path, user agent or IP address. So there’s no way to allow those endpoints on this domain, and nothing in .htaccess or WordPress will change it.
Here’s the article on the security system and what it blocks:
And this one covers API access in particular, including the options that are left:
Those options are premium hosting, which doesn’t have this restriction, or hosting the API side somewhere else.