-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect, perhaps due to self-signed SSL #92
Comments
Thanks for the report! I see you're on an iPhone and I'm not 100% sure it's possible to mess around with the CA chain (at least according to Apple's terms). I'll look into it though. But the issue at hand is very likely to be the fact you're using a self-signed cert. I expect it doesn't work with Glowing Bear as well, am I correct? As far as the error message goes, I'll try to make it a little less annoying (not pop up as often) when this happens. |
You're also right the error popup should be below the header bar so it doesn't move interactive elements when it appears, that's a great point. |
I haven't tried glowing bear - as mentioned, the vps doesn't run nginx. |
Should be fixed after b8e6ac7 |
When I try to connect to my weechat relay, it fails, shows a partial error message (screenshot below), and then clears the error and retries in at most 1 second. Lith repeats this as long as the app is open, and the red error message moving the menu button up and down makes it difficult to tap.
I think this is because my relay has a self-signed cert. (It doesn't run a webserver to get a Let's Encrypt or other cert).
So there's a couple issues:
Hope this helps. I look forward to trying the app.
The text was updated successfully, but these errors were encountered: