Strange - Servers have steadily become unusable with hummingbird but not Eddie

[sophia1 0]

I have 3 linux machines and they are all exhibiting the same behavior at variable rates, where it's become harder and harder to find a server that works.  They always connect but websites don't work.
My last machine now doesn't work as of yesterday, and coincidentally right after the time the Triangulum server went down for maintenance and came back up yesterday. 

Configurations:
1) Fedora machine running hummingbird/goldcrest
2) Debian 13 Machine running hummingbird/goldcrest in linux lxc container running Debian 12 (another lxc container also runs Debian 13)
3) Debian 13 Machine running hummingbird/goldcrest in linux lxc container running Debian 13
* I connect all machines using Openvpn and by default they seem to pick UDP.

Symptoms:
- All 3 machines connect to all airvpn servers without any error or problems. They connect quickly and reliably always.
- However, most websites don't work. 
- Smaller websites especially ones with only text work reliably but with delay.  ifconfig.io or ipchicken.com works.  lite.cnn.com (text version of cnn) works, but cnn.com has problems
- Airvpn.org is the most sensitive website and is the least likely to work.  It just hangs as if I typed in a non-existent website url.

Observations:
- In the end, these last several weeks, I had to try 20+ different servers and found that only the ones in latvia worked
- But this past week or two, it seems latvia servers are starting to do the same thing.
- I then switched to force goldcrest to use -p tcp which made things much better but yet sometimes quirky with not loading websites 
-The lxc containers all have very similar if not the same configurations
-I was using the older version of the airvpn suite until recently but switched to the newest one lately on many machines. It seems unrelated as my last machine was working until yesterday connecting to Triangulum in Singapore and was using the old version from 2023.
- The last machine was connecting with hummingbird and automatically choosing UDP and connecting to Triangulum. It has been working for several months this way.
    Yesterday, it stopped working right after that server went down and had maintainence.  Now I can still connect but half the websites don't work.
- As a result, I tried the -P tcp trick with hummingbird, and it works better now.  But other servers other than Triangulum have random websites that don't load even with the -P tcp flag.
- Eddie works fine for all my machines and configurations and connects to servers and works even when hummingbird doesn't.  But I want to use hummingbird. GUI is hard to work with in a LXC container and the eddie-cli doesn't seem to have the flexibility that hummingbird has.
- I noticéd that Eddie uses wireguard instead of openvpn.  Maybe that is what is making it work better?
- I don't mind using wireguard but I get this error when I set the wireguard flag in hummingbird/goldcrest and I don't know how to fix it: 
ERROR: system 'modules.builtin' does not exist.
ERROR: cannot load wireguard system module

Is there some kind of upgrade slowly rolling out over all the airvpn servers that is somehow making my configurations incompatible? It has been slowly getting harder and harder to find a server that works and I don't know why.

[Staff 10402]

17 hours ago, sophia1 said:

ERROR: system 'modules.builtin' does not exist.
ERROR: cannot load wireguard system module

Hello!

Note: Suite versions older than 2.0.0 do not support WireGuard.
Note: do not try to access Debian 13 kernel modules from a Debian 12 container.

It's possible that the WireGuard kernel module is not properly loaded in your Debian 13 LXC container, even though Debian 13 host includes the module.

LXC containers can be restricted from accessing kernel modules even if they're available on the host. Please make sure that the container has access to the network related kernel modules by checking your LXC configuration file. If this is not possible or anyway you want to avoid it, then you need to ensure that WireGuard's kernel module is available inside the container.  WireGuard kernel module (wireguard.ko or wireguard.ko.xz) should be in the following directory:
/lib/modules/$(uname -r)/kernel/drivers/net/wireguard

If the problem persists, can you please send us the output of the commands:

uname -a
lsmod | grep wireguard
ls /lib/modules/$(uname -r)/kernel/drivers/net/wireguard

Kind regards