Assunto: Falha de acesso externo à API REST do WordPress — ouvint.com.br
Olá, equipe de suporte.
O site https://ouvint.com.br, hospedado no InfinityFree, utiliza WordPress e o plugin WPVibe.
Entretanto, o diagnóstico do WPVibe informa que suas requisições externas recebem HTTP 200, mas o conteúdo não é reconhecido como JSON válido. As tentativas alternativas de conexão também apresentam timeout.
Solicito verificar possíveis interferências de proteção antibot, cache, redirecionamentos ou regras de segurança que afetem o acesso externo à API REST.
Peço, se possível, a identificação da resposta efetivamente entregue às requisições do WPVibe e orientações para restabelecer a conexão sem comprometer a segurança do site.
Atenciosamente.
Other Information
As seguintes rotas retornam JSON corretamente pelo navegador:
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 sounds like our browser security system, which is on every free hosting account. Your browser passes the check because it runs JavaScript and keeps cookies. An external service like WPVibe can’t do either, so it gets a short HTML page instead of your JSON. That page usually comes with status 200, which would explain why WPVibe reports HTTP 200 but “not valid JSON”.
The article says the check covers every URL, including REST endpoints, and can’t be turned off for one path, user agent or IP address. Your own domain doesn’t change that, and neither does a plugin setting or a cache or redirect rule. The options it lists are premium hosting, which doesn’t have this restriction, or not relying on inbound external calls to the site.
Here is the article on what the check looks like and what it affects:
And the shorter one on API access:
To check that this is your case, look at what WPVibe says it received, if it shows the response body. Does it contain aes.js or the text “This site requires Javascript to work”? If it does, the request was stopped by the security system and never reached WordPress. If it shows something else, please post that text.
The bot is right for the most part. API access to websites hosted with us is not possible, and that’s what WPVibe needs to work.
So using an AI to connect to your website is not possible. If you want to use AI, you could use a chat interface in the WordPress interface itself that calls out to an AI model to get instructions back and make changes. That’s what the official AI plugin from WordPress does, for example.
Finally, please note that this is an English language forum, and you’re expected to write your messages in English here.
Since your message was already clearly copy-pasted from an AI, ask it to write the message in English next time.