API 400 ERROR IN SEO ANALYSER

#613372
  • Resolved Anonymous

    2 years, 1 month ago

    Rank Math free

    I am getting the api 400 error in the seo analyser option in the rank math WordPress plugin. I also connected with the hosting provider but everything is fine from there hand. so please give me the solution. My website is vinaygargofficial.com

Viewing 7 replies - 1 through 7 (of 7 total)
  • Rakibuzzaman Siam

    2 years, 1 month ago

    Hello,

    Thank you for contacting us and sorry for any inconvenience that might have been caused due to that.

    Can you please confirm you’ve whitelisted the IP 193.138.6.5 and the user-agent RankMathApi/2.0.2; https://rankmath.com?

    You can do this in the firewall or ask your web hosting provider to help you further.

    After that, please head over to your WordPress Dashboard > Rank Math > Status & Tools > Database Tools and click the Clear SEO Analysis and Remove Transients buttons to flush the SEO Analysis cache.

    Flush

    Once done, clear your website and any server-level caching on your site before doing the SEO analysis again.

    Let us know how it goes. Looking forward to helping you.

    Thank you.

    Anonymous

    2 years, 1 month ago

    Rank Math free

    HOW TO WHITELIST IP CAUSE I CONNECTED TO A HOSING PROVIDER AND ALL THINGS ARE GOOD WITH THEM. TELL ME PROCEDURE

    Princess

    2 years, 1 month ago

    Hello,

    You can do this in the firewall or ask your web hosting provider to help you further.

    Please do not hesitate to let us know if this doesn’t help or you have any follow-up queries.

    Anonymous

    2 years, 1 month ago

    Rank Math free

    [28-Aug-2023 01:31:51 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:06 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:07 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:07 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:07 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:08 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:08 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:13 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:45 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:45 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:46 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:48 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:49 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:32:55 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:01 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:02 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:02 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:02 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:13 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:13 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:21 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:22 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:31 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:31 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:38 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:39 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:43 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:43 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:54 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:33:55 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:19 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:19 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:20 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:30 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:30 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:54 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:34:54 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:00 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:01 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:01 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:18 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:25 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:25 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:35 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:35 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:54 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:35:54 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:36:08 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:36:08 UTC] protocol error, got ‘E’ as reply-type byte

    [28-Aug-2023 01:36:09 UTC] protocol error, got ‘E’ as reply-type byte

    i have this error also in my rank math plugin how to resolve it

    Rakibuzzaman Siam

    2 years, 1 month ago

    Hello,

    Can you please share where you’re facing these errors? You can also use any image-sharing tool like https://imgur.com/upload to share a screenshot of these errors with us.

    However, if you’re facing these errors on your error log then please share the full error with us so that we can check the issue further for you.

    Looking forward to helping you.

    Thank you.

    Anonymous

    2 years, 1 month ago

    Rank Math free

    Hello,

    I have updated the sensitive data as requested. Can you please check further?

    Thank you.

    Miguel

    2 years, 1 month ago

    Hello,

    We have replied to your other ticket about the same issue.

    Please refrain from opening multiple tickets for the same issue as that won’t expedite the process of getting a response.

    We are closing this ticket in favor of the other one since it’s for the same issue.

    Thank you.

Viewing 7 replies - 1 through 7 (of 7 total)

The ticket ‘API 400 ERROR IN SEO ANALYSER’ is closed to new replies.