Inara updates, bug reports, requests
When you try to link your accounts, you may receive the http error 400 about expired tokens. It's an issue on Frontier's end that I cannot solve on Inara. Fortunately, the solution is simple - please give it a few days and it will start to work later (probably when the access token on their cAPI server expires). If the error 400 appeared later and it worked before, try to reauthenticate as said in the error message (may be just a regular reauth forced by Frontier). Alternatively, you can try to use the workaround below. If even that won't work, it's the problem described above.
Please vote for the issue on the official bug tracker: https://issues.frontierstore.net/issue-detail/21258
Possible workaround: Try to connect the account while you are in the game. It may work.
Game data and imports not available for console commanders and PC players with Legacy game version
Inara supports only the Live game version (so PC Horizons 4.0 and Odyssey) since game update 14, thus all the game data on the site and the commander data imports work only for those game versions.
07 May 2022, 2:19pm
07 May 2022, 4:25pm
ArtieHello, I should probably rename that tab - it provides a list of nearest possible expansion targets, so not all inhabited star systems are in there (they cannot be an expansion target, for example because there is too many factions already).
Ahh, OK got it - thanks :-)
And now a suggestion for a potential tweak to the Odyssey items list https://inara.cz/components/#tab_items: it would be awesome if there were a button to remove the greyed-out (i.e. useless) ones.
09 May 2022, 2:14pm
I'm having same problem as Schimz.
(There was a problem with Frontier's service while requesting the data. Please wait a couple of hours and then try to repeat your request.
[httpCode: 0, fetchCode: 28])
Could you adjust my import date too please? Relogged a lot because of this last cg and i didn't know that cause a problem. I'll be careful next time.
Huge thanks
Last edit: 09 May 2022, 4:25pm
09 May 2022, 6:55pm
In outfitting there is a 2D Corrosion Resistant Cargo Rack left, presumably from a former CG.
And it would be great to have an extra column with the applied discount(s) in the modules lists. Preferably in the way [20%] [2.5%], not just the calculated product.
09 May 2022, 8:56pm
HoleyMcMoleyArtieHello, I should probably rename that tab - it provides a list of nearest possible expansion targets, so not all inhabited star systems are in there (they cannot be an expansion target, for example because there is too many factions already).
Ahh, OK got it - thanks :-)
And now a suggestion for a potential tweak to the Odyssey items list https://inara.cz/components/#tab_items: it would be awesome if there were a button to remove the greyed-out (i.e. useless) ones.
WaylongwayHi Artie,
In outfitting there is a 2D Corrosion Resistant Cargo Rack left, presumably from a former CG.
And it would be great to have an extra column with the applied discount(s) in the modules lists. Preferably in the way [20%] [2.5%], not just the calculated product.
Thanks for the suggestions, that may be useful - both added to the list (and the 2D CRCR was removed, not sure why it was there).
Berkay BakuninHello Artie,
I'm having same problem as Schimz.
(There was a problem with Frontier's service while requesting the data. Please wait a couple of hours and then try to repeat your request.
[httpCode: 0, fetchCode: 28])
Could you adjust my import date too please? Relogged a lot because of this last cg and i didn't know that cause a problem. I'll be careful next time.
Huge thanks
The import date was adjusted to tomorrow, as even today's journal has troubles.
09 May 2022, 11:18pm
ArtieZemedelphosFor some reason, the site will not save my Diamondback Explorer's ID tag. It keeps saying it doesn't match Inara's records, even though I'm not trying to use an inara nexus supporter tag.
The ship in question is Mark Paul, whose Id is X-PLOR.
The "X-????" ident is currently reserved for the custom Inara idents (as seen in the ship edit), so it may not work with the own idents in this format. But I will probably remove this restriction later on.
Ah thank you for the info. I picked the tag well before I signed up for Inara, so I had no idea.
I just though it'd be funny to have an on-the-nose tag for my exploration ship.
12 May 2022, 7:38am
I seem to have the same problem as Schimz and Berkay.
I cant import my cmdr data anymore.
Same error.
There was a problem with Frontier's service while requesting the data. Please wait a couple of hours and then try to repeat your request.
[httpCode: 0, fetchCode: 28]
I had some problems of the last few days to import.
Some times it would take very long, other times, just not do it all together, and ask me to try again a bit later.
But now, it just started showing the error instead.
Sorry for the inconvenience.
Thanks.
12 May 2022, 10:21am
I'm also having the same problem
"There was a problem with Frontier's service while requesting the data. Please wait a couple of hours and then try to repeat your request.
[httpCode: 0, fetchCode: 28]"
It says the issue is happening for the 10th, but I also did heavy relogging yesterday for the CG, so that may also cause issues I suspect.
Did not know relogging could cause a problem, sorry!
Thanks
12 May 2022, 8:20pm
I'd like to report a bug with the mission visibility.
If a Squadron Mission is set to "Exclude Recruits":
Bug or unexpected behaviour:
- It will still appears in the MISSIONS SHORTLIST for recruits.
Behaving correctly:
- It does not appear in the mission list or under "Other Missions"
- The content of the mission itself is unavailable if accessed through the mission shortlist.
Cheers and thanks again for the awesome work with Inara!
12 May 2022, 8:54pm
ArtieBoth import dates were adjusted, please try again.
It works again.
Thank you very much!
13 May 2022, 10:46am
Cluster FoxHi Artie !
I'd like to report a bug with the mission visibility.
....
Thanks for the report! I will take a look at that for the next Inara update.
13 May 2022, 7:30pm
I recently came to notice a bunch of locations that were wrongfully listed as Odyssey Surface Settlements, whilst in reality they are Surface Ports/Stations or Horizons Surface Settlements in game. Now I know that this was because their data wasn't updated in a long time, so that's what I did with the help of a couple of friends, updating these locations by using tools such as EDMC so that their station page reflects their actual type of station in game.
A problem that I noticed is, being that some of these locations are Horizons Surface Settlements, they couldn't be updated via normal means like EDMC and such, so their pages had to be manually edited, but by doing so some wrong information persisted. For example, the following Horizons Surface Settlement that I personally edited shows to have small landing pad(s) available, which is not the case in game --> https://inara.cz/station/58003/
And here comes the request: I'd like to understand if it's possible to edit more information in the case of an Horizons Surface Settlement, such as the landing pads since, obviously enough, this type of stations do not have landing pads of any kind. If this is not possible, then maybe you could add/change information "presets" of the station types, such that, if one gets their type changed to an Horizons Surface Settlement, things such as Landing Pads and Services are shown as unavailable or similar; even if someone mistakenly changes a normal surface port/station to this type, I imagine it would be overwritten by the first player that uploads their data like what me and my buddies did as mentioned above.
I thank you for your time, and I wish this request of mine can be helpful in highlighting some possible improvements to one of my most used websites of all time.
Link to Inara Discord: https://discord.gg/qfkFWTr