Make sure you are logged into the launcher with your Paradox account. Then click on Games and Refresh.
That did the trick : logged out, closed Launcher, re-opened Launcher, logged in + Games/Refresh. Thanks!
Make sure you are logged into the launcher with your Paradox account. Then click on Games and Refresh.
v1.2.0-345R showed up in the Paradox Launcher today when I logged on. Thank you.
Here is my concern, Paradox/HBS... you OWN the game that is in the launcher and yet you didn't make the patch available for a WEEK after it was available on Steam and GoG. I mean this in all the kindest ways... but WHAT.THE.F@#$!! Shouldn't your own game launcher get the update AT THE SAME TIME? Or at the very least, BEFORE a non-Paradox/HBS gaming platform? This feels completely back-asswards for how you should be running your game launcher.
/end_constructive_criticism
Can I ask why not? Will that cause a problem? Because that has been the go-to fix basically since first release.A tiny note: only run the launcher as an admin in case something is wrong, to determine whether your problem is an access problem. Don't run it as an admin regularly.
Not working on OpenSUSE Tumbleweed or Fedora 28 for me either. I get the same error output. The:is not working on my ubuntu
"Execute patch: downloading repo metadata: server returned a non-2XX status code"
We're looking into the issue at the moment - I'll get back as soon as we know what's up.
All traffic to and from api.paradoxplaza.com must get through. Maybe check your firewall settings?Not working on OpenSUSE Tumbleweed or Fedora 28 for me either. I get the same error output. The:
part seems to indicate that it can't communicate with the paradox server properly?Code:"Execute patch: downloading repo metadata: server returned a non-2XX status code"
Not working on OpenSUSE Tumbleweed or Fedora 28 for me either. I get the same error output. The:
part seems to indicate that it can't communicate with the paradox server properly?Code:"Execute patch: downloading repo metadata: server returned a non-2XX status code"
Hi, can you give us an estimate on when the "Coming soon for Mac" is supposed to be released?
I've looked into it myself and I think my problem is due to my local setup. You are correct that it is CDN related, encrypted communication with api.paradoxplaza works well (amazon), but un-encrypted port 80 traffic to some CDN in Dallas throws errors (404). This seems to be due to AWS being exempt from my VPN in the firewall so the second CDN gets the wrong address. If I run everything over the VPN it seems to work just fine.We seem unable to reproduce it locally at the office. It appears to be CDN-related and as such can be different depending on where you are located (the best bugs to hunt!). If possible, and if the problem persists, can I ask you to mail Support with the cpatch.log file?