Description:

With the current packaged godot, I can not connect to a websocket to my server. I have no problems with an exported version of my project (tested on linux, web and android), or with the editor downloaded from godot website, or if I package godot myself and remove 'cert' from the 'to_unbundle' list.

I had not tested my project for several months, but the bug has been here for a least a few weeks. I can at least confirm it was present with the previous 3.3 version, and the current 3.4 one.

In my opinion, this feels like it is linked with Let’s encrypt root certificate expired in September. https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ However server-side my certificates are up to date (still not due to renewal), and my client is up to date (with ca-certificates, ca-certificates-mozilla and ca-certificates-utils packages installed). So I don’t know what additional entries godot’s certificate file has, but maybe it’s not a good idea to unbundle it after all.


Steps to reproduce:

I’ve created a minimal reproduction:

Client side, I create a scene, and attach a script containing the websocket example from https://docs.godotengine.org/en/stable/tutorials/networking/websocket.html
The address to use can be my own server for testing: "wss://porygon.shaac.me:46321". I attach to this ticket this minimal project for simplicity, but it really take 2 minutes to recreate it.

Server side, I have the simplest websocket server, in python (with python-websockets package). Code is the following:

```
#!/usr/bin/env python3

import asyncio
import ssl
import sys
import websockets


async def handler(websocket, path):
print(f"Accepted client {websocket.remote_address}")


ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)
ssl_context.load_cert_chain(sys.argv[1])

start_server = websockets.serve(handler, "", 46321, ssl=ssl_context)

asyncio.get_event_loop().run_until_complete(start_server)
asyncio.get_event_loop().run_forever()
```

I feed it in argument the path to a relay.pem wich is obtained with `cat {privkey,fullchain}.pem` in let's encrypt certificate folder. I’m letting my server open on "wss://porygon.shaac.me:46321" for the purpose of this ticket.