zfcsoftware / cf-clearance-scraper

This library was created for testing and training purposes to retrieve the page source of websites, create Cloudflare Turnstile tokens and create Cloudflare WAF sessions.
MIT License
227 stars 37 forks source link

Proxy api not getting ready #40

Closed Crease29 closed 1 day ago

Crease29 commented 3 days ago

Description

Since the latest update 3 hours ago the proxy does not get ready anymore for me when running it in a GitHub action. Any idea what it could be?

Full steps to reproduce the issue

Run it in a GitHub action and wait for it to be ready.


            -   name: Start Cloudflare Clearance Scraper
                run: |
                    docker run -d -p 3000:3000 \
                        -e PORT=3000 \
                        -e browserLimit=20 \
                        -e timeOut=30000 \
                        zfcsoftware/cf-clearance-scraper:latest
                shell: bash

            -   name: Wait for Cloudflare Clearance Scraper to be ready
                run: |
                    while ! curl -s http://localhost:3000 > /dev/null; do
                      echo "Waiting for Cloudflare Clearance Scraper..."
                      sleep 1
                    done
                shell: bash

Issue Type

Support

Operating System

Linux

Do you use Docker?

Docker

zfcsoftware commented 3 days ago

Only express timeout was added in the last update. -e timeOut=30000 \ this part -e timeOut=60000 \ Can you try to change it to the following?

Crease29 commented 3 days ago

I tried increasing the timeout to 60000 but it didn't help, unfortunately. Instead of using the latest docker image tag now, I've pinned it to 2.0.4 and it works just fine again.

zfcsoftware commented 3 days ago

I tried increasing the timeout to 60000 but it didn't help, unfortunately. Instead of using the latest docker image tag now, I've pinned it to 2.0.4 and it works just fine again.

The timeOut env variable came as a string and there was a problem with the express.timeout function. I updated it now, I tested it with the latest version, can you please test it with the latest version?