QtWebEngine

Please provide more details: Which certificate is not trusted? IIRC Webengine was introduced in 5.5, but it was missing features. My guess is that the certificated actually can't be trusted and Qt 5.5 didn't notice.

6.7.3 is a bit old. You might want to try with the latest of the 6.9 series to see if things improve with regard to webengine. One thing, are you in debug or release mode ? That can have some impact on performances.

[image: 991f3ebf-a6bb-4b03-80d2-9c9377609b65.png] I cannot find any option to install this, it is available in previous versions though,

I've found an icudtl.dat in /usr/local/resources. I suppose it's the system one. I've made a small fix in my CMakeLists by doing: if(LINUX) # Check if icudtl.dat exists for Qt6WebEngine deployment if(EXISTS "/usr/share/qt6/resources/icudtl.dat") message(STATUS "Found icudtl.dat in /usr/share/qt6/resources") else() # Check if icudtl.dat is in /usr/local/resources if(EXISTS "/usr/local/resources/icudtl.dat") message(STATUS "Found icudtl.dat in /usr/local/resources") # Generate a symlink from /usr/local/resources/icudtl.dat to /usr/share/qt6/resources install(CODE " message(STATUS \"Creating symlink for icudtl.dat\") execute_process( COMMAND ${CMAKE_COMMAND} -E create_symlink /usr/local/resources/icudtl.dat /usr/share/qt6/resources/icudtl.dat ) ") else() message(FATAL_ERROR "icudtl.dat not found in /usr/share/qt6/resources or /usr/local/resources") endif() endif() endif() But I'm not sure that it's the best way to do it.

Thank you @Christian-Ehrlicher, it's clear to me now.

@Wenzhi-Wang hi and welcome to devnet, Are you also trying to use the MinGW kit with the MSVC version of WebEngine ?

QtWebEngine is compiled with Qt6. Try using windeployqt6.exe instead. Works for me.

@Christian-Ehrlicher Thank you, I compiled the source code as you said, it works

OK fixed it. I was not updating the additional resource files when packaging my application. eg. qtwebengine_.pak, vcontext.bin, and the icudtl.dat file.

The bug is in the Nvidia code, good library should never crash. Unfortunately it is closed source and legacy, so I don't expect any fix from Nvidia.

o>O o.O oh

@Hecklezz said in Changing CSS to achieve a transparent background breaks rendering: Should I open a bug report regarding this or is this already a known issue? You can check in Qt bug tracker https://bugreports.qt.io/browse/VSCODEEXT-204?jql=

For more info, try clicking the blue "More details" at the bottom of that dialog error box "You can't get there from here"

@SGaist Hi, sorry for the late reply. I installed ubuntu and it finally worked! I had to change some of my code though, and installed deb. What I found: QApplication.instance().installEventFilter() will crash the program. Instead, run window.installEventFilter() You were right about Chromium on Debian issue. Changing to Ubuntu seems to have worked!

@SGaist I tried to update my Qt to 6.8.3, but I encoutered some issues about files not found. You can see in this topic : https://forum.qt.io/topic/162706/issue-encountered-with-c-compilation-in-qt-creator-and-msvc?_=1752664613398

@SGaist said in Connecting a QWebSocket to a given IPv6 address (no URL): What did you do that made things work ? It might be helpful to other people :-) There were two things: The QWebSocketServer was set to SecureMode, while on the client's side, the request URLs were all "ws://", so changing the QWebSocketServer to NonSecureMode helped a lot. When the lookup of QHostInfo is successful, the lookupId of is set to -1, and the errorString is then "Unknown error". So there really was no problem with this to begin with!

Hi @Pippin, You're right that managing 20k+ users with QTcpServer and raw sockets can be very resource-heavy. Instead of using plain HTTP, I'd recommend looking into WebSockets with QWebSocketServer, which allows real-time, two-way communication and scales better for game updates. For encryption, you can either use QSslSocket directly or offload SSL using a reverse proxy like Nginx to handle HTTPS/WSS and let your server deal with plain TCP internally. As for syncing game state: the server should act as the single source of truth. When Player A makes a move, the server processes it, validates it, then pushes the same update to Player B and any watchers using WebSocket messages. This way, all players receive the actions in the same order, keeping everything in sync. Starting with a small prototype using a few clients will help you get the architecture right before scaling up. Good luck!