403 Forbidden

This topic is: resolved

 

Thank you for contacting me. Please note that I live in the GMT+3 time zone - responses might be delayed by this.

This topic has 1 reply, 2 voices, and was last updated 1 day, 14 hours ago by Szabi – CodeRevolution.

Viewing 1 reply thread
  • Author
    Posts
    • #12014


      alexfit
      Participant

      Error 403 Forbidden When Using Aiomatic Plugin – Request for Assistance

      Message:

      Dear Aiomatic Support Team,

      I am currently experiencing a critical issue with the Aiomatic – AI Content Writer, Editor, ChatBot & AI Toolkit (Version 2.4.5) plugin on my WordPress website (https://estate-newyork.com). Whenever I attempt to generate content using the “Topic Based Post (Multiple API Calls)” mode, I receive the following error message:
      403 Forbidden
      You don’t have permission to access this resource.

      {“readyState”:4,”responseText”:”<!DOCTYPE HTML PUBLIC \”-//IETF//DTD HTML 2.0//EN\”><html><head><title>403 Forbidden</title></head><body><h1>Forbidden</h1>

      You don’t have permission to access this resource.

      </body></html>”,”status”:403,”statusText”:”error”}

      Attachments:
      You must be logged in to view attached files.
    • #12016


      Szabi – CodeRevolution
      Keymaster
      Post count: 4813

      Hello,

      First of all, thank you for your purchase.

      This seems to be a server config related issue.

      So, to resolve this issue, I suggest you to contact you hosting support and ask them the following: they should check if your host has any mod_security settings that forbids sending of URL as POST parameters, or any other rule, that could forbid this to happen. If they find such a rule, ask them to remove it. Also, you could describe the issue you are having to them, maybe they know how to fix it. To describe your issue, you can tell them the following: “When I try to activate a WordPress plugin, I get a 403 forbidden error.”

      If they do not find any such rule, maybe this behavior is because of another plugin you have installed on your WordPress installation, but let’s hope for now that contacting the hosting support team will solve this issue.

      Hope this is solved soon.

      Regards,
      Szabi – CodeRevolution.

Viewing 1 reply thread

You must be logged in to reply to this topic.