• Resolved yourstile

    (@yourstile)


    while saving, i have this Error: Communication Error exits
    Response Code: 403 error and saving of files stops

    {“readyState”:4,”responseText”:”<HTML>\r\n<HEAD>\r\n<TITLE>403 Forbidden</TITLE>\r\n</HEAD>\r\n<BODY>\r\n<H1>Forbidden</H1>\r\nYou do not have permission to access this document.\r\n<P>\r\n<HR>\r\n<ADDRESS>\r\nThe Web Server\r\n</ADDRESS>\r\n</BODY>\r\n</HTML>\r\n\r\n<!–\r\n – Unfortunately, Microsoft has added a clever new\r\n – \”feature\” to Internet Explorer. If the text of\r\n – an error’s message is \”too small\”, specifically\r\n – less than 512 bytes, Internet Explorer returns\r\n – its own error message. You can turn that off,\r\n – but it’s pretty tricky to find switch called\r\n – \”smart error messages\”. That means, of course,\r\n – that short error messages are censored by default.\r\n – IIS always returns error messages that are long\r\n – enough to make Internet Explorer happy. The\r\n – workaround is pretty simple: pad the error\r\n – message with a big comment like this to push it\r\n – over the five hundred and twelve bytes minimum.\r\n – Of course, that’s exactly what you’re reading\r\n – right now.\r\n –>\r\n”,”status”:403,”statusText”:”error”}

    can someone help me

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author watchful

    (@watchful)

    Sorry for the delay on this. Are you still having this error?

    I am having this issue yes. I will uninstall due timing here but wanted to report it back as well.

    {“readyState”:4,”responseText”:”<!DOCTYPE HTML PUBLIC \”-//IETF//DTD HTML 2.0//EN\”>\n<html><head>\n<title>403 Forbidden</title>\n</head><body>\n<h1>Forbidden</h1>\n<p>You don’t have permission to access this resource.</p>\n</body></html>\n”,”status”:403,”statusText”:”Forbidden”}

    • This reply was modified 5 years, 11 months ago by ricarod.
    Plugin Support jimiero

    (@jimiero)

    Hi,

    Afraid that’s an error coming from your website, I’d suggest you to check and see what’s blocking the access to the page

    As you can see…

    {“readyState”:4,”responseText”:”{\”apbct\”:{\”blocked\”:true,\”comment\”:\”*** Forbidden. You submitted too quickly. You may try again in a few seconds. Message seems to be spam. ***\”,\”stop_script\”:0}}”,”responseJSON”:{“apbct”:{“blocked”:true,”comment”:”*** Forbidden. You submitted too quickly. You may try again in a few seconds. Message seems to be spam. ***”,”stop_script”:0}},”status”:403,”statusText”:”Forbidden”}

    {“readyState”:4,”responseText”:”{\”apbct\”:{\”blocked\”:true,\”comment\”:\”*** Forbidden. You sent forms too often. Please wait a few minutes. ***\”,\”stop_script\”:0}}”,”responseJSON”:{“apbct”:{“blocked”:true,”comment”:”*** Forbidden. You sent forms too often. Please wait a few minutes. ***”,”stop_script”:0}},”status”:403,”statusText”:”Forbidden”}

    {“readyState”:4,”responseText”:”{\”apbct\”:{\”blocked\”:true,\”comment\”:\”*** Forbidden. You submitted too quickly. You may try again in a few seconds. Message seems to be spam. ***\”,\”stop_script\”:0}}”,”responseJSON”:{“apbct”:{“blocked”:true,”comment”:”*** Forbidden. You submitted too quickly. You may try again in a few seconds. Message seems to be spam. ***”,”stop_script”:0}},”status”:403,”statusText”:”Forbidden”}

    {“readyState”:4,”responseText”:”{\”apbct\”:{\”blocked\”:true,\”comment\”:\”*** Forbidden. Sender blacklisted. ***\”,\”stop_script\”:0}}”,”responseJSON”:{“apbct”:{“blocked”:true,”comment”:”*** Forbidden. Sender blacklisted. ***”,”stop_script”:0}},”status”:403,”statusText”:”Forbidden”}

    … I’ve had a variety of error messages and more that I didn’t take note of.

    I see various attempts at backup in the content folder w/ names such as .xcloner-006f0 but never got a message of a successful backup.

    I was using X-Cloner a few years ago and it worked fine. But apparently it has been improved so much that it no longer works at all.

    I’m currently running wp v5.4.1 but have been trying to get XC to work for the last few months w/o success.

    I previously uninstalled – some years ago – the earlier version of XC that worked fine – until it didn’t – and recently installed the current watchful v4.2.0.

    Suggestions?

    Plugin Support jimiero

    (@jimiero)

    Hello,

    What browser are you using when testing? Looking on the error you posted when you opend this ticket, seems Internet Explorer, can you try with different browser like Chrome or Mozilla Firefox and see how it goes?

    Plugin Support jimiero

    (@jimiero)

    Closing this for inactivity, if you still have issues, please open a separate ticket.

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

The topic ‘Communication Error Response Code: 403 error’ is closed to new replies.