Virusdie got PDF Report via email, but don't see results in MainWP Dashboard

[svenh (Sven)]

Hi,
I received the Virusdie PDF report via email that indicates some of my sites have infected files. However, the report doesn’t specify which site is infected. Additionally, the MainWP Dashboard shows “checked 0” and “not yet scanned.”
Does anyone know why the Virusdie reports are not syncing back to MainWP or where I can find the detailed results of the scan?

Thanks,
Sven

[bojan (Bojan Katusic)]

Hey @svenh

Welcome to the MainWP community!

The Virusdie PDF reports are sent out by Virusdie themselves, not our extension.
So we don’t have an influence on the content of that report.

@svenh

Does anyone know why the Virusdie reports are not syncing back to MainWP or where I can find the detailed results of the scan?

You can try loading fresh Virusdie data in the extension by clicking on the Reload Virusdie Data button:

Finally, do you know if you are using any other Virusdie accounts, or just the one you created when setting up the MainWP Virusdie extension?

[svenh (Sven)]

Thanks for your response.
I know that the PDF report comes from the Virusdie page, but I was thinking that after that report, I would also get the data in MainWP. I tried reloading the Virusdie data, but nothing changed. I am only using the Virusdie account that was created from the MainWP dashboard.

[bojan (Bojan Katusic)]

Since it is the same Virusdie account, the extension should indeed be displaying the same information.

Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?

And please refer to this Managers thread by its URL in the ticket.

[bojan (Bojan Katusic)]

We’ve determined that this issue is caused by a change in Virudie’s API response.

Please see this announcement for more information:

Virusdie API Problem

Recently, we noticed that the MainWP Virusdie Extension started showing 0s instead of real scan statistics. After investigating, we found that the issue is caused by a problem with the Virusdie API. Unfortunately, there is nothing that can be done from our end as the API has stopped returning this information. We have informed the Virusdie technical support team and are awaiting further information from them. As soon as they resolve the problem, the extension should start working as normal.