search

ElevenPaths / thethe

thethe
GNU Affero General Public License v3.0
116 stars 30 forks source link

Using Plugins #11

Closed Phil-ThePower-Pearce closed 4 years ago

Phil-ThePower-Pearce commented 4 years ago

hi, using the docker version.

Is there a way to troubleshoot the plugins/apikeys? Ive added all my apikeys, and when I try to use them, no data is returned. They work on some APIs, but not for example haveibeenpwned, or virustotal. I'd like to see the response returned or an error message. Is this possible?

deibit commented 4 years ago

Hello.

We are working on a visual feedback, task stacking and a spinner to notice the activity.

Try to reload the project and see if the results are there (some users have noticed this issue).

In any case, you can do:

docker logs -f <container name> Containers thethe_celery and thethe_server should print some useful debug information.

Thank you.

Phil-ThePower-Pearce commented 4 years ago

thanks for replying. ok, just did a log on celery [2020-02-05 13:13:20,768: INFO/MainProcess] Received task: server.plugins.haveibeenpwned.haveibeenpwned[99162245-e52c-40fd-9a8e-0a39394fff62] [2020-02-05 13:13:20,769: WARNING/ForkPoolWorker-1] **No API key...!** [2020-02-05 13:13:20,769: INFO/ForkPoolWorker-1] Task server.plugins.haveibeenpwned.haveibeenpwned[99162245-e52c-40fd-9a8e-0a39394fff62] succeeded in 0.0008234660017478745s: None [2020-02-05 13:13:26,472: INFO/MainProcess] Received task: server.plugins.haveibeenpwned.haveibeenpwned[ff66e1c6-caaa-4108-a7fb-11e51fc1f1cc] [2020-02-05 13:13:26,473: WARNING/ForkPoolWorker-1] **No API key...!** [2020-02-05 13:13:26,474: INFO/ForkPoolWorker-1] Task server.plugins.haveibeenpwned.haveibeenpwned[ff66e1c6-caaa-4108-a7fb-11e51fc1f1cc] succeeded in 0.0008022190013434738s: None

I assume this is what Im looking for... The haveibeenpwned api is entered, and I can do a manual api call with the same key. http://tinyurl.com/rmbed2l

I looked at the plugin code the urls and api calls look exactly the same as my manual ones

deibit commented 4 years ago

Hi.

We found the possible cause. It is because Celery cached the API_KEYS an they are not refreshed upon invocation. We fixed this in https://github.com/ElevenPaths/thethe/commit/2947e9177de4cf68028bf8fab81aa074ac248579

Eventually, you can restart the celery container:

docker container restart thethe_celery

to refresh the api keys.

Thanks.