radical solution to the shadow root problem#1300
radical solution to the shadow root problem#1300AlexFozor wants to merge 15 commits intoFlareSolverr:masterfrom
Conversation
|
This is seems to be working and with much faster response time. |
|
It's working with YGG How to do with docker image : Build image : Update docker compose file : |
|
Prebuild image in AMD64 : Prebuild image in ARM64 :
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as duplicate.
This comment was marked as duplicate.
Hello, For me is not good : Launching web browser... |
AMD or ARM ? I have try only my ARM build to be honest |
|
@TheNexter the AMD64 image work perfectly too. I use this one |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
One note: DrissionPage seems to be Chinese. Aside from the international relations concerns that some people may have, leading some users to be hesitant to integrate FS into their workflows, most of the development for FlareSolverr is in English. Do we want to introduce a major dependency that's (about half) written in another language? For instance, one of the docstrings for a Drission function: """调用获取元素的方法
:param locator: 定位符
:param timeout: 超时时间（秒）
:param index: 获取第几个，从1开始，可传入负数获取倒数第几个
:param raise_err: 找不到时是否抛出异常
:param method: 调用的方法名
:return: 元素对象或它们组成的列表
"""The param names are understandable because that's just how Python is written, but will the average contributor have any idea what these take? Timeout is obvious, but what's the method param? What does this function return? We could translate as needed, but that's less than ideal Just raising this to see how other people feel about the inclusion of other languages. It certainly complicates things as you get further down the line and need to work on bug fixes, patches, etc. |
This comment was marked as duplicate.
This comment was marked as duplicate.
That's exactly it, I agree. The author of drissionpage has a separate website with documentation. Machine translation is not so bad now, it was enough to create this working version. |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Getting this thread back on track, @AlexFozor do you have any idea if this project supports the return of status codes and response headers? There's an open issue #1162 relating to this, due to Selenium's refusal to add support. Bringing proper status code and response header support back to FlareSolverr would open up the door for its inclusion in quite a few more workflows There are several that I work on myself that would see a huge benefit from FlareSolverr, but rely on returned status codes rather than text, so they haven't been able to benefit yet. |
|
I have already implemented this, and according to my tests it works as it should. There is a risk of getting a timeout when waiting for http responses, then the header and response code will not be transmitted correctly, but I have not encountered any problems in my tests. Waiting for a response now occurs with a timeout of 5 seconds, it is possible to make it longer. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Doesn't work for me |
|
@ChristophorusReyhan I had the same issue before disabling ipv6. |
I've disabled ipv6 via sysctl, I don't think that's it? or am i missing something? |
|
i think this same issue g1879/DrissionPage#365 (comment) in this issue g1879/DrissionPage#242, the dev said it's because it's too old, but i don't think so because i already updated everything |
|
Still not working here, with ipv6 disabled, with or without flaresolverr:
image: alexfozor/flaresolverr:pr-1300
container_name: flaresolverr
environment:
- LOG_LEVEL=${LOG_LEVEL:-info}
- LOG_HTML=${LOG_HTML:-false}
- CAPTCHA_SOLVER=${CAPTCHA_SOLVER:-none}
- TZ=Europe/Paris
- DRIVER=nodriver # same with or without this line
- PGID=1000
- PUID=1000 |
Use this version : 21hsmw/flaresolverr:nodrivertest with environnement DRIVER : nodriver |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Okay, this works but I cant seem to reach the site from prowlarr? |
This image and the compose I posted works from prowlarr for me. Your error must be elsewhere. flaresolverr:
image: 21hsmw/flaresolverr:nodrivertest
container_name: flaresolverr
environment:
- LOG_LEVEL=${LOG_LEVEL:-info}
- LOG_HTML=${LOG_HTML:-false}
- CAPTCHA_SOLVER=${CAPTCHA_SOLVER:-none}
- TZ=Europe/Paris
- DRIVER=nodriver
- PGID=1000
- PUID=1000
networks:
- internal |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Hello, it seem that the proposed solution now fail since some days and this message appear on my logs I use the |
|
I was also using |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
|
(YGG) Since yesterday, FlareSolverr using the Docker image 21hsmw/flaresolverr:nodrivertest has stopped solving challenges. Below are the logs showing the issue: yaml Has anyone experienced a similar issue or have suggestions for troubleshooting? |
Try with this image it work : alexfozor/flaresolverr:pr-1300-experimental. But yes Flaresolverr 21hsmw version don't work at this moment. I think he'll do an update soon. |
|
I activate the DEBUG LEVEL to have more information |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Hello, seems this doesn't work anymore? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@ilike2burnthing I spend half a day reading a bunch of issues, commits, etc. Trying this and finding out it was not maintained, trying that, etc. Btw |
I dared to replace selenium with DrissionPage. For me it solves the latest shadow root problem in 100% of tests, better than #1272 with 60% (for me).
I suggest putting this code in a separate branch drission-page and making a docker build.
I have very little experience writing in Python, so don't judge me too harshly. I am open to criticism and suggestions for improving the code.
Important!
If you encounter any errors, please check that you are using the latest image / latest commit of the branch
Along with the error description and logs, please write full information:
Latest builds:
alexfozor/flaresolverr:pr-1300- always latest multi-platform build (amd64, arm64)alexfozor/flaresolverr:pr-1300-experimental- experimental image with Cloudflare Turnstile transform by browser extensionCommunity builds with unknown version, check update time:
nexter92/flaresolverr:amd64- amd64nexter92/flaresolverr:arm64- arm64Thanks:
@TheNexter for the first working docker image
Notes:
UPD:
alexfozor/flaresolverr:pr-1300-experimental