Discussion So what's happening with Fdev fixing the API , this time ?

Trade Finder System is Up now ;

In French : Les utilisateurs de TFS vont pouvoir mettre à jour la nouvelle version qui prend en charge les APIs de market et shipyard.
Merci de votre patience :)
 

Maylor Rom

Banned
Just tried to connect the API to EDDI & EDMC ...again

I'm unable to connect with FRONTIER API ... invalid credentials

I'm using Revo, to remove EDMC, then do a clean reinstall, after entering my Email & Password, I'm then given the CODE, after entering the code

EDMC says 'invalid credentials'

https://github.com/Marginal/EDMarketConnector/issues/242

I have them both working now.

I did not uninstall or remove any software, they just started working again after the recent update yesterday.

I doubt you needed to do all that software removal to fix something that was not broken on your "client" side.

The Frontier API uses the same credential set as the Game Elite uses when you log into your game account. You get the "invalid credentials" when these do not match.

Is it at all possible you have used the wrong username or password with EDMC, a typo, or thinking it is EDMC website credentials when you meant to use Frontier Elite Game credentials?

What I am saying is that I made no software changes to my EDDI/EDSM/EDMC software, including any change to credential sets, and all was working. Then Frontier updated twice, the first update took the API down, the second fixed it and it is up again, and without any changes on my "client" end, it all started working again.

I'm inclined to believe it is not your installs, but your credential set. Once you discover it, you will feel (as I often do) foolish you did not see it, or realize it sooner.

No offense.
 
Last edited:
I have them both working now.

I did not uninstall or remove any software, they just started working again after the recent update yesterday.

I doubt you needed to do all that software removal to fix something that was not broken on your "client" side.

The Frontier API uses the same credential set as the Game Elite uses when you log into your game account. You get the "invalid credentials" when these do not match.

Is it at all possible you have used the wrong username or password with EDMC, a typo, or thinking it is EDMC website credentials when you meant to use Frontier Elite Game credentials?

What I am saying is that I made no software changes to my EDDI/EDSM/EDMC software, including any change to credential sets, and all was working. Then Frontier updated twice, the first update took the API down, the second fixed it and it is up again, and without any changes on my "client" end, it all started working again.

I'm inclined to believe it is not your installs, but your credential set. Once you discover it, you will feel (as I often do) foolish you did not see it, or realize it sooner.

No offense.

I logged out of my machine via the Launcher, and re-entered my Email and Password, the Launcher accepted the CODE, I'm now logged in......again.

AFTER the Launcher success !, I did a clean re-install of EDMC and ...."Just tried to connect the API to & EDMC, again I'm unable to connect with FRONTIER API, EDMC says 'invalid credentials "

So I have no-idea what 'credential set' I have to remove / rejoin to be able to get the API working ?
 

Maylor Rom

Banned
I logged out of my machine via the Launcher, and re-entered my Email and Password, the Launcher accepted the CODE, I'm now logged in......again.

AFTER the Launcher success !, I did a clean re-install of EDMC and ...."Just tried to connect the API to & EDMC, again I'm unable to connect with FRONTIER API, EDMC says 'invalid credentials "

So I have no-idea what 'credential set' I have to remove / rejoin to be able to get the API working ?

Your Fontier API on EDSM/EDMC relies on an API Key. The API Key in EDSM relies on the credential set of the Elite Game. Once bonded, they act as one. I suspect you may need to "reset" your API Key with EDSM/EDMC.

I did reset my API Key with them as I also changed my commander name in doing an Elite CMDR Game Clear, and the API Key is also associated with the CMDR Name. To make it all work again, I reset the API Key and then used the Frontier delivered code and NEW API Key in both.

See if that may be the problem.

There are two phases to this issue. In either phase you can get "Invalid Credentials" errors, but for different reasons.

The first phase is a bad cookie file that needs deleting. The second phase is "It's working but the companion API is still flaky"

I found I had to do the following to fix EDMC.

First, make sure that game and EDMC are running the latest version. Exit from both and make sure neither are zombie tasks. You can look on the Details tab of the windows Task Manager, or just reboot.

Go to the local AppData folder for EDMC (there is no folder in roaming, or at least there shouldn't be!). Do not have EDMC running at this point. You can get to the AppData folder by pressing Windows + R to get a Run window open and then pasting this in "%appdata%\..\Local\EDMarketConnector".

Move anything starting with cookie to a backup folder (move, not copy).

Start EDMC. It may ask for credentials and verification at this point. If it does, enter your account details and check your e-mail inbox for the verification code.

Start the Elite and head into the actual game to force a starting point journal entry to be made. Sitting at the main menu is not good enough.

EDMC might ask for verification at this point (after loading your journal and getting your username from here). It might ask for credentials and then verification.

Even after you do all this the cAPI may still be unreliable. Press Update a couple of times before writing it off.

Hopefully the EDMC team will automate this soon, or at least publish some documentation on formalising the fix process.

It gets even more complicated if you are using multiple windows accounts to run multiple instances of the game and EDMC at the same time.

This also may help.
 
Last edited:
Your Fontier API on EDSM/EDMC relies on an API Key. The API Key in EDSM relies on the credential set of the Elite Game. Once bonded, they act as one. I suspect you may need to "reset" your API Key with EDSM/EDMC.

I did reset my API Key with them as I also changed my commander name in doing an Elite CMDR Game Clear, and the API Key is also associated with the CMDR Name. To make it all work again, I reset the API Key and then used the Frontier delivered code and NEW API Key in both.

See if that may be the problem.

^^ .. ok cheers..... more stuffing around at my end :)
 
I have the same problem as Sutex. All I get out of the client is invalid credentials as well.

I am using EDMC 2.4.3 on Windows 10.

A bit more diagnostic information would be a help. Does EDMC allow for tracing or provide detailed diagnostic information somewhere ?
 
I have the same problem as Sutex. All I get out of the client is invalid credentials as well.

I am using EDMC 2.4.3 on Windows 10.

A bit more diagnostic information would be a help. Does EDMC allow for tracing or provide detailed diagnostic information somewhere ?


Done all the bits suggested , nothing is working, API is not working for me just have to wait ....
 
I noticed that it is connecting/sending something to EDDN but when it tries to do a fetch, no idea of what, it gets the Error: Invalid Credentials.
 
Frontier are well aware the cAPI isn't fully working 100% and are still trying to figure out what's going on with it...

Latest from Dav: "We’ve seen a few thousand hits to the Companion API in the last 24 hours, so it’s definitely working for some people some of the time. We’re patching out a bit more logging this afternoon to try to get a feel for the failure rate and to see if there are any patterns to the failures."

A pinned message from yesterday, on the EDCD Discord server.

Regards o7
 
Latest from Dav: "We’ve seen a few thousand hits to the Companion API in the last 24 hours, so it’s definitely working for some people some of the time. We’re patching out a bit more logging this afternoon to try to get a feel for the failure rate and to see if there are any patterns to the failures."



Yeah mate, that's me re-entering my credentials :eek:
 

Maylor Rom

Banned
I have the same problem as Sutex. All I get out of the client is invalid credentials as well.

I am using EDMC 2.4.3 on Windows 10.

A bit more diagnostic information would be a help. Does EDMC allow for tracing or provide detailed diagnostic information somewhere ?

Not that I am aware, but I'm sure there is logging for it somewhere either on the client <(in your directory tree for EDMC) or the EDMC website under your account possibly.

I am not an expert on this piece of software or the API.

I also use Windows 7 as opposed to Windows 10, so that may have some influence on how EDMC performs, as well as how the API and logging are implemented.

In the thread I pointed to, there seems to be many more experts there working on possibilities, but everyone here should know that the Frontier API was NOT DESIGNED for use by third party support sites, and those sites, on there own, figured out how to use the API to grovel and present data on THEIR sites. Frontier offers support on the API for Frontier's use, not third party, i.e. EDDI/EDSM/EDMC and others. This leaves the support sites on their own when changes occur on Frontiers side, and all of us are left scrambling for answers and solutions.

My play is to install the third party stuff on my side (client), get it working and leave it alone until there is some change or update by the third party developer. If it stops working, 99% of the time, it is Frontier's changes which prevent it from working, and there is nothing to do but wait it out.

Done all the bits suggested , nothing is working, API is not working for me just have to wait ....

On your issue, I still believe it is a client side problem. Did you clear your "browser cookie" associated with Elite and EDMC as suggested in the "fix" on the post I included?

The "invalid credential" issue has two reasons, one is clearing the cookies in your browser, which contain usernames and passwords associated with the API issue.

Sorry I could not be of further assistance.
 
Last edited:
Back
Top Bottom