Viewing 5 replies - 1 through 5 (of 5 total)
  • Which ever plugin you are using, post in that plugin’s support forum.

    Thread Starter fterdal

    (@fterdal)

    Thanks for your reply! The problem is, I’m not sure which plugin (if any) is raising this error. Is there anything in WordPress Core that would raise this error? I’ve actually seen this crop up in several of our company’s WordPress sites, which all have a different combination of plugins.

    WordPress core would not cause any lockouts.

    What do your sites have in common? Host?

    The responsible plugin is probably iThemes Security. (formerly Better WP Security)

    It looks like the 418 “teapot” error might be intended as a humerus way to respond to the lockout that was added in version 3.2.1. https://plugins.trac.ww.wp.xz.cn/browser/better-wp-security/trunk/readme.txt#L1118

    418 http status code explained (link goes to google)

    Installation and configuration info for the plugin can probably be found in the plugin docs or links contained therein.

    [edit] humerus.. Get it? Funny bone? Lol! (so sorry)

    Thread Starter fterdal

    (@fterdal)

    Thank you both for your replies. All of my sites do indeed have the same host. So that’s a possibility. I’ll check with them. (I’ll mark as resolved if that turns out to be the issue.)

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

The topic ‘418 teapot error’ is closed to new replies.