Error: Invalid Credentials #242
Comments
|
+1 here. I should remark that when I ran ED 2.4 this evening, the launcher asked me to type in my credentials before it would let me launch the game and I had to paste in a code from a Frontier email. I'd run the game yesterday so I don't think my credentials had expired. |
|
The Frontier cAPI is still not properly up yet. |
|
@Berbe wrt ROSS, EDMC submits some data from the companion API and some data from journals. It will still be able to submit journal data to EDDN |
|
EDDI is similarly affected (I raised a ticket for that) |
|
2.40.0 ....since i have updated to ED 2.4 the "Invalid Credentials started"...have been deleting the cookies, upgraded to 2.4.3.msi....but no.....it does send information to Inara, but not to shipyard or so I understand it's at Frontiers end? |
|
same issue v2.4.3 msi used to re-install after uninstall, deleted reg keys and files in app data before re-install. I got a verification notice, which worked but still getting the same message. The program detects where I am in ED but does not seem to send data. |
|
Me too. Can we help, or are we certain it's at the Frontier end? |
|
Have same issue, but just tried a clean install of the older 2.4.1 and still getting the same problem so i don't think its an issue with 2.4.3.. probably some change in the background with ED 2.4 has broken things. |
|
This just happened to me too. I started the ED:H 2.4 update (still syncing). I then updated EDMarketConnector. After a few botched key-entry attempts, I finally got through but then hit "Invalid credentials". Uninstalling EDMarketConnector, deleting the "Marginal" HKCU registry key for it and its %localappdata%\EDMarketConnector folder, then reinstalling it did not correct the problem. |
|
Howdy peeps, we know about this one and it's out of our power to fix, FDev are working on the server end. Stat tuned |
|
Frontier has reacted on the cAPI issue submitted to them and has acknowledged it yesterday. Wait and see... [EDIT] |
|
it should be no surprise, as it's on FD's end but just FYI, the Mac version 2.4.2 has same issue |
|
Frontier are considering this issue of the "highest priority" so we'll have a fix sooner rather than later, one hopes. |
|
Can't wait when it will be finally fixed! |
|
Thanks Draeth. I just started using EDMC a week before the update and I was already hooked. :) Not to mention how all of the data to all of the websites helps the whole ED community. |
|
Did the update this morning fix the issue? I'm still getting the error. |
|
You may have to just re-enter your credentials. For Eddi I had to re-authenticate with a code, but for the market connector I just re-entered my password. All
OK now
Shaun
… On 3 Oct 2017, at 14:45, Sean ***@***.***> wrote:
Did the update this morning fix the issue? I'm still getting the error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Still have it, 2.4.2.0 |
|
Its still there. With 2.4.2 and 2.4.3. Changing the PW in ED and entering the new does not help either. |
|
It started working for me the other day. I didn't have to do anything.
…On Tue, Oct 3, 2017 at 10:18 AM Loutreck ***@***.***> wrote:
Its still there. With 2.4.2 and 2.4.3. Changing the PW in ED and entering
the new does not help either.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#242 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ae4WKzULo6fOK-9p9Xy-sua7dYreIx1pks5sokJOgaJpZM4Pk-6b>
.
|
|
2.4.3 removed cookie, re-authenticated with validation-code....but alas...still there |
|
Still "Error: Invalid Credentials" with 2.4.3. I tried some relogin every 30 minutes after ED Update but it want connect. Also reinstallation (deinstallation, registry clean, AppData clean) dont work |
|
No commodity update to EDDN logs in the past 7 days. The project is collapsed? |
|
Folks, Frontier broke the API with the 2.4 patch. They are aware and have committed to fixing it. There's nothing we can do but wait. |
|
Dreath, the API was listed as fixed in the patch that was released today. |
|
Well, then the statement "Fixed Companion API authentication problems" in the latest patch note is "doubtful". |
I have v2.4.3.0 and it seems to work occasionally, but there doesn't seem to be a pattern to it. I'd venture to guess that it's affected by the load on Frontier's cAPI server(s) at any given moment. |
No. Last I heard Frontier are adding some more logging to their cAPI server to diagnose. |
|
I installed completly from fresh on a new PC and can't get EDMC to work at all because of it. Its very frustrating. I feel for you guys having to answer queries for a problem not of your making |
|
I have two Elite accounts, and I run them on different machines. On one account all I had to do was clear the EDMC cookie file and re-validate and I was up and running, and once running it has never failed, not once. On my other account there is nothing I can do to get it to work. I can press 'Update' a thousand times and it never works. What is interesting is that it appears to be the validation that's not working. I get the e-mail after removing the cookie file and type the code in (taking great care not to make any errors) and it asks for the code a second time. I type it in again (still taking a lot of care not to screw it up) and the validation window goes away, and immediately it says "Invalid Credentials" and will not work, no matter how many times I press Update. I do think there is something wrong with the cAPI, and it's effecting a subset of accounts. If there is further detail I can provide to help the process, please let me know. |
@chrismartinau You think well: the problem is on the game developer server side, not clients, as Marginal stated and confirmed (as do all 3rd-party developers). You can follow the core issue & resuolution on the cAPI thread on Frontier forum. For some people it works, and it seems that when it does it might only temporary. The rest of use remain stranded outside. It seems it is not the first time it happens, but as long as people continue to buy their useless products (ie skin packs) and money is pouring in on their side, their management probably won't take such trouble more seriously than that and allocate time so developers can trace this kind of issue better. Be patient for now and in the future refrain on buying supplemental content until Frontier show deep signs of changes in its priorities of what to process is all you can do. |
|
Where is this "Cookie file" referenced a few times? |
|
cAPI should now be working for everybody. If it's not working for you:
If you're prompted for a verification code then your email and password settings are OK. |
|
No joy @Marginal . I've just installed the app for the first time about 10 mins ago, and I can't get past the "invalid credentials" error after entering my login details. Have double checked, and I'm able to log into the Elite with the same creds |
|
JAY!!!>>>MACversion works!...will try PC now Including Engineerd modules : Great :D Compliments on that too!! |
|
Works for me, Windows version. Last time I removed the cookie files was a day ago, I didn't need to renew them today, it just worked. |
|
Excellent! Next to the Mac version, Win7 version worked as well.....just needed to remove cookie |
|
"If you see "Invalid Credentials" after getting and entering the validation code then the cAPI is still not working for you." Any solution yet for those who are still not able to use it? Thanks! |
|
Works for me now too. 👍 |
|
@Marginal - brilliant. Seems to be working fine now! Thanks |
|
Still having trouble, updated to new version and deleted cookie. Getting invalid credentials and a greyed out update button. |
|
@ziceman Double-check your email and password settings. |
|
Tried that, even a complete re-install of edmc. Doesn't seem to be saving the login details no sign of the verification check upon re-install. |
|
After updating to the most recent version and deleting the cookie files, I'm now able to log in finally. Thanks @Marginal |
Same here. 1st machine was upgraded to windows 10 and works fine (have not yet updated this machine to latest EDMC 2.4.4.0 - i.e still using 2.4.3. Shall I update or is there a chance for loosing functionality on this machine as well???)
|
|
@Marginal All working now, came back to it fresh this morning and all working as it should be. I must have missed something, who knows what! |
|
@neutronium See advice above |
|
@Marginal I suppose you wanna leave that ticket open until only a marginal (no play with words I promise) amount of players is still impacted? I let you close it when you see fit. |
|
@Berbe yes. I believe that lingering issues (if any) are just due to caching at the server end. Will leave this open for a while to catch any reports. |
Marginal I am sorry. I tried these steps. I even deleted the whole C:\Users\you\AppData\Local\EDMarketConnector\ folder. No luck. The strange thing is that Elite: Dangerous Launcher and Elite: Dangerous game itself as well as EDDiscovery app tool are all loading OK. |
|
@neutronium try deliberately setting the wrong cmdr name and then restart edmc twice, try your own details on the 3rd restart |
|
@inorton I just reinstalled after reading your message and ... IT WORKED out of the box! i.e. just after installation, it asked for the verification code without me having to do anything! I am so happy! Thank you guys! |
and others
My problem does not seem to be related to #165. I am using EDMC for Windows (
7 x64).Everything worked fine in
v2.4.1.0onv2.3Elite: Dangerous.After having patched the game to
v2.4, I updated EDMC tov2.4.3.0and all I can get is theError: Invalid Credentialsmessage.Here is what I tried:
v2.4.3.0<User>\AppData\Local\EDMarketConnectorHKCU\Software\Marginal\EDMarketConnectorOf course, deleting the cookie (and even more deleting all data) had me reauthorized the app, which I did seamlessly.
I see on ROSS logs that other EDMC Windows clients are working fine. Is there something I haven't checked which could be wrong on my side? Or could there be something wrong with the
v2.4cAPI? Or maybe have you changed something on your part regarding login (I aven't found anything in the commits)?Note: I did not try
v2.4.2.0, I jumped fromv2.4.1.0tov2.4.3.0, might that mean somehow the problem lies in the cAPI?The text was updated successfully, but these errors were encountered: