-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frontier CAPI error #2048
Comments
Can confirm this is an issue, I only started noticing it after ED:O Update 16 and updating EDMC to 5.9.2 this week. I haven't played much over the last three months or so but don't recall it giving errors in January-March.
Relevant logs:
Deauthorizing through https://user.frontierstore.net/ and relaunching EDMC to force authorization gets the following in the logs:
|
I see this happening outside the carriers too. While in cruise for example. |
2023-08-05 14:08:32.245 UTC - INFO - 13332:9220:9220 EDMarketConnector.main:359: An EDMarketConnector.exe process was already running, exiting. |
I think the issue conny is having is a different error. Spinning that one off for a more immediate fix in #2057 |
Yea, could have been another issue yes. I solved it temporary by using a flag to use local database (or what it was called) and then it worked fine. |
I can confirm this issue under Linux as well. Could this be due to the fact that shipyard is not available for this carrier i am docking at? Just a though.
|
What flag did you use to make this work? |
I think this issue is because fleet carrier not always offer all services like shipyard etc, if one fails it should still update market etc. Just tested this on another (not my) fleet carrier with shipyard enabled, then there was no errors |
"C:\Program Files (x86)\EDMarketConnector\EDMarketConnector.exe" --force-localserver-for-auth Still see CAPI: misc.Error though (while on a carrier) but it works once I am ingame and fly about. |
Testing this on my own carrier with shipyard (but no ships for sale) and outfitting I still get the CAPI 500 error I reported while docked. It does not seem to error in other systems. |
I think the CAPI 500 on Shipyard is indicative of something FDEV changed in U16. No ETA on a fix yet but we'll keep looking into it. |
It seems like this issue has been resolved (for me at least) I will keep this thread open just in case anyone else encounters this error again. |
According to sources, the issue was resolved on FDEV side. Closing due to that. |
Please complete the following information:
Describe the bug
When you are currently docked at any Fleet Carrier, EDMC will fail update and will spit out the error "Frontier CAPI: Misc. Error"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should properly update and say "Last updated at xx:xx:xx"
Screenshots
Additional context
It does not seem to occur when docking at normal stations and only seems to happen when docked at Fleet Carriers
EDMarketConnector-debug.log
The text was updated successfully, but these errors were encountered: