Ferdi: Unable to import my franz account

Created on 22 Aug 2020  Â·  19Comments  Â·  Source: getferdi/ferdi

Hi!
(1) I startet with opening the link "https://api.getferdi.com/import" in my browser which produced "Could not login into Franz with your supplied credentials. Please check and try again". I do have a working franz account and can login into my meetfranz account without any problems (https://meetfranz.com/login)!
(2) Then I created a new getferdi account through the app itself with the "same" cretentials as my existing franz account.
(3) when opening "https://api.getferdi.com/import" in the browser again I get "There was an error while trying to import your account: - There is already a user with this email"

Any chance to import my settings from meetfranz and how?
Best regards!

bug

Most helpful comment

The same is happening to me.

All 19 comments

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.75. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

The same is happening to me.

Also getting the same issue

I am having this same issue. I tried to delete and reimport my Franz account to the Ferdi server (because of other issues I'm having with Ferdi) and my problem has exactly the same symptoms.

When Ferdi try to authenticate to the Franz API, it is now receiving a 400 Bad Request reply, with a message "Could not verify request". Seems Franz API has changed its requirements...

For the login request, it is now necessary to add the following header:
x-franz-source: Web

same

When Ferdi try to authenticate to the Franz API, it is now receiving a 400 Bad Request reply, with a message "Could not verify request". Seems Franz API has changed its requirements...

For the login request, it is now necessary to add the following header:
x-franz-source: Web

Can someone get this change into a pull request? It seems fairly easy to implement.

@dgervalle Can you state a source for your suggestion?

Could you come up with a pull request for this change? I guess the appropriate place would be app/Controllers/Http/UserController.

This just happened to me. No fix still after 2 months?

This just happened to me. No fix still after 2 months?

That's an unfair statement. If you have the coding skills simply add the fix suggested by @dgervalle to app/Controllers/Http/UserController, and verify whether that helps. A PR is always welcome!

If you're looking for a software that is run by a full-time development team, please head over to Franz. The 3 €/month are worth it, it pays their rent. Note that they don't provide a support contract, but you can freely shout at them on their bug tracker when you pay, I think they don't complain. Also, their releases are stable for what I can tell. Less features, less freedom, but more stability.

You choose. Thank you for your understanding!

I personally use Ferdi quite often (and like it). So in case nobody will have done it until I'll have the time in the coming days, I will then do it if it's really just that little thingy.

Seems they not only changed the required headers.

The only thing I can get out of the Franz API is this 401 response:
{ message: 'User credentials not valid', code: 'invalid-credentials', status: 401 }

No clue what's required to get this working, but it's not only about the headers.

That's an unfair statement. If you have the coding skills simply add the fix.

I don't have the skills @bittner. You launched this app in hopes of getting users, and users need this fix. If you feel that it is not worth your time to fix this issue then either say it clearly so we don't expect a fix, or put a donate link in your website, I'd gladly donate your hourly rate to fix this issue. You choose.

I don't have the skills @bittner. You launched this app in hopes of getting users, and users need this fix. If you feel that it is not worth your time to fix this issue then either say it clearly so we don't expect a fix,

I don't want to go into arguing. I'm just explaining things.

Your profile says, "Product Designer that codes". This statement conveys you can do coding. And even if you can't, this does not give you the freedom to treat people – you don't pay – like contractors that miss a deadline. This is just not how Open Source works. Period.

or put a donate link in your website, I'd gladly donate your hourly rate to fix this issue. You choose.

Thanks for asking. Please, go ahead and donate at https://opencollective.com/getferdi. You don't need to cover an actual hourly rate (you can, though; my employer's customers pay 200 CHF/USD + tax per hour for me, usually with half a day minimum amount to book). Really, any amount will do. Of course, there is no commitment from any of us. But, of course, someone will be motivated when you give (probably with a matching amount of motivation).

In Life, You Always Meet Twice

It's really just to treat each other as we should. Think, what if we meet at the next developer conference? Will we be able to look each other in the eyes? (Note that I'm talking in the names of all maintainers, not just about myself.)

@mcdope It might worth to look into this again once https://github.com/getferdi/ferdi/pull/1033 gets merged. If Franz has changed the authentication protocol, it'll probably be propagated to Ferdi after that. Otherwise, we might need to reverse engineer Franz's authentication, but that would be a bit ridiculous (since Franz is already source available, at least).

On the other hand, this issue falls in line with the worrying trends of trying to ban alternative clients (like Ferdi) from online apps (see Gmail, Facebook login issues, Skype call issues, etc.) Maybe we should set up integration tests for such regressions, but just look at how that ended up for youtube-dl...

As far as I have seen in the Franz source the authentication is unchanged. I'm suspecting something like a Domain Whitelist. Though I haven't tried using the exact user agent of Franz, maybe that will help.

Edit: Just tried again setting all the headers Franz sets in the current version (according to sourcecode), plus this time I've set source to "Desktop" instead of "Web" (in case there is some CORS security magic or domain whitelist preventing it if Web) and the user-agent to the same Franz is using. Still getting the same 401 response.

No clue how to fix this :man_shrugging: For "desktop" source there can't be any whitelist, so it must work. I think this is something deeper, maybe the used http library doesn't support the encryption scheme used by the Franz server or something like that. But just guessing here.

As far as I have seen in the Franz source the authentication is unchanged. I'm suspecting something like a Domain Whitelist. Though I haven't tried using the exact user agent of Franz, maybe that will help.

Edit: Just tried again setting all the headers Franz sets in the current version (according to sourcecode), plus this time I've set source to "Desktop" instead of "Web" (in case there is some CORS security magic or domain whitelist preventing it if Web) and the user-agent to the same Franz is using. Still getting the same 401 response.

No clue how to fix this For "desktop" source there can't be any whitelist, so it must work. I think this is something deeper, maybe the used http library doesn't support the encryption scheme used by the Franz server or something like that. But just guessing here.

Did you have any success with manual export/import (which was also broken last time I tried)? Or this is a separate issue?

@TheGrave haven't tried

Was this page helpful?
0 / 5 - 0 ratings

Related issues

webworker01 picture webworker01  Â·  3Comments

ammarmalhas picture ammarmalhas  Â·  3Comments

kytwb picture kytwb  Â·  3Comments

sschaefa picture sschaefa  Â·  3Comments

yourcontact picture yourcontact  Â·  3Comments