omSupply Desktop returns a blank screen when Caddy is off (AKA Invalid SSL Cert)

[marthakeezy]

What went wrong? 😲

If Desktop isn't able to connect to the server due to an SSL Certificate issue, the desktop app doesn't show any error.

Interestingly with developer tools open the error is shown!

Thank you @jmbrunskill 🙏🏼 🙏🏼 🙏🏼

Not sure what the severity is, it depends a bit on if this is a pattern we see in our install base.
So far it's primarily affecting testers...

Expected behaviour 🤔

If there's an ssl certificate error connecting to the server this should be displayed clearly to the user.

Possibly we should allow the user to connect even with invalid cert? - Add trust for a particular cert perhaps?

We should probably create a way to allow the user to specify a URL manually rather than relying entirely on discovery?

How to Reproduce 🔨

Steps to reproduce the behaviour:

1. Setup your open-mSupply server to use a certificate for a domain name aka test.msupply.org
2. Start desktop locally on the server
3. Connect to the IP Address shown (IP Address doesn't have a valid cert)
4. Connection fails...

Your environment 🌱

• Open mSupply Version: V2.3.0-RC1
• Legacy mSupply Central Server Version: V7.17.10

• Platform: Desktop (Windows); Central Server

• Database type: SQLite3

[andreievg]

Make sure error like this appears on screen, if can't be replicated don't spend too much time trying to replicate.

There is prosed work around/solutions for this in #5080