Summary:
If DNS is unavailable when Caprine starts, Caprine will display a white screen as if it got stuck. Instead, it needs to retry for a connection every so often. Right now the only fix is to exit Caprine and relaunch it.
Details:
I handle DNS through AdGuardHome running in a Docker container. It's configured to start up, but there's about a 30-60 second delay while Docker loads in the background. Because my DNS is configured to look at it, I do not have connectivity to the Internet for about a minute after my computer starts. Caprine is set to load during startup, and in a timing race, beats Docker at loading. Because DNS doesn't resolve for about a minute, Caprine gets stuck and just shows a white screen. Instead, like other programs, it needs to retry the connection every so often.
Caprine 2.54.0
Electron 10.1.5
win32 10.0.19043
Locale: en-US
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too