57b4f9cd82
Since flaresolverr has a specific endpoint for healthchecks (/health) it could make sense to use it insted of the root. Also, this will not flood the log when using INFO LOG_LEVEL (default) with entries like: 2024-01-15T17:49:56.962520+01:00 hassio addon_db21ed7f_flaresolverr[816]: 2024-01-15 17:49:56 INFO 127.0.0.1 GET http://127.0.0.1:8191/ 200 OK
Home assistant add-on: Flaresolver
Thanks to everyone having starred my repo! To star it click on the image below, then it will be on top right. Thanks!
About
FlareSolverr starts a proxy server and it waits for user requests in an idle state using few resources. When some request arrives, it uses puppeteer with the stealth plugin to create a headless browser (Firefox). It opens the URL with user parameters and waits until the Cloudflare challenge is solved (or timeout). The HTML code and the cookies are sent back to the user, and those cookies can be used to bypass Cloudflare using other HTTP clients.
NOTE: Web browsers consume a lot of memory. If you are running FlareSolverr on a machine with few RAM, do not make many requests at once. With each request a new browser is launched.
Project homepage : https://github.com/FlareSolverr/FlareSolverr
Based on the docker image : https://hub.docker.com/r/flaresolverr/flaresolverr
Configuration
Webui can be found at http://homeassistant:port
Installation
The installation of this add-on is pretty straightforward and not different in comparison to installing any other Hass.io add-on.
- Add my Hass.io add-ons repository to your Hass.io instance.
- Install this add-on.
- Click the
Savebutton to store your configuration. - Start the add-on.
- Check the logs of the add-on to see if everything went well.
- Carefully configure the add-on to your preferences, see the official documentation for for that.
Support
Create an issue on github