Byparr

[!IMPORTANT] This software does not guarantee (only greatly increases the chance) that any challenge will be bypassed. While this tool passes the initial browser check, Cloudflare and other captcha providers likely require valid network traffic originating from the user’s public IP address to mark a connection as legitimate. If any website does not pass the challenge, please run troubleshooting steps and check if other websites work before you create an GitHub issue.

Options

Proxy Recommendation

Recently I've partnered with a new in town proxy service - ProxyBase - to offer affordable proxy services that seems to work seamlessly with Byparr! Using my affiliate code byparr (case sensitive!) when signing up will not only get you access to their cost-effective ($0.69/GB with occasional promotions at the time of writing) proxy network but will also help support the continued development of this project. ProxyBase's proxies can significantly improve your success rate when bypassing anti-bot challenges. Check out ProxyBase and enhance your Byparr experience!

Tags

• v*.*.*/latest - Releases considered stable
• main - Latest release from main branch (untested)
• pr-{number} - Pull request images for testing (automatically cleaned up when PR closes)

Usage

[!IMPORTANT] Support for NAS devices (like Synology) is minimal. Please report issues, but do not expect it to be fixed quickly. The only ARM device I have is a free Ampere Oracle VM, so I can only test ARM support on that. See #22 and #3

Docker Compose setup

1. Review settings in compose.yaml.
2. Start the service:

docker compose up -d

Docker install

1. Pull and run the image:

docker run -p 8191:8191 ghcr.io/thephaseless/byparr:latest

1. Optional: set env vars using -e or --env-file.

Local install

1. Install uv.
2. Run uv run main.py
3. Profit.

API Docs

Once running, open:

• http://localhost:8191/docs
• http://localhost:8191/ (redirects to /docs)

Troubleshooting

Docker troubleshooting

1. Clone repo to the host that has issues with Byparr.
2. Run docker build --target test .
3. Depending of the build success:
4. If run successfully, try updating container or if already on newest stable release create an issue for creating new release with new dependencies
5. If build fails, try troubleshooting on another host/using other method

Local troubleshooting

1. Download uv
2. Download dependencies using uv sync --group test
3. Run tests with uv run pytest --retries 3 (You can add -n auto for parallelization)
4. If you see any F character in terminal, that means test failed even after retries.
5. Depending of the test success:
6. If run successfully, try updating container or if already on newest stable release create an issue for creating new release with new dependencies
7. If test fails, try troubleshooting on another host/using other method