[2020] Trouble logging into Paradox Account in game (CK3) for accessing multiplayer

I've had one case like this resolved this way:

In the Windows search box enter firewall. Click on “Allow an app through the firewall” . Scroll through the list there, you’ll probably see CK3 there already. Both the Private and Public boxes should be ticked; if either are not click on Change Settings up the top then check both boxes and Ok that change. Then scroll down further and check the same for Paradox Launcher and Steam.  

We're working on this btw, just wanted to pop in and let you know! So far, according to our systems, the login should work fine but clearly that's not the case hence we're digging deeper. Can you please check the following:

1. Are you using a VPN? If so, please disable it and try again
2. Can you please sync your computers clock in Time and Date settings in Windows? It's a bit of a long shot but could actually solve it!  

lukior said: I have a problem, I want to join a friend online but i can't, we have all the same DLCS. But I don't have the right version and i don't know why, I can't even see the other parts online. Help me.

If you can log in okay you do not have the problem being discussed in this thread. If you have the wrong checksum in the MP lobby compared to your friend, one of you has a bad installation. DLCs have nothing to do with it. Current version and checksum is 1.02 713d , whoever does not that should do a Steam verify or a clean reinstall.  

somebears said: I managed to get it working by downloading the windows version from steam. It did not start with proton, but I ran ck3.exe with my system wine. Login works from there

We are mostly seeing this with the Windows version in fact. I assume you were on Linux?  

We've had one report this helped this issue, please try it!

In the Windows search box enter Xbox and choose Xbox Networking under Settings. Wait until it has finished checking the network then hit “Fix it”.  

I am sorry but yesterday's attempt to fix this issue in our servers failed. Work on the issue will resume tomorrow!

Sorry about that.