@ericmarceau, my tests were conducted on firefox-nightly-152.0a1-20260510094626. However, unlike yours, but similar in notion, I am able to access it on chromium-147.0.7727.137-1.fc44. Consequently, I’ve since tried firefox-nightly -safe-mode, and it works. I wonder what could be the cause. Per about:addons, I’ve merely:
Two minutes ago I couldn’t reach the website at all with neither librewolf or brave
Then used netsurf, which connected immediately (but no login ofcourse because no javascript)
Then I could connect with librewolf, but the site refused to give javascript or css.
Then after a refresh I got the javascipt moving dots but nothing else.
I have the idea that their server-jungle, which was already a bit flakey to begin with, is severely hosed at this moment.
EDIT: minutes later, the landing page popped up, I could login via launchpad. It is now hanging indefinitely on this page \https://login.ubuntu.com/saml/process
with the message:
You are now signed in at the Identity Provider.
You will now be automatically redirected to the Service Provider.
If so, if anyone is willing to upvote my original GitHub report (), please do. It’ll cause it to rank higher in their issue list. Additionally, please post any new, actionable information for them, there, too.
If they will manage to somehow make only Cloudflare domains excudable, that will use dynamic load or whatever, i am ok. But i will not exclude any website, because it can contain not only Cloudflare scripts.
I can confirm I’m aware of issues; and as confirmation you’ll note no Ubuntu Weekly Newsletter issue this week was published, ie. 943 didn’t make it to The Ubuntu Weekly Newsletter | Ubuntu
I’ve had issues since I woke my box my Saturday [9 May] morning, but given on the weekend I knew a lot of Canonical staff were travelling (sprints are running this week, one of the weeks where most are at the same location instead of working spread around the globe from their home offices or normal locations) many are ‘out of reach’ for much of the time. I raised a ticket that afternoon anyway.
It’s now Tuesday arvo for me, and still no reply, nor have I learnt more from other sources. The last chat message I see on UD was 8 May or before current problem. Sure I can write something, and it acts ~normal, but an hour after I send the message I get told that it couldn’t send. These problems are what caused the work on UWN943 to pause (joint decision as it wasn’t just me encountering issues).
This week many Canonical paid staff are on sprints & set activities they do twice a year when they’re all together, and not in their normal workspaces/routines, the weekend just past is commonly when they’re travelling to the sprints, and the next weekend (or week, some can stay a little longer than a week) is staff returning home anyway, so twice a year (post release usually) there are times where responses from Canonical staff can be a little slowed.
Many Canonical IS also ‘idle’ in places like #canonical-sysadmin on libera/IRC too, but entering that room gives you details on filing a ticket with RT anyway.
( I have got faster responses via IRC, which is likely why I mention it, but I think in those cases I was just lucky & made comment whilst someone happened to be looking who could help/action & request was easy)
I confirm my own access to the Ubuntu Discourse site is no longer experiencing issues. Others may wish to test and confirm for themselves.
Don’t know if the timing of the fix for others seems to correspond with the timing of the response I received in the email shared in the following posting.
), please do. It’ll cause it to rank higher in their issue list. Additionally, please post any new, actionable information for them, there, too.
