[PicardHSV]

Edit by jiaz: see here for latest update, https://board.jdownloader.org/showpo...4&postcount=16


Heute mal was anderes, in der Accountverwaltung wird jetzt beim Premiumdienst filefactory der o.a. Fehler angezeigt.

Zuerst hatte ich an VPN oder Hosterprobleme gedacht und entsprechend alles ausprobiert, dem ist aber nicht so. Über Firefox konnte ich mich normal einloggen und die Kontoeinstellungen stimmten alle, Premium noch länger aktiv, Passwort richtig hinterlegt etc.

23.08.22 08.18.03 <--> 29.08.22 14.16.29 jdlog://9949211370661/

[pspzockerscene]

Wir haben nichts geändert und warten derzeit auf Antwort von Filefactory zu diesem API Problem.

[Jiaz]

[auweia]

dasselbe hier.
Ich warte gern geduldig

[Jiaz]

Evtl hilft es wenn auch ihr mal den Filefactory Support entsprechend kontaktiert Die sollen ruhig wissen/merken das deren Änderung für Probleme gesorgt hat

[auweia]

Jiaz, danke für den Tip!
Habe gerade den support von FF angeschrieben.

[needtakehave]

I also have this problem. I contacted Filefactory and am waiting on a reply.

[Daywalker]

Hallo, seit ca 2 Tagen bekomme ich in der Accountübersicht bei meinem Filefactory.com Account die Meldung bei Status angezeigt:
Invalid authorizathion Key

Den Fehler hab ich so noch nicht gesehen und hab keine Ahnung wie ich das lösen kann. Hab den Account schon entfernt und neu zugefügt, aber das hat nichts genützt!

Hoffe ihr könnt mir da Helfen?

greetz

[Jiaz]

@Daywalker: siehe https://board.jdownloader.org/showpo...86&postcount=5

[Daywalker]

Originally Posted by Jiaz

@Daywalker: siehe **External links are only visible to Support Staff**...

Ja der ist leider manchmal nicht der schnellste! Das heißt dann abwarten und Tee trinken!

[needtakehave]

I got a reply from Filefactory.

——

JDownloader is not currently compatible with FileFactory. We discovered a security issue related to their app, so we had to disable their access.

[FBD]

Von einem user im chat der nach eigenen Angaben eine Antwort vom FileFactory support bekommen hat:

JDownloader is not currently compatible with FileFactory. We
discovered a security issue related to their app, so we had to disable their access.
Please use another method to download

Hab ihm empfolen die gesamte Antwort nochmal per Ticket einzureichen.
Hört sich (imho) nach einer Ausrede an um eigene Serverprobleme zu vertuschen...

[Jiaz]

JDownloader is not currently compatible with FileFactory. We
discovered a security issue related to their app, so we had to disable their access.
Please use another method to download

At least some sort of reaction. We don't know what security issue they are talking about
as they have not tried to contact/inform us in any form (not on our filefactory account, not by mail) and still do not react/answer on our support tickets/mails. Please contact their support and ask them to get in contact with us (support@jdownloader.org or on our mails/tickets) and provide us more details about this security issue so we can check and work on it and get back a working plugin for their paying premium customers.

[GWT10]

I just got this response from Andy over at Filefactory.

"We will work with JD to come up with a solution for this problem"

So according to them, they are apparently reaching out to you all.

Frankly I find it highly disturbing that Filefactory would suddenly now put a "DO NOT use JDownloader!" warning on their premium questions home page. Especially after years of safe Filefactory/JDownloader use. -

[User0]

Not sure where to post. Searched in the Plugins Forum but there were no similar posts. The only other recent posts having to do with FileFactory concerned speed issues & VPN but my issue is different. So I'll try here.

According to FileFactory support, they're no longer supporting JDownloader.

Today I got a never-before-seen JD error on my FileFactory premium plugin in JD2 Account Manager: "Invalid authorization key."

I contacted FF support & here's their reply:

"JDownloader is not currently compatible with FileFactory. We discovered a security issue related to their app, so we had to disable their access."

A link was provided suggesting alternatives. In that linked KB article, JD was criticized for being "Open Source" and possibly harmful.

I wrote back that, on macOS, JD 2 is the only viable bulk HTTP d/l manager, and that in the many years I've used the official version of JD, I've never experienced any "security issue" that the AppWork team failed to address or resolve.

Anyway, I'm wondering if the JD team has any add'l info about this. Worse case scenario, FileFactory on JD2 is now kaput and I guess I'll never buy another subscription to that hoster.

[Jiaz]

Meanwhile we've received feedback from filefactory concerning this topic.

"JDownloader is not currently compatible with FileFactory.
We discovered a security issue related to their app, so we had to disable their access."

apparently someone has abused the api authkey (it's part of open source of plugin) from JDownloader for brute forcing account logins and therefore they have disabled it. We're working on restoring plugin functionality and currently waiting for further feedback from their support.
Due to different timezones between us and them, it might take some more days till plugin will be working again.

[raztoki]

If I recall correctly, I did advise them that JD open source, the authkey for memory was just session akin to a cookie. They made the API and even had documented it publicly. One could say its not an API just for JDownloader, it was designed for any app to use if they wished. Anyway its good to see progress has been made =]

[needtakehave]

I got another reply overnight from Andy @ Filefactory.

----


Hi there, we have provided JDownloader with the information they need to get the app working again. Hopefully, it will be fixed within 24 hours. You MAY need to download a new update to the program, but we're not sure yet. Apologies for the inconvenience, and thanks for your patience!

[Jiaz]

Will be fixed with next plugin update in a few minutes

[User0]

just checked, 5:38 AM GMT -8

updated JD 2 & FF is now working. no more key authentication error.

thx, appreciate the fix.