Closed junetried closed 2 years ago
Hi! Anything interesting in the 2nd log file? It looks like for some reason your proxy suggests a TLSv1 connection. Not sure that I can do something about that.
Nothing in the other log looks interesting, no.
Looking back at my nginx config, I have these two lines:
ssl_protocols TLSv1.3;
ssl_prefer_server_ciphers off;
Yet Firefox prefers to use TLSv1.2? Going to Google and checking encryption info, no issues with TLSv1.3 support... This is weird, and it might be an issue on my end.
I was having a similar issue, #127, and as soon as I allowed TLS 1.2 the login screen would advance and the app works just fine now. In my case, I had to adjust the TLS via Cloudflare, as that is where I had it set to 1.3 only.
I was having a similar issue, #127, and as soon as I allowed TLS 1.2 the login screen would advance and the app works just fine now. In my case, I had to adjust the TLS via Cloudflare, as that is where I had it set to 1.3 only.
Allowing TLSv1.2 fixes this, the app logs in just fine now. Thanks!
I have no idea how to troubleshoot at this point, so I'll just attach a log.
When trying to log in, the 'Open in browser' and 'Continue' buttons do nothing when I type my host. Initially I thought it was because my nginx configuration trims /index.php, but I don't have much reason to believe that at this point. What I do know is that it works fine under my apache configuration, after trusting the self-signed certificate (the CA has been added in android settings). Switching back to nginx after logging in with apache running doesn't work around this issue.
I'm not sure the log is very useful, it doesn't give much insight. Don't know what
TLSV1
is doing there, Firefox assures me the host is using TLSv1.2.