@redrum Yeah, I guess I didn't realize that the non-default dice server properties read from
dice_server/tripleawarclub.properties get stored with the save game. I had assumed the client always reads the local dice server properties based on which dice server was selected in the save game (i.e. using the dice server name as a lookup key into the local dice server property database).
So, what's happening is this... When you start the game with the latest pre-release, it stores the scheme (
https) in the save game but not the port (see https://github.com/triplea-game/triplea/pull/3277). In 9678, the default port is
80, so an attempt is made to open an HTTPS connection to the MARTI HTTP endpoint, resulting in the error above. It works in the latest pre-release because the default port is
-1, which means use the standard default port for the specified scheme.
I believe adding a
port=443 line to all dice server properties files under
dice_servers should fix the problem going forward. However, I'm not sure if that will fix your save game above, even after you re-save it using a patched pre-release, as I'm not sure if the dice server properties get re-read when loading from a save game.