error playing online
-
@panther There is one other cause of this issue that we've identified, and that is if the user has some kind of SSL/TLS proxy installed (typically found as part of parental controls software), as discussed in https://github.com/triplea-game/triplea/issues/2472. Running the OpenSSL test described in #2554 or #2472 would allow us to confirm if that's the case.
Also, I read that post on A&A.org, and it's not clear if the user removed the problematic JRE. If you read #2554 carefully, the outdated JRE that was causing the problem was installed by TripleA itself, so it is is not uninstallable via Control Panel--the user has to actually delete a folder within their profile to get rid of it. (Even if a newer version of Java is installed, the TripleA launcher will prefer the outdated JRE that was installed when TripleA was installed.) We can verify if this is the problem by having the user start a local game, open the debug console, and click the Properties button. Have them paste or attach the console output. From that we can see exactly which JRE is being selected.
Given that the user was eventually able to get PBEM working, I suspect an SSL/TLS proxy may not be in play here. So, I'd start with the second recommendation to capture the debug console properties to determine from where TripleA is picking up the JRE.
-
@ssoloff Thank you for your synopsis. I never experienced install4j installing a JRE, so that lack of own experience mislead me to somehow misunderstand that part of information when going through that issue.
Got it now and will go on troubleshooting. -
@panther if you diiscover how to uninstall it slap me! Had a similar problem with triplea insttalliing 32 bit java and still running it after having 64 bit java installed. (New hard drives) and triplea auto installed 32 bit. I should have reinstalled java before triplea I guess.
-
@prastle In case install4j autoinstalled Java when installing TripleA you will find those Java installation(s) here:
c:\program files\common files\i4j_jres\1.8.0_xxx
or (if 32bit) here:
c:\program files (x86)\common files\i4j_jres\1.8.0_xxx
Simply delete the Java version folder(s).
Don't always trust TripleA when it comes to rules questions. Know the rules before you start … and better check what TripleA has done.
-
@panther thanks
-
-
@ssoloff it was installed with admin but what I discovered is that if you install TripleA on a clean system, that doesn't have Java, it auto installs 32 bit(even with 64 bit download). If you install 64 java after it still runs the 32 bit as triplea.
-
@prastle Interesting. It may be that the 64-bit installer is bundling the wrong JRE. I'll try to reproduce.
-
@ssoloff Apart from this - is it always the latest JRE that is installed ... and does a bundled JRE installed with TripleA ever get an update?
-
@Panther We update it every now and then, but the process is difficult and not really thought out currently.
Now that I'm thinking of it, we should just have a single filename for the bundled JREs and just make the installers point to the revision. @ssoloff -
@prastle Are you sure your TripleA ships the wrong JRE?
I recall your issue only occured when invoking triplea via the commandline, in this case it's not the installers fault -
@roiex But a once installed bundled JRE will never be updated? Or is there sort of a version control?
-
The installer won't do anything when there's a JRE already installed on the system.
So no, no updating. -
-
@prastle they didn't work because 32 bit was running in background with a clean install
-
@prastle issue is simple it auto installs 32 bit if you don't have java yet
even with 64 bit dl -
@RoiEX I guess the true test would be to install java before dl triplea on a clean install
BUT
I can 100% say
since I watched it do it!
If you dl TripleA stable
It will install java
if you don't have it yet
and will screw up your 64 bit bots
then you will ask Roi wtf?
and he will help you eidt it to 32 bithopefully this jogs your memory bro
-
@roiex @ssoloff The issue has been resolved for the user. Indeed he had an older JRE in a C:\Program Files\Common Files\i4j_jres directory. It might be interesting for you that he had experienced this problem using Update 144 that had been bundled obviously!
So manually deleting 144 and using the system-wide update 151 resolved the problem. -
Thanks for the update, @panther! I'll take a look at the truststore in the build 144 bundled JRE to see if it's missing the root CA used by GitHub. I know my build 121 JRE installed from Oracle includes it, so presumably build 144 or later would also include it. I wonder if there's something defective about the bundled JREs we get from install4j?
-
@prastle I installed 64-bit TripleA (7950) on a system with no pre-installed JREs (32-bit or 64-bit). The TripleA installer downloaded the 64-bit bundled JRE (144), and I confirmed TripleA uses that JRE when started. Can you elaborate on what you saw that indicated the bundled JRE that was downloaded by the TripleA installer was 32-bit?
@Panther I installed 32-bit TripleA (7621) and 64-bit TripleA (7950) on a system with no pre-installed JREs (32-bit or 64-bit). The former installation downloaded and installed the 32-bit bundled JRE (144), while the latter downloaded and installed the 64-bit bundled JRE (144). I verified that, in both cases, I was able to download the map listing and PBF on A&A.org. So I'm not really sure why I can't reproduce the problem the user was having when using the 144 bundled JRE. It's concerning that there may be something machine-specific going on here.
@prastle @Panther Note that in both of my tests, I installed TripleA as a user without admin rights, so my bundled JREs were installed under my user profile rather than under C:\Program Files or C:\Program Files (x86). I can't see why that would change which bundled JRE was downloaded or cause a certificate validation failure, but it may be another variable worth exploring if this happens again.
The only other difference I can see between my environment and the OP's is that they were on a 32-bit machine, whereas I'm testing on a 64-bit machine. Again, nothing jumps out at me as to why that would matter for the scenario we're testing.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login