challenge-bypass-extension icon indicating copy to clipboard operation
challenge-bypass-extension copied to clipboard

Page gets stuck on "Proceeding..."

Open Car0lina5 opened this issue 1 year ago • 7 comments

When the extension is active I can't get past any Cloudfare captcha, not even the website "https://captcha.website/". If I disable the extension, the captcha works normally.

  1. Using the Floorp browser, click on the extension
  2. Click on get more passes
  3. Try to complete the captcha

Expected behavior The page will get stuck on "Proceeding..."

System (please complete the following information):

  • OS: Windows 11
  • Cloudflare tokens or hCaptcha tokens? Cloudfare
  • Browser: Floorp Browser
  • Browser Version: v10.13.0
  • Privacy Pass Version: 3.0.5

Additional context In other forks of Firefox the extension works normally, but for some reason in Floorp it doesn't work. This browser is getting a little popular and I would like to start using it. I don't know if anyone will be able to help me, but it doesn't hurt to try. Thanks anyway.

16 05 2023  -  01 36  -

Car0lina5 avatar May 16 '23 04:05 Car0lina5

Hi @Car0lina5,

Thanks for openning an issue.

We would need more details to better investigate. Could you provide an HAR file, recording your session when accessing captcha.website, and attempting to complete it?

To do so:

  1. Open the developer console. see
  2. Click on the Network tab
  3. Now, go to https://captcha.website
  4. Once you reach the state you mention in your first ticket, being stuck at "Proceeding", export the HAR by clicking on the cog icon of the network tab.

thibmeu avatar May 24 '23 16:05 thibmeu

Hello, I don't understand much about this but I hope I collected it correctly.

HAR File

Car0lina5 avatar May 24 '23 16:05 Car0lina5

Having the same problem, the POST request gets blocked by the firefox extension.

1RandomDev avatar May 26 '23 13:05 1RandomDev

Facing the same issue. @thibmeu

RupomChowdhury avatar Jul 29 '23 13:07 RupomChowdhury

I am also reproducing the POST request being blocked by the Privacy Pass extension (version: 3.0.5; installed from AMO; ID: {48748554-4c01-49e8-94af-79662bf34d50}) in Firefox (version: 118.0a1 (2023-08-07); update channel: nightly; build ID: 20230807215239; OS: Windows_NT 10.0 22621).

cURL syntax of the blocked POST request
curl 'https://captcha.website/' -X POST \
  -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/118.0' \
  -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/jxl,image/webp,*/*;q=0.8' \
  -H 'Accept-Language: en-US,en;q=0.5' -H 'Accept-Encoding: gzip, deflate, br' \
  -H 'Referer: https://captcha.website/?__cf_chl_tk=mgXnY4tr1xI06AaJaFThqjVKMOMmIaXFc3oRwLXEGtM-1691538698-0-gaNycGzNCNA' \
  -H 'Content-Type: application/x-www-form-urlencoded' -H 'Content-Length: 2330' \
  -H 'Origin: https://captcha.website' -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Upgrade-Insecure-Requests: 1' \
  -H 'Sec-Fetch-Dest: document' -H 'Sec-Fetch-Mode: navigate' -H 'Sec-Fetch-Site: same-origin' -H 'Sec-Fetch-User: ?1'

bb010g avatar Aug 09 '23 01:08 bb010g

Also replicating this behavior in Firefox Developer Edition.

OS: MacOS 13.5 Browser: Firefox Developer Edition 117.0b5 (64-bit) Extension Version: 3.0.5 (Installed from Firefox Addons Store

I went ahead and pulled up the extension debugger and it appears the root cause is the request being made by the extension is getting a 403 in response from Cloudflare. I've attached the HAR for the request made by the extension.

pp_request.har.txt

Not sure if someone just changed something on the back end right before I submitted this (I was typing this response so no changes were made on the browser when it happend) but I was somehow issued 60 tokens while not even looking at the "Just a moment" tab.

Will definitely be keeping an eye on it to see if it is actually working.

RickyGrassmuck avatar Aug 09 '23 07:08 RickyGrassmuck

This bug with the page being stuck in "Proceeding" does not seem to happen with Firefox 119.0.1. Major fix to the extension is being tracked in #400.

thibmeu avatar Dec 21 '23 11:12 thibmeu