Possible migration issue with current rc? System carrier moved from Fedex to eShipper

[ChrisNolan]

I changed my docker-compose.yml to use the new rc32 images... I brought it down, and then up again... all looked fine.

But then I was getting "No active carrier connection found to process the request" as a response to my API calls... looked at :3000/connections/system and I saw my 'fedex-ca-tracking' carrier-id still there so... oh wait, but teh big blue label next to that wasn't saying "Fedex" anymore, it was saying "Eshipper"? Huh? Checked :5002/admin/providers/eshipperconnection/ and sure enough, there was my fedex-ca-tracking instead of having it over at :5002/admin/providers/fedexconnection/

Any ideas what could have done that? Was it a bad setup on my end, or an issue with one of the 'migrations' or something?

Let me know if I can check any logs or anything.

In the mean time I'm just going to re-setup my tracker under Fedex (I don't see an option to 'move' it or anything).

Thanks

[ChrisNolan]

Huh... now fedex's dev portal is having problems and not responding. just my luck ;-) Any hints on how I can 'move' that one back over to fedex then in the database so I can still use my api secret attached to it? (of course I didn't save my secret anywhere else)

Update: nvm dev portal back up and running so I've gotten a new secret after all. Got to explore a few parts of the system I hadn't seen yet though... got confused when my 'eshipper-connections' table was empty... I think the 'system' ones must be somewhere else... found the graphQL for it in the GET_SYSTEM_CONNECTIONS const but that was as far as I got on that journey.

[danh91]

Hi @ChrisNolan ,

🤔 That would definitely be a migration issue.

What version did you have before?

Two ways to fix the FedEx -> eshipper issue.

• connecting to your database and changing the carrier_code field to from eshipper back to FedEx

• ssh to your docker container with docker run and use karrio shell.

I will share the commands from my pc

[ChrisNolan]

I was on... rc23 before I believe, might have been 24. I dont need the commands at this point, I've gotten it moving again by re-creating my system carrier as I only had a handful in there.