Unable to Login Windows

[Rob Michel]

Just downloaded subsurface on new Windows PC running Windows 10. Subsurface version 6.0.5079-CICD-release. Will not login to cloud. Changed password from the new PC thinking I forgot it, was able to sign in on all other instances of subsurface across different platforms with the new password that I made via the new PC but can't sign into that PC.

[Dirk Hohndel]

The first thing to do is to run Subsurface again on that Windows system, try to log in, take note of any error messages that you see, and send quit Subsurface.
After you exited Subsurface, attach the log files to a response to this message (including any error messages)

The logfiles are in C:\Users\Home\AppData\Roaming\Subsurface in the two files subsurface_out.log and subsurface_err.log

/D

[Rob Michel]

Should add that I can login here with the new credentials also;

https://cloud.subsurface-divelog.org

[Rob Michel]

Mr. Dirk, I did reply to you with the logs.. did you get them? For some reason I don't see that message anymore.

[Dirk Hohndel]

Is this a Windows XP PC by any chance? Or something else that is utterly ancient?

The PC doesn't recognize our (valid, I might add) SSL certificate:

"The issuer certificate of a locally looked up certificate could not be found"

got invalid SSL certificate with hex digest "e3ad7c44619854d0b920efe2a82f9213"

Received error response from cloud storage backend: "SSL handshake failed"

Not much I can do to fix that on my end.

/D

[Rob Michel]

No Sir, brand new Windows 10 PC

[Dirk Hohndel]

Oh, here's an idea. That's not the fingerprint of our server certificate. Is this a corporate PC that's trying to be clever and is doing a man in the middle attack with a proxy or some other form of web filtering (like from an "advanced security app" or some other nonsense?

It looks like someone or something is trying to intercept the connection and Subsurface is declining to play along.

/D

[Rob Michel]

No Sir, just a plain jane Windows PC

--
You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/00C19499-9D9B-481A-8384-447FA9A6CE1C%40hohndel.org.

[Geo Wil]

I'm having the same issue. I re-imaged a laptop with Win10, clean install, nothing except the latest patches on it. I can login from other PC and web but on the new install, it keeps telling me the password is wrong. I did reset it just to be sure it wasn't cached somewhere and still the same issue. I'll get the logs and post them here soon. Thanks

[Geo Wil]

I just pulled my logs and my error log states the exact same thing, except at the very end, there is one more line. It is: "Completed connection with cloud storage backend, response " " " 

Mine is the same, a standard Win10 build and nothing is installed, just MS patches and Subsurface. Why would the SSL handshake fail? I can't see the codes so I can't tell which part is failing. Is there any forced TLS 1.3 only setups maybe? Or is there a fallback version set? Are the SSL certs self-signed or is there a CA that's involved? Would you like me to send my logs in anyway? Is there something else I can test on this side? 

Thank you for your time with this.  

[Dirk Hohndel]

They are Let's Encrypt certificates and current.
And they work for on average 2000 different users who access the cloud every day...

I am completely out of ideas

/D

[Geo Wil]

Okay, thanks, I'll look at the cert store in Win and see if I can find anything out of the ordinary.  Then I'll see if I can setup something to test the different versions of SSL/TLS and see what happens. This is so strange - clean install, nothing but patches, just weird. I am taking this laptop with me on a dive soon and wanted to track everything there. I guess I could just load them locally and then later on, go to my other machine and sync with the cloud, right? 

[Rob Michel]

@Geo Wil I am still hitting a brick wall with this. I'm in the same boat. Nothing special to this machine at all. Installed Windows 10, dl Subsurface and nada. It works fine on all the other machines I have it on, So weird.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/1f6049c9-aca7-4337-aaf1-292987049368n%40googlegroups.com.

[Gmail im Auftrag von Martin Gröger]

hm...

maybe you have to set the permission for subsurface to pass the windows firewall. have you checked the firewall-settings in windows?

keep on howling

grey

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CAMERQOmHSX8_c4CL7buPKhN9Y-ggTqsjRDT4c9Fx9EYNmsz1xg%40mail.gmail.com.

[Geo Wil]

I'm glad you said that, Grey. I checked my settings and they were set to allow Subsurface through the FW. But I thought, well, I will just disable all of them and try again...all of a sudden, it connected. Doesn't make any sense whatsoever but it's working. I will play with the rules some more but at least this is a good sign. Thanks for the suggestion! 

@Rob Michel, please try disabling all of the individual firewalls (Public/Private/Domain) and see if that works. Then you can go back and turn on as needed and make rule exceptions. I am still playing with mine now but I wanted to post this immediately to see if it would help you or anyone else with this issue. I normally disable it first when troubleshooting but I thought the exceptions were fine. Anyway...let us know.