www.ads-software.com doesn’t load under experimental QUIC Protocol/HTTP3

  • Hello, I’m not sure where else to report this. I’ve had a lot of trouble accessing www.ads-software.com lately. The website didn’t load properly, including all documentation pages and forums. I managed to resolve this issue by disabling the experimental QUIC protocol on my web browser.

    I had the same problem with Tumblr (see here)

    I assume both of these websites share Automattic’s infrastructure somehow and that’s the reason of these issues.

    Might be something worth looking into.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Yui

    (@fierevere)

    永子

    Like SPDY (currently standartized as HTTP/2) there can be protocol version mismatches, that can result in errors. Please use default browser settings ??

    I have forwarded your topic url to Slack’s #meta channel, you can join and follow up there

    Slack

    Moderator Yui

    (@fierevere)

    永子

    https://quic.nginx.org/quic.html

    You can also disgnose if your browser correctly handles QUIC and there are no obstacles like UDP filtering on the route from your ISP

    Yani

    (@yaniiliev)

    I also experienced similar issue like the OP described. www.ads-software.com would load very slow or not load at all. I had to disable QUIC protocol in the browser to access www.ads-software.com normally.

    Thread Starter othernoel

    (@othernoel)

    Like SPDY (currently standartized as HTTP/2) there can be protocol version mismatches, that can result in errors. Please use default browser settings

    The problem occurs with default browser settings. It seems the default for “Experimental QUIC Protocol” is “enabled.” This occurred in Chrome, Firefox, and Vivaldi, on Windows 11 and Linux Mint 22. It also occurred on Fedora 40, but I didn’t test multiple web browsers on it.

    I have forwarded your topic url to Slack’s #meta channel, you can join and follow up there

    Thanks. ??

    https://quic.nginx.org/quic.html

    You can also disgnose if your browser correctly handles QUIC and there are no obstacles like UDP filtering on the route from your ISP

    The first time it showed 100 green (QUIC) blocks, and 900 red (failed) blocks, and the rest became HTTP. I re-ran the test and it was all HTTP. I assume that by default Chrome switches off QUIC if requests start failing from a website? In that case, it’s rather weird because that didn’t seem to happen when I was having trouble with www.ads-software.com.

    Perhaps the problem is that www.ads-software.com loaded partially instead of failing completely? In some cases only half of the text of the webpage would load, meaning the connection would be closed while in progress for some reason.

    To my knowledge, only www.ads-software.com and Tumblr fail to load like this. I never had trouble with any other website.

    I just checked and this issue also seems to affect all websites hosted on wordpress.com.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.