OPNsense 26.7.2_2: TLS error when connecting to i.ytimg.com

Started by S1ardust, Today at 10:47:26 AM

Previous topic - Next topic
Hello,

I am new to OPNsense and  I'm experiencing a strange HTTPS/TLS issue. (Version: 26.7.2_2)
On my Windows 11 Client behind OPNsense, I was missing thumbnails on the YouTube website.

When I try to open the URL "https://i.ytimg.com/vi/FLH1aARTpMg/hq720.jpg" i get the error "ERR_SSL_PROTOCOL_ERROR" in Edge-Browser:

You cannot view this attachment.

After a lot of troubleshooting, with some help from ChatGPT, I was able to reproduce the issue directly from the OPNsense shell.

Most HTTPS traffic works normally. For example:

curl -4 -sS -o /dev/null -w '%{http_code}\n' \
https://www.google.com

returns:
200


However, connecting to the YouTube image server directly from OPNsense fails:

curl -4 -sS -o /dev/null -w '%{http_code}\n' \
https://i.ytimg.com/vi/FLH1aARTpMg/hq720.jpg

results in:

curl: (35) TLS connect error:
error:0A00010B:SSL routines::wrong version number
000



DNS resolution works correctly, and the same i.ytimg.com IP is reachable. The URL also works normally when the client connects directly through the router instead of OPNsense.

Has anyone seen a similar TLS issue with OPNsense 26.7.x / FreeBSD 15.x?

Any hints on where to investigate further would be greatly appreciated.

EDIT: No Plug-Ins, No relevant Firewall rules, fresh Install

Thank you very much for your support!

No problem here, neither with opening the site in Edge nor with the given command - it returns 200.

So that is not an OpnSense problem. I would rather suspect a geoip issue, because Youtube has distributed servers. You may have hit a defective one.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, Leox LXT-010H-D

1100 down / 450 up, Bufferbloat A+

Hello,

Quote from: meyergru on Today at 11:49:48 AMNo problem here, neither with opening the site in Edge nor with the given command - it returns 200.

Thank you for checking! 🙏🏻

I found an issue on my network/gateway/router.
It was not an OPNsense problem.

Thank you