Back to Community
Home / Community / General

Troubleshooting Sucuri Security: Why Your Failed Logins Pagination Shows Raw HTML Code

13 threads Sep 9, 2025

Content

If you use the Sucuri Security plugin and have recently visited the Last Logins → Failed Logins section, you might have encountered a strange issue: instead of seeing neat page navigation links, you see a long block of raw HTML code that looks like this:

<li><a href="..." class="...">1</a></li><li><a href="..." class="...">2</a></li>

This problem was widely reported by users after updating to plugin version 1.7.17. The good news is that it's a known bug that has since been fixed. This guide will explain why it happened and what you can do to resolve it.

What Caused the Pagination Bug?

Based on analysis of community reports and the official responses from the 'Sucuri Security – Auditing, Malware Scanner and Security Hardening' team, the issue was a coding error introduced in version 1.7.17. The function responsible for generating the pagination links was incorrectly outputting the raw HTML code instead of rendering it properly in the browser. This bug affected the pagination on both the Failed Logins and All Users tabs within the Last Logins page.

How to Fix the Pagination Display Issue

There are two primary ways to address this problem, depending on your comfort level and website's needs.

Solution 1: Update the Plugin (Recommended)

The simplest and safest solution is to ensure your Sucuri Security plugin is updated to the latest version. The development team identified and fixed the bug in a commit dated several days after the 1.7.17 release. This fix was included in all subsequent stable public releases. Simply navigate to your WordPress dashboard and update the plugin to the newest version.

Solution 2: Manual Fix (For Advanced Users or If Update is Not Immediate)

If you needed a fix before the public release was available, the development team provided a temporary workaround. They indicated that users could install the development version of the plugin from its GitHub repository. It is important to note that installing development versions is generally not recommended for production sites, as they may contain untested code. This solution was only suggested as a stopgap measure until the official fix was rolled out.

Other Related Issues

While troubleshooting, some users reported seeing a "Get_logs: couldn’t connect to host" message. According to the sample threads, this appears to be unrelated to the pagination bug and is likely specific to individual server configurations.

If you continue to experience issues after updating, it is advisable to ensure your WordPress installation is also up to date and to test for conflicts with other plugins by temporarily disabling them.

Related Support Threads Support