• Resolved barnez

    (@pidengmor)


    Hi,

    I’m getting this error logged in the WP dashboard:

    Failed to post via WordPress: "hash does not match: ClientCB[<!DOCTYPE HTML PUBLIC "-\/\/IETF\/\/DTD HTML 2.0\/\/EN">
    <html><head><title>NinjaFirewall: 403 Forbidden<\/title><style>body{font-family:sans-serif;font-size:13px;color:#000;}<\/style><meta http-equiv="Content-Type" content="text\/html; charset=utf-8"><\/head><body bgcolor="white"><br \/><br \/><br \/><br \/><center>Sorry <b>206.189.100.139<\/b>, your request cannot be proceeded.<br \/>For security reason, it was blocked and logged.<br \/><br \/><img title="NinjaFirewall" src="https:\/\/www.xxxx.com\/wp-content\/plugins\/ninjafirewall\/images\/ninjafirewall_75.png" width="75" height="75"><br \/><br \/>If you think that was a mistake, please contact the<br \/>webmaster and enclose the following incident ID:<br \/><br \/>[ <b>#6464297<\/b> ]<\/center><\/body><\/html>] Server[c02QAieSMG1kDxmG]"

    Failed to post via WordPress: "no auth_key"

    If I refresh the page it disappears. Is this a Litespeed Cache issue?

    Report No.: XACQWURS

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Hi @pidengmor, yes the error message is from Litespeed Curl task, and it seems your plugin NinjaFirewall blocked the request.

    Can you turn on debug log on Litespeed Cache > Setting > Debug and send us the debug log for checking after you see the message?

    Thread Starter barnez

    (@pidengmor)

    Thanks for the advice. I’ve enabled debugging, and will wait for the error message to be triggered again.

    Noted, thanks.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi,

    I’m going to mark this topic “Resolved,” due to lack of activity.

    If get the error again, feel free to reply and let us know what the debug log says. We’ll be happy to reopen the topic.

    Thanks!

    Thread Starter barnez

    (@pidengmor)

    Hi.
    I logged into the admin dashboard this evening (03/02/2019) at 21:53 and the error message was visible in the dashboard. Here is the debug.log split into two files:

    Part 1: https://pastebin.com/AsLFaHwD
    Part 2: https://pastebin.com/NwbNUJm0

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Log is incomplete and/or incorrect.

    Please create a ticket here

    Best regards,

    Thread Starter barnez

    (@pidengmor)

    Hi,
    I’ve tried to send you the files as a 2.2. MB tar directory but there is an upload error:

    The following errors occurred:
    Uploaded file was too large. Please try uploading a smaller file.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please try upload it somewhere like dropbox , google drive etc and provide the link in ticket.

    Best regards

    Thread Starter barnez

    (@pidengmor)

    Done. Thanks for the suggestion.

    Thread Starter barnez

    (@pidengmor)

    Issue now resolved by whitelisting the following LiteSpeed Cache IPs:

    
    142.93.112.87 
    68.183.55.115
    178.128.152.109
    206.189.203.203
    68.183.60.185
    206.189.100.139
    128.199.57.119
    159.89.13.42
    165.227.131.98
    45.76.44.137
    68.183.4.220
    68.183.180.19
    178.128.100.105
    139.59.59.66
    
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Failed to post via WordPress: “no auth_key”’ is closed to new replies.