10:13:47 ERROR SSLSocket.cpp (520) Certificate verification for host '' failed: 2148081683
10:13:35 ERROR JobHttp.cpp (153) Http status code is none for url. 10:13:35 INFO SSLSocket.cpp (427) Certificate verification failed, closing connection. 10:13:35 ERROR SSLSocket.cpp (524) US, Massachusetts, Cambridge, "Akamai Technologies, Inc.", a248.e. 10:13:35 ERROR SSLSocket.cpp (520) Certificate verification for host '' failed: 2148081683 10:13:11 ERROR JobHttp.cpp (153) Http status code is none for url. 10:13:11 INFO SSLSocket.cpp (427) Certificate verification failed, closing connection. 10:13:11 ERROR SSLSocket.cpp (524) US, Massachusetts, Cambridge, "Akamai Technologies, Inc.", a248.e. 10:13:11 ERROR SSLSocket.cpp (520) Certificate verification for host '' failed: 2148081683 10:13:10 ERROR AssetsGetAsset.cpp (98) Failed to get asset for product id 4932.
I'm not messing around with Windows settings every time I just want to load the app or a game - especially not something as seemingly easy to change as Windows date/time which I imagine could actually end up screwing things up if for example Windows or another program decides to set an automatic backup/cloud sync for something after I've changed the date and names/links it to November 2019 because that's what I've had to set the Windows clock to at the time instead of the proper current time & date. Personally, I will not be using UPlay until this is fixed. It's frustrating that it's always UPlay that I seem to have these "connection problems" with - when I don't have any actual problems with my internet, Windows, other apps or other game launchers. I had a look around the forums and can see that this problem has come up before - so it seems like it's something Ubisoft should be aware of and should have fixed by now. I always have to put Windows' date to November 2019 now if I want to log in at all or even play anything once I'm inside.
I also tried putting the date back to normal, quitting UPlay and reloading it to see if it had actually fixed anything with the login problem - it hadn't. I did manage to get the Store to load a few times by clicking on the Store button, then immediately going into the Games button and clicking on a game so that the store info would be dragged through for the game, then clicking back to the Store button and eventually it would load - but even then, the Store loaded in a "blacked out" version of itself with a constant spinning circle in the middle and I wasn't able to click on anything. but I'd still be unable to access the Store normally. So then I'd change the date back to November 2019 and the games would straight away be able to load their info again. Even clicking into games that I already owned in the "Games" part of the app, it wouldn't be able to load any of the information relating to the games that it normally pulls from the Store info - there'd just be endless spinning circles where the info should be. However, after then changing the date back to normal, moving around UPlay to different pages would time out and I started getting the error message inside the app saying the store was "Currently Unavailable" when trying to use the Store page.
What finally worked for me was changing the Windows date back to November 2019, which allowed me to log in first try.
I refused to resort to opening ports on my router because no other app that I use in Windows 10 requires that and no one should ever have to resort to leaving ports wide open if an app is written properly - I'm more likely to stop using an app that requires port forwarding than leave ports open. I tried everything - clearing DNS cache, checked for alterations to host file, reinstalled UPlay, checked the LAN setting in the UPlay proxy settings (it was already unchecked), even checked the Windows Firewall settings and noticed that UPlay doesn't request access through Windows Firewall (like every other app that needs direct access does) so I manually added the Uplay executables to the settings to bypass the firewall to see if that worked - still didn't work. Then it just randomly decided to stop letting me sign in at all saying the "Connection Lost" error message.
Sometimes I'd just have to open a web browser and a load a page so that my internet connection was actively doing something during the sign in and it'd suddenly decide to work. I've had this on and off with UPlay for as long as I can remember using UPlay, except before it used to be completely random - sometimes I'd be able to sign in and sometimes I wouldn't.