Exception: Error getting browser User-Agent. <urlopen error [WinError 10054] #1119
Open
4 tasks done
Labels
Comments
|
Try several other test URLs. |
ilike2burnthing
added
the
more information needed
|
I have tried 50 test URLs, but none of them passed the test. @ilike2burnthing test URLS: Logged Error Messages |
|
Weird. Provide the response for Can you try |
|
@ilike2burnthing |
I've also put 1.1.1.1 to the test and came up with the same error. |
ilike2burnthing
added
help wanted
|
1 for this. I am getting same error. Output from |
|
having the same issue here |
4 tasks
|
possibly some helpful info: running natively on my windows desktop it uses a newer chrome version (123 vs 120) is there a possible way to get the chromium version to force update? or is it possible to change the user agent in some way? |
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.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
v120 is the latest release on the stable source. To use v123 you can change to the rm chromedriver
sed -i 's/bullseye/testing/g' /etc/apt/sources.list
apt update
apt install -y chromium chromium-common chromium-driver
apt autoremove -yThen restart the container and see if v123 makes a difference. |
|
damn, same error |
4 tasks
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.
|
I think ive made some progress in identifying the problem? it seems to be related to it trying to bind and listen to the set ip address and port. keeping the host variable default 0.0.0.0 it will work once, then it will take to long to process the prowlarr request (at least for me) and error and supposedly kill the instance of "webdriver" but hen any further retries of loading the chromedriver executable will fail being unable to connect @ 127.0.0.1:. changing the host ip address (i.e from 0.0.0.0 to the internal docker one for example so 172.20.0.10) would once again allow it to boost and pass the initial test only to once again fail the prowlarr ping and then be unable to start the chromedriver afterwards. however going back and forth between to ip address' seem to work. at this point im gonna look into seeing if a persistent chrome instance would help in any way (i think i remember seeing somewhere that it was possible) edit: i was doing some more testing and i tried without the lang and timezone variable and hit this error: which to me seems to prove the problem ( might be wrong tho) |
|
somewhat of a hollow victory at this point considering the current semi broken state of flaresolverr but I managed to fix the issue (at least for me) throughout multiple deletes and redownloads of flaresolverr it always said that the first layer (f7b75fe1f735) already existed. then yesterday i was having another look at trying to remove specific layers to make it redownload it. when I did a prune yesterday it decided to delete the images of some containers that were in use (the important one being pi-hole), when i went through and redownloaded the images it deleted I noticed that pi-hole was using the layer mentioned earlier due to it being downloaded during the pi-hole re-install. since then I haven't had the problem (now i just need to get one of the 3 current options to work) TL:DR |
I guess that the following code in utils.py might be causing the browser to fail to start. It's possible that the program is attempting to download the browser driver, but since the proxy is not enabled, the URL requested by patcher.executable_path cannot be accessed: if driver_exe_path is None:
PATCHED_DRIVER_PATH = os.path.join(driver.patcher.data_path, driver.patcher.exe_name)
if PATCHED_DRIVER_PATH != driver.patcher.executable_path:
shutil.copy(driver.patcher.executable_path, PATCHED_DRIVER_PATH) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you checked our README?
Have you followed our Troubleshooting?
Is there already an issue for your problem?
Have you checked the discussions?
Environment
Description
Since I am in China, I may not be able to access most websites from other countries.When I don't turn on the system proxy, launching the flaresolverr service results in the error below, and it does not pass the test.
When I use Clash to turn on the system proxy , running flaresolverr can pass the test, after which I shut down the system proxy and flaresolverr can function normally.I have already set the environment variable TEST_URL to a URL that our country can access, but it is still ineffective, TEST_URL=https://www.baidu.com/. I used the following batch script:
@echo off
set LOG_LEVEL=debug
set LANG=en_GB
set HEADLESS=true
set TEST_URL=https://www.baidu.com
python src/flaresolverr.py
no system proxy.Flaresolverr encounters an error:
Enable the system proxy using Clash.Then flaresolverr can run:
As I'm located in China, I might face difficulties accessing a majority of websites from other nations.Upon not activating the system proxy, I encounter an error when initiating the flaresolverr service, preventing it from passing the tests.However, once I activate the system proxy using Clash, flaresolverr seems to successfully pass the tests. Subsequently, on disabling the system proxy, flaresolverr continues to operate as expected.I have already set the environment variable TEST_URL to a URL that our country can access, but it is still ineffective, TEST_URL=https://www.baidu.com/.
Logged Error Messages
Screenshots
The text was updated successfully, but these errors were encountered: