301 can't login error
Hey guys a friend of mine is getting a 301 can't post because can't login to the aa.org forums error.
I troubleshot his system with a working account (my own) and despite being able to log in to the site, tripleA just can't seem to do it with the same information. I can post on the same accounts from my computer just fine.
Any help is appreciated.
Hmm...maybe have him check his java ? Sometimes old ones can hide and still be there, but if it worked before one would think that's not it, although if he recently updated java, it could be.
Is he on windows ?
It is not only the installation of the latest stable that is necessary but there are also issues with special characters in user names.
I would recommend that you/your friend either check the above mentioned support forum and topic or open a thread there including the full error message. We will get it sorted, then.
Ok. Thanks for help guys. Latest Java is installed, latest TripleA is installed, and there are no username issues.... but we'll go over it again.
and I have to laugh at LaFayette, TripleA is having issues logging in to A&A.org to post game files from TripleA.
Yes TripleA and AA.org are obviously different organizations, however TripleA uses AA.org as a go between for play by forum players. So it's a tripleA (or supporting software) issue, not an aa.org issue, which is why I am posting here. My post could have been more clear.
Hehe, well deserved, I realized a bit later that night that it was probably play by forum via A&A.org that was having issues.
Latest java is likely the issue and we've been having some debates whether to always bundle a java version with TripleA to help avoid these issues. It seems like doing that, at the cost of a larger download (IIRC by about 30MB), is probably worthwhile.
Latest Java is installed, latest TripleA is installed, and there are no username issues.... but we'll go over it again.
Have you checked for an outdated Java in "i4j_jres"?
Doing the same procedure as started in https://forums.triplea-game.org/post/21961
might help to resolve the issue.