Timer gets to zero, but sites not blocked

[JLewis5]

Hello all,

I just added the LeechBlockNG Chrome extension last week, and have been getting it configured. One issue I've encountered, however, is keeping me from enjoying the full functionality: the countdown timer gets down to zero, but it doesn't block either the site I'm currently on, or other sites in my blocked list if I try to visit them.

A few details:

1. I created one block set, and have a variety of sites included, such as YouTube, etc.
2. I have a daily time limit of 30 minutes.
3. I have the block in effect between 8:30 AM and 4:50 PM.
4. It's blocking within time periods AND after time limit.
5. The block is in effect Monday through Friday.

So let's say I'm on YouTube. I can see the counter going down, but when it gets to zero, the page stays open and the video keeps playing. If I go to a new tab and visit another site on the blocked list, I'm able to do so. The timer will still display (showing 00:00), but the page isn't blocked.

I don't know if I have some settings set up incorrectly or what.

If anyone has any suggestions, I'd be grateful!

[proginosko]

Please export your options to a text file (Options > General > Export Options to Text File) and email it to me at leechblockng@proginosko.com so I can take a closer look.

[JLewis5]

Thank you! I've sent over the options file.

[proginosko]

Thanks for sending the options file. Strange. I don't see anything wrong with your settings, and when I tested them on my system (Chrome on Windows 11) they worked as expected.

Which OS are you using?

Try this:

• Go to the Extensions page and click on the link to "service worker" under LeechBlock NG. (You may have to enable developer mode first.)
• Click on the Console tab and see if any error messages appear when you go to a site that should be blocked.

[JLewis5]

Thanks for getting back to me. I'm running Windows 11. I followed the instructions on checking for errors, and found the following: *Uncaught (in promise) Error: Only a single offscreen document may be created.* I should mention that the error was already in the console when I opened it, before I visited a site on the block list. So it would seem that something else caused it. As an extra tidbit of information, I tried using the lockdown feature, and that did successfully block sites. So it's not a matter of blocking being completely non-functional. Rather, it seems that the blocking functionality isn't being triggered by the timer reaching zero. I do appreciate your help! Jonathan

…

On Mon, Jul 21, 2025 at 8:39 PM James Anderson ***@***.***> wrote: Thanks for sending the options file. Strange. I don't see anything wrong with your settings, and when I tested them on my system (Chrome on Windows 11) they worked as expected. Which OS are you using? Try this: - Go to the Extensions page and click on the link to "service worker" under LeechBlock NG. (You may have to enable developer mode first.) - Click on the Console tab and see if any error messages appear when you go to a site that should be blocked. — Reply to this email directly, view it on GitHub <#616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BU6BQTCCEXKO6NTZKB2CSKD3JWI45AVCNFSM6AAAAACCAAFKMOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBTHE4DENA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[JLewis5]

Just wanted to check back to see if the error I found means anything, or if there are any other possible solutions.

[proginosko]

I don't think that error message is relevant to the issue here.

I know this sounds desperate, but perhaps try uninstalling the extension, restarting your computer, then reinstalling the extension. You can use the exported text file to import your settings again. I'm not sure what else to suggest at this point, because your system is basically the same as mine, but I haven't been able to reproduce the issue.

[JLewis5]

So, for whatever reason, it's been working perfectly over the last two days (even without the uninstall/reinstall). I don't know why it's suddenly working, but hey, I'll take it.

[proginosko]

Okay, good! Feel free to reopen this thread if the problem recurs.