Closed vauvenal5 closed 3 years ago
Hi,
same problem here. I have my Nextcloud available in local network and I can't log in using 192.168.178.xx/nextcloud.(Just a blank page appears). I only can log in from outside my home network with the DNS name.
Oliver
@ksapp-dell are you using a properly signed certificate? Which version are you using? Why not login from within the network with the dns name?
@loveisfoss when TLSv1.2 is enabled do you still have to accept the certificate? To really test this you will need to reset the app data. It is a bit strange though that the app asks you to accept the certificate if it is truly a signed let's encrypt certificate.
I myself am using let's encrypt through a reverse proxy. Certificate validation is done at the proxy.
@vauvenal5 Yes, it asks for a certificate validation and it really seems strange.
Other examples:
It may be something with my apache reverse proxy configuration. I'll look into it and come back.
@loveisfoss a few thoughts on this:
host.com
but you are accessing the server by ip 192.168.x.y
.The problem this issue is actually describing was about the bad user experience when having to login with a self-signed certificate. This is fixed in v0.23.1
since #34 was closed.
Hi, F-droid had an update and now I am at Version 0.23.2. The behaviour changed:
What do you need from me to troubleshoot this ?
@ksapp-dell do you have a properly signed certificate?
@vauvenal5 I think you are right. Asking for confirmation when using letsencrypt is strange, but it doesn't have to do with Nextcloud Yaga. The TLSv1.2 requirement seems to have to do with the app, though, right?
Hi, I am using letsencrypt to get signed certificates.
@loveisfoss
@ksapp-dell Actually same issue as with @loveisfoss, if you really have a properly signed certificate then Yaga will not ask you to accept the certificate. Are you really trying to login with your certificate hostname or with your local ip?
@vauvenal5
Is it possible that you are still in lets encrypt test mode?
I am just using swag on Docker to get certificates for duckdns domain with dns validation method. I don't know what testing mode of letsencrypt is, hmm...
Edit: I had a configuration error. I was using cert.pem instead of fullchain.pem in my apache configuration. After changing to fullchain.pem no further confirmation is needed. It fixed also my log in problem to Nextcloud bookmarks (Android app). BIG thanks for this, even if it was an indirect and kind of off-topic problem! :)
@loveisfoss glad you could resolve it :)
This was fixed in v0.23.1
.
Just a heads-up. Using Nextcloud on Docker and https through apache2 reverse proxy with letsencrypt certificates.
Cannot log in with "Sign In" button, goes to a blank white page.
Could not log in with "Sign In with Browser", nothing happened with this button. Solved it by commenting out this line from apache conf file: "SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1 -TLSv1.2". Sign In with browser now works because I am being asked to accept or not if I trust the certificate! (After some trial and error the problem was that I was disabling the TLSv1.2 one.)