I can no longer access these forums via WiFi; only via mobile data

Since yesterday afternoon, I have been unable to access these forums via my home broadband. However, I can access them using my phone’s mobile data (using its hotspot when trying from my desktop or laptop).

This is consistent across my Android phone, Ubuntu desktop and Ubuntu laptop.

The error message is ERR_TIMED_OUT. The screenshot is from Chrome:

It worked well up until yesterday morning.

Using it via my mobile is terribly frustrating because the signal here is poor and therefore slow!

What I’ve tried:

  • Power down the modem and router, leave for a minute, and power them back up.
  • Same with my desktop, laptop and phone.
  • Swap between IPv4 and IPv6.
  • Disable ad-blocking (the only ad-blocker that I use is NextDNS; but I can still access the forums via my mobile data with NextDNS enabled).
  • Try from a different browser (Firefox).
  • Try from a Guest profile.

As this affects all of my devices (Android phone, Linux desktop and Linux laptop), I am at a loss as to how to even start to diagnose or fix this.

What can you suggest please?

EDIT: The following command works on WiFi even though the browser doesn’t.

curl https://discourse.ubuntu.com/

Mystifying!

5 Likes

please try changing your DNS settings to ClouldFlare

1.1.1.1 or 1.1.1.2

1.0.0.1 or 1.0.0.2

then try the connection please, best of luck Steve ..

That happened with me yesterday too while using Wi-fi in my local.

Other sites were loading ok

Oddly it only happened on my laptop and I could view it on my phone connected to the same Wi-Fi

Try using a VPN and see what happens.

1 Like

Paddy, it’s worse than that…

Ubuntu 26.04 with Firefox 150 fails
I’m writing this reply via Microsoft Edge in a Windows 11 VM with Ubuntu 26.04 host

It’s baffling?

1 Like

It’s likely ‘issues with infrastructure’ - something that has been plaguing the Discourse since it’s been launched. There is a lot of complaints about this rising up the chain already behind the scenes.

3 Likes

It’s not just Discourse, I have been unable to run snap refresh or open snapcraft.io (ERR_SSL_PROTOCOL_ERROR) for about a week now while connected to any VPN, despite https://status.snapcraft.io/ showing “All components are Operational“.

Is there any ETA on restoring access so that people using VPNs can update their snap packages?

At my end I can’t open Ubuntu discourse within Firefox on my Noble, but on same Network using other devices and browsers. Other websites work as usual.

[edit]
After deleting cookies and browsing data belonging to Ubuntu and Canonical sites I can open Ubuntu discourse. Trying to log in it seems I’m only receiving an incomplete web page. Login not possible.

1 Like

@g-schick could you possibly post some screenshots?

Thanks/Danke

It just stops there.


Just tried installing chromium. Can’t reach snapcraft.io from this system. Updating deb packages works via terminal but no snaps. Need to investigate further …


Just tried same things on a second device (other manufacturer, but same software setup). Same result. iOS and MacOS devices on same network do not show problems with Ubuntu discourse and snapcraft.io

Have you tried logging in using Private/Incognito mode in a new window?

What happens?

Deleting cookies and other website data should do the same as ‘Private/Incognito’. But tried it anyway. Didn’t change anything.

Not if you have extensions like adblockers or NoScript (unless you whitelisted this site).

I have to go out now but will also test later.

This may be part of the recent attacks against Canonical’s infrastructure or it may be something new.

I honestly don’t know but we ask that everyone remains patient until the parties who deal with this can take a look.

More than that I don’t have right now.

1 Like

Kubuntu 24.04, Firefox, wired connection: no joy whether in normal or private browsing mode, the connection times out :cry:

Hopefully, this will be resolved soon :folded_hands:

Thank you, everyone!

Alas, no improvement.

I don’t have a VPN (except Tailscale, but that’s not what you mean; I’ve tried with Tailscale both enabled and disabled). I installed Opera and used its VPN, but, sadly, no change.

It certainly is!

Thanks for the information. Do you know if there’s a place where this is reported, so I can view its progress?

If you use IPv6, try restricting your connection to IPv4. In the past, I found that it helped, although recently IPv6 has worked fine for me.

I used a Guest profile (which goes a step further than incognito), and a fresh Firefox instance. Today, I tried an incognito window and, again, the same problem.

2 Likes

Just an update on my recent experience with discourse.ubuntu.com

Yesterday, Saturday 09 May 2026, using my normal Ubuntu 26.04 OS, I tried the following without success:-

  1. Removed all Firefox extensions
  2. Deleted all Firefox browsing data/history etc.
  3. Private browsing with Firefox
  4. Booted into a “Try Ubuntu” live session and opened Firefox
  5. Rebooted my router
  6. Changed the DNS setting to 1.1.1.1
  7. Opened Epiphany (Gnome Web) and the first page of discourse.ubuntu.com loaded, subsequent navigation failed inc. login

Currently, writing from Windows 11 VM via Microsoft Edge within Ubuntu 26.04 host
Just found out that I can also login through ProtonVPN (Firefox extension)

3 Likes

Well, that’s interesting! I don’t have a VPN, so I can’t test this for myself.

I tried Brave and ProtonVPN free and no luck. Some reports on Reddit are suggesting Canonical might be blocking VPN to mitigate attacks but I certainly am unable to confirm this as fact.

https://snapcraft.io/ also has a message about performance degradation but I just installed Brave in my Ubuntu 26.04 test VM without issues.

Perhaps try first logging in here https://login.ubuntu.com/ and then Discourse, any difference?

1 Like

I discovered, quite by accident, that not all the Proton VPN servers allow you to log in to discourse.ubuntu.com.
Amsterdam and Zurich were fine, San Jose USA failed.
This reply via Firefox Extension > Proton VPN > Zurich

Still baffled, perplexed and discombobulated :upside_down_face:

2 Likes

I logged out and tried it, but no difference.