Active topics button not working

[Tortoise]

Is it just me, or is anyone else taken to Telstra Gateway instead of Active topics when they click on the said button? Edit: Sometimes I get the option of a 'new posts' button as well, which does work.

[tastrax]

works correctly for me (PC, WIN10, Chrome browser)

[Tortoise]

It's a Mac. Still not working.

[Son of a Beach]

Works OK for me (MacOS 10.15.5 / Safari, Windows 10 / Chrome & iOS / Safari).

If you have a different browser installed, try that.

Try clearing all your browsing data (clear cache and cookies).

Have you tried turning it off and turning it on again? (I know its very cliche, but it's amazing how many things this will fix - all for good reasons... so much internal data gets reset and corrected during the process of a clean boot up ... in this case it will clear your DNS cache which might or might not be relevant).

What's the full "Telstra Gateway" URL that you get redirected to?

[Tortoise]

Works OK for me (MacOS 10.15.5 / Safari, Windows 10 / Chrome & iOS / Safari).

If you have a different browser installed, try that.

Try clearing all your browsing data (clear cache and cookies).

Have you tried turning it off and turning it on again? (I know its very cliche, but it's amazing how many things this will fix - all for good reasons... so much internal data gets reset and corrected during the process of a clean boot up ... in this case it will clear your DNS cache which might or might not be relevant).

What's the full "Telstra Gateway" URL that you get redirected to?

Thanks, SoaB! It works on Firefox (not on Safari). Don't know why I didn't think of doing the off/on thing. I'll also google how to clear my browsing data.
http://mygateway.gateway

[Tortoise]

I found nice instructions. History, cache and cookies now cleared. Active topics working in Safari again. Thanks again.

[Son of a Beach]

Good to hear. Looks like that URL might be for your local broadband router. Something weird may have happened with your computer's idea of it's network, or your browsers cache of things, and the modem/gateway was trying to handle the weirdness.