sounds like it wasn't triggering correctly, which makes sense if you're on 5.5.2, it breaks the reliability of the exploit when launched via browser. 5.5.1 didn't fail as frequently.
your new homebrew channel should prevent any of this happening again.
your new homebrew channel should prevent any of this happening again.






