Hi Plamen,
Please review your internal correspondence and records. The following was received from your support team (Atanas, NitroPack Performance Engineer) on March 26, 2024 and April 1, 2024, respectively:
(Note: Our domain has been obfuscated)
March 26, 2024:
My name is Atanas and I am a Performance Engineer at NitroPack.
I was made aware of what happened and I confirm that I removed the website from our system. The pings will now stop and not reoccur.
The explanation of what happened is the following:
We have a system that periodically checks the connection status between our system and our customer servers to ensure NitroPack is working. At some point, the website https://www.mysite.com/ was connected to NitroPack and when the plugin was uninstalled, it didn’t notify the system so it didn’t stop trying to verify the connection.
We found a broken functionality in our plugin and it should not behave this way. The plugin must notify our system that the site is no longer using it. The action we’re taking is to update the plugin’s code to prevent such occurrences in the future.
In the meantime, to perform a full uninstall, it is recommended to first disconnect the plugin from the plugin’s interface in WP Admin and then delete it.
Thank you for your cooperation and understanding.
April 1, 2024:
I was alerted that https://www.mysite.com/ is still receiving pings from our systems.
I cross-checked with our CTO and found that despite removing the website previously, I the queue was built in advance and rescheduled itself on the same list where the website existed.
My colleagues have explicitly removed the website from the list and you should stop receiving requests from our end. Also, my colleagues will work on improving the service to consider more variables when pinging a website to verify whether it should be pinged.
I apologize once again for the inconvenience.
Based on our current issue, it appears Team NitroPack did not implement the fixes and go-forward plan shared by Atanas.
Bottom Line:
This issue affects many websites that do not use or no longer use your plugin (not just ours).
Recommendations:
1. Update your backend code (conditionals) to ensure it can accurately detect websites that are actively using your plugin. Websites not actively using your plugin need to be removed from your servers and ensure your User Agent respects that finding (i.e., stops pinging websites).
2. Update your plugin’s code and instructions for performing a clean uninstall of your plugin. The updated code should include removing your plugin’s info and collected data from the user’s (i.e., website’s) database and your servers. Your updated instructions also need to state that performing a clean uninstall of your plugin will completely remove all data contained in the affected database(s) and from your servers. That is, all data will be lost and is unrecoverable.
Done at our end. Thank you.