::
I’d HIGHLY recommend you try hosting your backend via TOR not HTTP. Flushing out all the TLS dependencies could be more than you care to tackle. Then there is the question on whether you bind to localhost your external IP. TOR takes the port accessibility, IP binding, and TLS all off the table.
If you don’t want to use TOR, then my next recommendation is that you create a fully signed TLS certificate chain that you add to your root CA for all units involved. Keep in mind, some „browsers“ balk at self-signed certificates. Suite is in essence an embedded browser engine.
Also look at the Suite command-line switches to see if there are any `–debug`, or `–no-ssl` options, or anything of the like.
If the problem persist, review our open issues on GitHub
* https://github.com/trezor/trezor-suite/issues
* https://github.com/trezor/blockbook/issues