I don’t use a BPN and this has been happening when I first open the site. I don’t clear anything just close the page and reopen and it usually takes a couple of tries to access the site.
I just starting today having problems sending messages. It says there is an error I try multiple times to send ... I back out and go back to message and try again and it will still say error and once it actually goes there.is then suddenly multiple messages. This is both on my mobile connection and when I get in the WiFi
This is what I’m getting now.
I keep getting it too. Non stop. I have to refresh multiple times in hopes of getting to a page.
@Sheena123
Same here regarding refreshing multiple times
Thanks for the update on this.
Current theory is an iOS update that rolled out March-April time has created a compatibility issue.
Will message you both to request more info.
Yes! It’s been happening for two weeks for me.
We have just made a change which might help.
Please do following:
Let me know if things calm down over next 24 hours.
Before bothering with the above, you can check if the change is already applying to your device by clicking the link below. If the "http" line equals "http/2" then you don't need to do anything. Just see if things improve from there. If it says "http/3" then follow the steps to hopefully clear the network caching.
https://cuddlecomfort.com/cdn-cgi/trace
@Mark I do networking engineering in additional to general tech consulting (primarily for business clients). I have experienced this issue on my phone, tablet, and computers on various WiFi, cellular, and wired networks. It's not specific to VPN or non-VPN connections. I believe you're onto the fix if you haven't found it. However, it's possibly related to Private Wi-Fi Address or Limit IP Address Tracking settings.
While troubleshooting an issue for a client, I turned off these settings and various devices and noticed that this site loaded more reliably, since.
I'm happy to accept a DM if I can help with any testing, too.
@ScottMelts
Thank you. The good news is that I've been communicating privately with those most impacted and it is fully resolved since my last update.
As best I can understand from looking over various forums, the recent iOS updates have issues with some websites and apps where HTTP/3 QUIC is part of the network stack.
People could change their settings but I took the simple measure of switching the website to HTTP/2 which has worked here. We should be able to switch back at some point in the future once this is ironed out by Apple. Apparently the upcoming iOS update has a related fix.
@mark nice work!