Your software makes connections to https://35.244.225.31/ (the mothership?) which uses a self-signed SSL cert.
Not really a feature request I guess but just a suggestion for basic cybersecurity hygiene.
Your software makes connections to https://35.244.225.31/ (the mothership?) which uses a self-signed SSL cert.
Not really a feature request I guess but just a suggestion for basic cybersecurity hygiene.
I think the certificate is valid per se (signed by letsencrypt, if I’m right) but it’s not working for this IP (it’s issued for roonlabs.net
/ .app
).
If I remember it correctly it was mentioned that there’s some load balancing or so going on which somewhere doesn’t translate back from IP to a domain name. I believe it should be solved programmatically but don’t ask me how.
Guess I should have thought about that… yeah, get’s complicated. Depending on which load balancers you’re using and such too methinks. I’ve got limited experience with big IP and sonicwall.