Keep getting redirected to main.js

[Greywolf74]

Not sure how to fix this issue. When I first sat down this morning I went to TPB.org website (got there just fine) to try and register for an account because I have some torrents i wanted to share. Ive since seen on the forums here that website registration isnt currently working but I didnt know that at the time. When I clicked on the register button it seems to just reload the main page so I thought "Maybe my pop up blocker (ad blocker ultimate add-on in firefox) is blocking the registration page from popping up" so i disabled the pop up blocker. Once I did that then I started being redirected to the main.js page. I re-enabled my pop up blocker, still being redirected. Rebooted, still being redirected.

At this point I opened up Chrome and got to the page normally but the registration button was doing the same thing so I went in to the Chrome settings and disabled the built in pop up blocker and now Im being redirected to Main.js in Chrome too. Went and re-enabled the pop up blocker in Chrome but still get redirected to Main.js.

I started Googling the issue and browsing through the forums here and the only suggestions I could find said that javascript needed to be enabled but when I go into "about:config" in firefox and look at the "javascript:enabled" setting it is set to "True". So now Im stumped. Can anyone offer any further insight?

[CaptButler]

Not sure what you were searching--there are several threads listed on this problem on the main "Site Issues" page.  This is because TPB has not accepted any new registrations since at least 2019.  Comments have also been disabled and all of the previous comments have been wiped.

[SectorVector]

Try clearing your browser cache. It might solve it.
You can clear browser cache selectively for one site (TPB.org). You don't have to clear the entire cache.

[Greywolf74]

Try clearing your browser cache. It might solve it.
You can clear browser cache selectively for one site (TPB.org). You don't have to clear the entire cache.

I forgot to mention it but I had tried that. It didnt work at the time but at some point over the last 3 days the issue has resolved itself. Thanks for the input tho