search

dessant / buster

Captcha solver extension for humans, available for Chrome, Edge and Firefox
https://addons.mozilla.org/en-US/firefox/addon/buster-captcha-solver/
GNU General Public License v3.0
8.03k stars 597 forks source link

IBM Watson API doesn't work #234

Closed krisu5 closed 4 years ago

krisu5 commented 4 years ago

System

Extension

Bug description I changed the speech service to IBM Watson, location to Frankfurt and added the API key.

Doesn't solve captcha because of 403 error.

Logs

Browser:

14:15:18.233 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:18.233 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:18.233 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:18.320 [Nano] Nano Defender Activated :: google.com core.js:43:24
14:15:18.321 [Nano] Excluded :: All Generically Applied Solutions rules-common.js:250:28
14:15:18.842 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). demo line 1 > injectedScript:60301:29
14:15:18.842 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). demo line 1 > injectedScript:60304:75
14:15:18.887 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:18.887 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:18.887 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:18.904 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). 2 demo line 1 > injectedScript:261:18
14:15:18.905 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:18.905 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:18.915 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). showOriginal.js:143:22
14:15:19.144 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.144 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.144 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.146 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.146 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.146 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.147 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.147 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.147 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.202 [Nano] Nano Defender Activated :: www.google.com core.js:43:24
14:15:19.203 [Nano] Excluded :: All Generically Applied Solutions rules-common.js:250:28
14:15:19.446 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.446 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.446 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.446 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.446 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.446 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.516 [Nano] Nano Defender Activated :: google.com core.js:43:24
14:15:19.516 [Nano] Excluded :: All Generically Applied Solutions rules-common.js:250:28
14:15:19.569 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.569 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.569 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.569 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.569 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.569 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.612 [Nano] Nano Defender Activated :: www.google.com core.js:43:24
14:15:19.612 [Nano] Excluded :: All Generically Applied Solutions rules-common.js:250:28
14:15:19.635 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.635 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.635 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.651 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.714 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.714 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.714 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.715 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.715 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.715 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.716 Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
14:15:19.716 Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
14:15:19.716 Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
14:15:19.779 [Nano] Nano Defender Activated :: www.google.com core.js:43:24
14:15:19.780 [Nano] Excluded :: All Generically Applied Solutions rules-common.js:250:28
14:15:19.907 MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. anchor:1633:6
14:15:21.980 MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. bframe:1633:6
14:15:24.477 Error: API response: 403, {"code":403, "error": "Forbidden"}

Client app:

2020/09/23 11:15:22.684464 Starting client (version: 0.3.0)
2020/09/23 11:15:22.684464 Receiving message
2020/09/23 11:15:22.684464 Processing message
2020/09/23 11:15:22.684464 Command: ping
2020/09/23 11:15:22.684464 Sending response
2020/09/23 11:15:22.684464 Receiving message
2020/09/23 11:15:22.703469 Processing message
2020/09/23 11:15:22.703469 Command: moveMouse
2020/09/23 11:15:22.703469 X: 416, Y: 740
2020/09/23 11:15:22.708469 Sending response
2020/09/23 11:15:22.708469 Receiving message
2020/09/23 11:15:22.822604 Processing message
2020/09/23 11:15:22.822604 Command: clickMouse
2020/09/23 11:15:22.853359 Sending response
2020/09/23 11:15:22.853359 Receiving message
2020/09/23 11:15:23.557870 Processing message
2020/09/23 11:15:23.558870 Command: moveMouse
2020/09/23 11:15:23.558870 X: 457, Y: 423
2020/09/23 11:15:23.590878 Sending response
2020/09/23 11:15:23.590878 Receiving message
2020/09/23 11:15:23.690590 Processing message
2020/09/23 11:15:23.690590 Command: clickMouse
2020/09/23 11:15:23.720932 Sending response
2020/09/23 11:15:23.720932 Receiving message
2020/09/23 11:15:24.476196 Closing client
dessant commented 4 years ago

I've just tested it with an API key from the London endpoint and it worked. Make sure to select the correct datacenter and add the API key.

krisu5 commented 4 years ago

I'm dumb, I picked "Text to Speech" instead of "Speech to Text" service. 😅

Yeah, it works alright.