EDCD / EDMarketConnector

Downloads commodity market and other station data from the game Elite: Dangerous for use with all popular online and offline trading tools.
GNU General Public License v2.0
989 stars 155 forks source link

Authentication not possible (PC) #909

Closed MartindForlon closed 2 years ago

MartindForlon commented 3 years ago

Login with your Frontier account into EDMC (4.2.0) not working on my PC. First time I experience this issue. Frontier Authentication is normally opened, I add email/password (Sign in with Frontier) like usual and press Login ... but then nothing, EDMC still shows trying to log in.

Windows 10 Locale Czech Browser Firefox 86.0 EDMarketConnector-debug.log EDMarketConnector.log EDMC

Athanasius commented 3 years ago
  1. EDMC started around 08:35, at which time it succeeded in using Refresh Token to get a new Access Token. It should also have stored the new Refresh Token at this time.
  2. Then at 14:53 the game is started and EDMC springs into action...
  3. The first attempt to get /profile from the CAPI fails with a 401.
  4. The attempt then to auth from scratch yields:
2021-03-14 14:53:51.963 - ERROR - companion.Session.dump:591: Frontier CAPI Auth: https://companion.orerve.net/profile 401 Unauthorized {"status":401,"message":"JWT has incorrect\/unexpected fields"}
2021-03-14 14:53:51.965 - DEBUG - companion.Auth.refresh:231: Trying for "Martind Forlon"
2021-03-14 14:53:51.967 - DEBUG - companion.Auth.refresh:235: Cmdrs: ['Martind Forlon', 'Karina Forlon']
2021-03-14 14:53:51.968 - DEBUG - companion.Auth.refresh:238: idx = 0
2021-03-14 14:53:51.969 - DEBUG - companion.Auth.refresh:243: We have a refresh token for that idx
2021-03-14 14:53:51.970 - DEBUG - companion.Auth.refresh:250: Attempting refresh with Frontier...
2021-03-14 14:53:52.418 - ERROR - companion.Auth.refresh:261: Frontier CAPI Auth: Can't refresh token for "Martind Forlon"
2021-03-14 14:53:52.420 - DEBUG - companion.Auth.dump:363: Frontier CAPI Auth: https://auth.frontierstore.net/token 401 Unauthorized {"message":"An error occured.","logref":"2531a26a6ead8695b4af32177402c731"}
2021-03-14 14:53:52.421 - INFO - companion.Auth.refresh:271: Frontier CAPI Auth: New authorization request
2021-03-14 14:53:52.423 - INFO - companion.Auth.refresh:277: Trying auth from scratch for Commander "Martind Forlon"
2021-03-14 14:53:52.598 - DEBUG - companion.Session.login:428: We do NOT have an access_token
2021-03-14 14:53:52.599 - ERROR - companion.Session.query:518: Frontier CAPI Auth: HTTP error or invalid JSON
  1. This then repeats over and over, ending up without an access_token each time.
Athanasius commented 3 years ago

We're going to need some extra logging to see precisely what comes back from the Frontier Auth callback. I'll look into adding some for 4.2.1.

Johnat31 commented 3 years ago

I am also having this exact same problem. EDMarketConnector.log

Windows 10 Firefox 86.0.1

Athanasius commented 3 years ago

Having worked on a branch to add some extra logging I'm wondering if this is only related to the edmc:// protocol handler.

Could anyone experiencing this try launching EDMarketConnector.exe with the --force-localserver-for-auth argument so that it uses a localhost:// listening local webserver instead ?

"c:\Program Files (x86)\EDMarketConnector\EDMarketConnector.exe" --force-localserver-for-auth

in a Command Prompt (cmd.exe) window will do this.

I'll still want to track down the actual cause, but this might get Auth working for you in the meantime.

MartindForlon commented 3 years ago

I tried it on now my laptop (where I have the same issue as was yesterday on my gaming PC) and it is working.

... and do not forget copy whole link including apostrophes ... ;)

edmc2

Athanasius commented 3 years ago

So, something is wrong, but only for some people, with the code for the edmc:// protocol handler.

My first guess is firewall/anti-virus. I know when I used to run Comodo Personal Firewall it blocked some DDE calls, which this relies on. So, do any of you with this not working (without the --force-localserver-for-auth argument) have an AV/firewall ? If so, check the logs in it to see if decided to block this.

It would have been a DDE call from your web browser of type DDE_EXECUTE, with arguments something like:

open("edmc://auth...")
Johnat31 commented 3 years ago

have added the extra line and is now working I am using avast av with firewall along with windows firewall but can see no mention of dde calls

MartindForlon commented 3 years ago

I also have avast/windows defender combo ... I see nothing there, but I'm not sure which logs exactly I should check, there was not any report that edmc might cause problems. I also did not any changes to both (they uses practically default settings). Prior this last edmc version I had no issues with authentication.

Athanasius commented 3 years ago

https://github.com/EDCD/EDMarketConnector/releases/tag/Release%2F4.2.1 is now available with the extra logging for this issue. If you can reproduce it then please attach your latest debug log file to this issue.

MartindForlon commented 3 years ago

With a 4.2.2 I logged now into frontier without issues on laptop. Will check this later today also on my gaming PC and will report back.


2021-03-17 14:07:33.090 - INFO - monitor.EDLogs.start:182: Monitoring Journal Folder: "C:\Users\xxxxx\Saved Games\Frontier Developments\Elite Dangerous"
2021-03-17 14:07:33.091 - INFO - monitor.EDLogs.start:183: Start Journal File: "C:\Users\xxxxx\Saved Games\Frontier Developments\Elite Dangerous\Journal.210315152727.01.log"
2021-03-17 14:07:33.092 - DEBUG - monitor.EDLogs.start:186: Starting Journal worker
2021-03-17 14:07:33.093 - DEBUG - monitor.EDLogs.worker:239: Starting on logfile "C:\Users\xxxxx\Saved Games\Frontier Developments\Elite Dangerous\Journal.210315152727.01.log"
2021-03-17 14:07:33.229 - DEBUG - companion.Session.login:417: changed account or retrying login during auth
2021-03-17 14:07:33.230 - DEBUG - companion.Auth.refresh:231: Trying for "Martind Forlon"
2021-03-17 14:07:33.231 - DEBUG - companion.Auth.refresh:235: Cmdrs: ['Martind Forlon', 'Karina Forlon']
2021-03-17 14:07:33.232 - DEBUG - companion.Auth.refresh:238: idx = 0
2021-03-17 14:07:33.234 - DEBUG - companion.Auth.refresh:243: We have a refresh token for that idx
2021-03-17 14:07:33.235 - DEBUG - companion.Auth.refresh:250: Attempting refresh with Frontier...
2021-03-17 14:07:33.621 - DEBUG - companion.Session.login:427: We have an access_token
2021-03-17 14:07:33.623 - DEBUG - companion.Session.start:460: Starting session```
MartindForlon commented 3 years ago

Sorry folks ... on my gaming PC it doesnt work right now, but I cannot access some websites and also discord suddenly stopped working, so it can be just internet connection failure for here.

2021-03-17 18:32:27.587 - DEBUG - monitor.EDLogs.start:186: Starting Journal worker
2021-03-17 18:32:27.588 - DEBUG - monitor.EDLogs.worker:239: Starting on logfile "C:\Users\Martin\Saved Games\Frontier Developments\Elite Dangerous\Journal.210314161340.01.log"
2021-03-17 18:32:27.767 - DEBUG - companion.Session.login:417: changed account or retrying login during auth
2021-03-17 18:32:27.768 - DEBUG - companion.Auth.refresh:231: Trying for "Martind Forlon"
2021-03-17 18:32:27.769 - DEBUG - companion.Auth.refresh:235: Cmdrs: ['Martind Forlon', 'Karina Forlon']
2021-03-17 18:32:27.770 - DEBUG - companion.Auth.refresh:238: idx = 0
2021-03-17 18:32:27.771 - DEBUG - companion.Auth.refresh:243: We have a refresh token for that idx
2021-03-17 18:32:27.771 - DEBUG - companion.Auth.refresh:250: Attempting refresh with Frontier...
2021-03-17 18:32:28.366 - ERROR - companion.Auth.refresh:261: Frontier CAPI Auth: Can't refresh token for "Martind Forlon"
2021-03-17 18:32:28.367 - DEBUG - companion.Auth.dump:368: Frontier CAPI Auth: failed with `r` False: <Response [401]>
2021-03-17 18:32:28.368 - INFO - companion.Auth.refresh:272: Frontier CAPI Auth: New authorization request
2021-03-17 18:32:28.369 - INFO - companion.Auth.refresh:278: Trying auth from scratch for Commander "Martind Forlon"
2021-03-17 18:32:28.530 - DEBUG - companion.Session.login:433: We do NOT have an access_token
Johnat31 commented 3 years ago

Seems to be working normally now thanks

MartindForlon commented 3 years ago

Seems local connection issue only. EDMC authentication is now working smoothly. Thanks!

StevenNuke commented 3 years ago

Hi, i have also same problem since v4.2.0. (excuse please my english)

EDMarketConnector.log

I trying turn off AV and FW and nothing change. To user section frontierstore i can login normaly, also trying deauthorise EDMC and new start. Authorization here is proceede normaly, but Connector still cant take token from Frontier. I really dont know, what can i do.

Athanasius commented 3 years ago

Hi, i have also same problem since v4.2.0. (excuse please my english)

EDMarketConnector.log

I trying turn off AV and FW and nothing change. To user section frontierstore i can login normaly, also trying deauthorise EDMC and new start. Authorization here is proceede normaly, but Connector still cant take token from Frontier. I really dont know, what can i do.

Two things:

  1. It looks like something is preventing your web browser from invoking the DDE path for communicating the successful authentication back to EDMC. This definitely works with Windows 10 Home and latest Firefox as the browser, that's how I test it.
  2. But it does look like we lost a bit of code somehow, for handling the auth callback being invoked by running the program again. I'll look into that and likely put out a 4.2.3 later today. In the log (and this means we do need to be checking the 'raw' log file, not just the debug one):

    usage: EDMarketConnector [-h] [--trace] [--suppress-dupe-process-popup]
                         [--force-localserver-for-auth]
    EDMarketConnector: error: unrecognized arguments: edmc://auth/?code=...
StevenNuke commented 3 years ago

So, i tried latest Firefox as main browser, as you say. Still off AV and FW. Still same result, unfortunately. And i have Win10 home. Also tried with Chrome browser.

Athanasius commented 3 years ago

Yeah, we somehow lost that bit of code I mentioned in point 2. I've just added it back and have been testing that it now works.

I'm still puzzled as to why anyone's system would be failing to invoke the DDE path for this in the first place though.

Could you please open regedit.exe and then paste in Computer\HKEY_CLASSES_ROOT\edmc\shell\open to the location bar and verify there's a ddeexec folder inside that, with a single Default key with value Open("%1") ? It should look like this:

EDMC-ddeexec-registry

StevenNuke commented 3 years ago

Yes, is it there. aaa

Athanasius commented 3 years ago

Yes, is it there.

Yet for some reason, even with Firefox, on your system the DDE method isn't invoked. A quick web search doesn't turn up anything. I can only suspect AV/security software blocking it. NB: That could be:

  1. Blocking Firefox from even seeing the registry entry
  2. Blocking Firefox from sending the DDE message
  3. Blocking EDMarketConnector.exe from listening to DDE messages
  4. Blocking the specific DDE message from being delivered to EDMarketConnector.exe

Anyway, 4.2.3, which I'll put out in a few hours time at most, should fix this, assuming that EDMarketConnector.exe is still allowed to use ShellExecute() to send the DDE message (from the extra process your browser starts) back to the main EDMarketConnector.exe process.

If that doesn't work, then I advise to launch EDMarketConnector.exe with --force-localserver-for-auth argument to use the non-DDE method:

"c:\Program Files (x86)\EDMarketConnector\EDMarketConnector.exe" --force-localserver-for-auth

StevenNuke commented 3 years ago

"... If that doesn't work, then I advise to launch EDMarketConnector.exe with --force-localserver-for-auth argument to use the non-DDE method:

"c:\Program Files (x86)\EDMarketConnector\EDMarketConnector.exe" --force-localserver-for-auth ..."

Ah, this method working, im not tried this before. Now is authorisation successful.

Athanasius commented 3 years ago

@MartindForlon @Johnat31 @StevenNuke Please try https://github.com/EDCD/EDMarketConnector/releases/tag/Release%2F4.2.3 without the --force-localserver-for-auth argument. Report back if it still doesn't work (and then use --force-localserver-for-auth in the meantime).

StevenNuke commented 3 years ago

Yes, this version is working for me. Launch via MS Edge and without --force-localserver-for-auth. Before try i manualy deauthorized EDMC via user.frontierstore.net and new authorization was successful. Thank you so much, I can't even imagine Elite without EDMC :)

MartindForlon commented 3 years ago

All works for me, tested on my gaming PC now. I'm running Firefox and 4.2.3 edmc was newly authorised (I removed old authorisation first) without any argument. Thanks much!

Leif-The-Head commented 2 years ago

So I've been experiencing this again for the last month or so. EDMC is a few versions further now, tried every step listed here. Deauthorised on frontier site, which got me past the login prompt, but then clicking approve wouldn't do anything. Now I started using --force-localserver-for-auth after another deauth, which turned out to be successful. After a restart it still would work, so I deauthed again and started again using no argument, and since then it apparently works as intended.

While that is technically resolved for me, I'd assume this isn't intended behaviour, also this might help others that come across this issue that is supposedly fixed since last major version.

Oddly enough, seems like the callback from auth tried to start another instance - at least I clicked the login twice here. This is before I fiddled with it:

2022-02-26 10:35:30.030 UTC - DEBUG - 10100:18672:18672 companion.Auth.refresh:323: Trying for "Leif"
2022-02-26 10:35:30.031 UTC - DEBUG - 10100:18672:18672 companion.Auth.refresh:327: Cmdrs: ['Leif']
2022-02-26 10:35:30.031 UTC - DEBUG - 10100:18672:18672 companion.Auth.refresh:330: idx = 0
2022-02-26 10:35:30.032 UTC - DEBUG - 10100:18672:18672 companion.Auth.refresh:335: We have a refresh token for that idx
2022-02-26 10:35:30.033 UTC - DEBUG - 10100:18672:18672 companion.Auth.refresh:342: Attempting refresh with Frontier...
2022-02-26 10:35:30.241 UTC - ERROR - 10100:18672:18672 companion.Auth.refresh:359: Frontier CAPI Auth: Can't refresh token for "Leif"
2022-02-26 10:35:30.241 UTC - DEBUG - 10100:18672:18672 companion.Auth.dump:532: Frontier CAPI Auth: failed with `r` False: <Response [401]>
2022-02-26 10:35:30.242 UTC - INFO - 10100:18672:18672 companion.Auth.refresh:371: Frontier CAPI Auth: New authorization request
2022-02-26 10:35:30.243 UTC - INFO - 10100:18672:18672 companion.Auth.refresh:377: Trying auth from scratch for Commander "Leif"
2022-02-26 10:35:30.260 UTC - DEBUG - 10100:18672:18672 companion.Session.login:694: We do NOT have an access_token
[...] Canonn Plugin logging
2022-02-26 10:35:41.379 UTC - INFO - 12704:2096:2096 journal_lock.JournalLock._obtain_lock:106: Exception: Couldn't lock journal directory "C:\Users\Leif\Saved Games\Frontier Developments\Elite Dangerous", assuming another process running: PermissionError(13, 'Permission denied')
2022-02-26 10:35:41.381 UTC - INFO - 12704:2096:2096 EDMarketConnector.__main__:353: An EDMarketConnector.exe process was already running, exiting.
2022-02-26 10:35:59.928 UTC - INFO - 19680:10264:10264 journal_lock.JournalLock._obtain_lock:106: Exception: Couldn't lock journal directory "C:\Users\Leif\Saved Games\Frontier Developments\Elite Dangerous", assuming another process running: PermissionError(13, 'Permission denied')
2022-02-26 10:35:59.930 UTC - INFO - 19680:10264:10264 EDMarketConnector.__main__:353: An EDMarketConnector.exe process was already running, exiting.

And now, after I did all that:

2022-02-26 10:52:24.147 UTC - DEBUG - 14816:8288:8288 companion.Auth.refresh:323: Trying for "Leif"
2022-02-26 10:52:24.148 UTC - DEBUG - 14816:8288:8288 companion.Auth.refresh:327: Cmdrs: ['Leif']
2022-02-26 10:52:24.149 UTC - DEBUG - 14816:8288:8288 companion.Auth.refresh:330: idx = 0
2022-02-26 10:52:24.149 UTC - DEBUG - 14816:8288:8288 companion.Auth.refresh:335: We have a refresh token for that idx
2022-02-26 10:52:24.150 UTC - DEBUG - 14816:8288:8288 companion.Auth.refresh:342: Attempting refresh with Frontier...
2022-02-26 10:52:24.393 UTC - DEBUG - 14816:8288:8288 companion.Session.login:688: We have an access_token
2022-02-26 10:52:24.394 UTC - DEBUG - 14816:8288:8288 companion.Session.start_frontier_auth:642: Starting session
[...] Canonn Plugin logging
Athanasius commented 2 years ago

So I've been experiencing this again for the last month or so. EDMC is a few versions further now, tried every step listed here. Deauthorised on frontier site, which got me past the login prompt, but then clicking approve wouldn't do anything. Now I started using --force-localserver-for-auth after another deauth, which turned out to be successful. After a restart it still would work, so I deauthed again and started again using no argument, and since then it apparently works as intended.

2022-02-26 10:35:30.260 UTC - DEBUG - 10100:18672:18672 companion.Session.login:694: We do NOT have an access_token
[...] Canonn Plugin logging
2022-02-26 10:35:41.379 UTC - INFO - 12704:2096:2096 journal_lock.JournalLock._obtain_lock:106: Exception: Couldn't lock journal directory "C:\Users\Leif\Saved Games\Frontier Developments\Elite Dangerous", assuming another process running: PermissionError(13, 'Permission denied')
2022-02-26 10:35:41.381 UTC - INFO - 12704:2096:2096 EDMarketConnector.__main__:353: An EDMarketConnector.exe process was already running, exiting.

This implies there's something going wrong with the "is another process running? Yes, does this invocation have the edmc:// argument? Yes, forward the message" code in your use case. Using --force-localserver-for-auth explicitly avoids that scenario. There's a small possibility that an anti-virus/software firewall could interfere with the edmc:// process.

ergose commented 2 years ago

Turned on my PC to play and seeing this exact issue today. Haven't run into it before. Current EDMC version is 5.3.1+24e8912 (updated recently).

The --force-localserver-for-auth workaround from the command line isn't working for me. With or without that flag, I get sent to Frontier's auth page, drop in my details from my password manager, and click the 'Login' button. Page just refreshes/flashes quickly clearing the fields. EDMC stays on 'Logging in...' until I close it.

I logged in to the main Frontier site, logged out, did same through same auth page via the Frontier help login, tried opening EDMC while already logged in, etc. User and password is working through Frontier's flow.

URL before and after login (same - used OMITTED where wasn't sure if should be public): https://auth.frontierstore.net/auth?response_type=code&audience=frontier,steam,epic&scope=auth%20capi&client_id=OMITTED&code_challenge=OMITTED&code_challenge_method=S256&state=OMITTED&redirect_uri=edmc://auth

From Debug Log:

2022-03-07 18:37:19.742 UTC - DEBUG - 11500:864:864 monitor.EDLogs.worker:414: Entering loop...
2022-03-07 18:37:19.770 UTC - DEBUG - 11500:11504:11504 companion.Session.login:678: changed account or retrying login during auth
2022-03-07 18:37:19.772 UTC - DEBUG - 11500:11504:11504 companion.Auth.refresh:323: Trying for "OMITTED"
2022-03-07 18:37:19.773 UTC - DEBUG - 11500:11504:11504 companion.Auth.refresh:327: Cmdrs: ['OMITTED']
2022-03-07 18:37:19.774 UTC - DEBUG - 11500:11504:11504 companion.Auth.refresh:330: idx = 0
2022-03-07 18:37:19.774 UTC - DEBUG - 11500:11504:11504 companion.Auth.refresh:335: We have a refresh token for that idx
2022-03-07 18:37:19.774 UTC - DEBUG - 11500:11504:11504 companion.Auth.refresh:342: Attempting refresh with Frontier...
2022-03-07 18:37:20.344 UTC - ERROR - 11500:11504:11504 companion.Auth.refresh:359: Frontier CAPI Auth: Can't refresh token for "OMITTED"
2022-03-07 18:37:20.344 UTC - DEBUG - 11500:11504:11504 companion.Auth.dump:532: Frontier CAPI Auth: failed with `r` False: <Response [401]>
2022-03-07 18:37:20.344 UTC - INFO - 11500:11504:11504 companion.Auth.refresh:371: Frontier CAPI Auth: New authorization request
2022-03-07 18:37:20.344 UTC - INFO - 11500:11504:11504 companion.Auth.refresh:377: Trying auth from scratch for Commander "OMITTED"
2022-03-07 18:37:20.563 UTC - DEBUG - 11500:11504:11504 companion.Session.login:694: We do NOT have an access_token
2022-03-07 18:37:36.039 UTC - INFO - 11500:11504:11504 EDMarketConnector.AppWindow.onexit:1697: Starting shutdown procedures...
Athanasius commented 2 years ago

@ergose Try deauthorizing EDMC:

  1. Go to https://user.frontierstore.net/
  2. Login
  3. Approve
  4. Click 'Authorized Applications' from the menu on the left -> https://user.frontierstore.net/linked
  5. Find "Elite Dangerous Market Connector (EDCD/Athanasius)"
  6. Click the "DEAUTHORISE" button on that line.
  7. Try EDMC login again (restart if needs be to trigger it).
Athanasius commented 2 years ago

Also, for everyone reporting issues with Frontier Auth and EDMC, please always state what kind of account you're trying it with: Frontier, Steam or Epic (Games Store).

ergose commented 2 years ago

Update to above. I just thought to try edmc://auth in a new tab to see what would happen (Edge). I get a pop-up: 'This site is trying to open EDMarketConnector.exe. A website wants to open this application.'. Clicking that 'Open' button then results in 'malformed payload'. May be nothing, but felt best to add it.

@Athanasius - Trying that now. As for account type. I have a Frontier account with a different login, but it's linked to my Steam account. Steam is where I bought and installed Elite from.

Athanasius commented 2 years ago

Update to above. I just thought to try edmc://auth in a new tab to see what would happen (Edge). I get a pop-up: 'This site is trying to open EDMarketConnector.exe. A website wants to open this application.'. Clicking that 'Open' button then results in 'malformed payload'. May be nothing, but felt best to add it.

Yes, going to only edmc:// will result in an error, because it's meant to have the response code on the end of it. If it wasn't doing that in the normal auth flow (i.e. your browser not showing that pop-up, or otherwise proceeding) then that points to the issue being at Frontier's end. All we pass is the information in that URL you cited/elided, asking for the response to be sent to edmc://.

@Athanasius - Trying that now. As for account type. I have a Frontier account with a different login, but it's linked to my Steam account. Steam is where I bought and installed Elite from.

That counts as a Steam account. I'd try always doing this using the Steam option on the frontier website, not the Frontier account login. You'd hope Frontier would realise it's a Steam account in this case and always do the right thing, but ....

ergose commented 2 years ago

@Athanasius - Well. Wasn't expecting that. This time it may be Frontier-side. Got to Step 2, logged in. Same behavior. Login page refreshes and doesn't go further.

To clarify, If I login from the 'www' site and try to login via that form then, no issues. From user.frontierstore.net -> auth.frontierstore.net or via the EDMC tab open. Same behavior.

Athanasius commented 2 years ago

@Athanasius - Well. Wasn't expecting that. This time it may be Frontier-side. Got to Step 2, logged in. Same behavior. Login page refreshes and doesn't go further.

To clarify, If I login from the 'www' site and try to login via that form then, no issues. From user.frontierstore.net -> auth.frontierstore.net or via the EDMC tab open. Same behavior.

If you can't even login to user.frontierstore.net then contact Frontier support as it's definitely an issue their end.

ergose commented 2 years ago

@Athanasius - Bingo. Got it. Thanks. You're comment on using the Steam option nagged on me so I tried it with fresh open of EDMC. It redirected to Steam and I logged in that way. That worked on Frontier's site and sent me to the Approve page. Clicked Approve and then EDMC now says 'Authentication Successful'

Further suggesting Frontier change/issue after clicking the approve button...

Oops! An Error Occurred
The server returned a "500 Internal Server Error".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
Leif-The-Head commented 2 years ago

Also, for everyone reporting issues with Frontier Auth and EDMC, please always state what kind of account you're trying it with: Frontier, Steam or Epic (Games Store).

That counts as a Steam account. I'd try always doing this using the Steam option on the frontier website, not the Frontier account login. You'd hope Frontier would realise it's a Steam account in this case and always do the right thing, but ....

This is indeed a weird behaviour. Had to come back here since my authentication period ran out. Trying today with Frontier Acc no dice, although it worked last time. Using Steam Acc first try. Now the jist: I'm running on an account that predates Elite being on Steam, I've only switched to a Steam installation to use VR more than a year ago, and every other login on account-related frontier pages worked better using the frontier login over the Steam login. I should try this again with my second account which doesn't officially run on steam (also predating Elite on Steam) and never retrieved a code for it, but having it used through the same Steam installation in the past.

mpetricone commented 1 week ago

EDMarketConnector-debug.log EDMarketConnector.log

update, It's entirely possible I was logging in with a wrong account. Version 5.12.0+cc6e200

I'm no longer to login after the latest update. With similar symptoms as above . I recently install EDCopilot, I don't know if that might affect anything.