Ninluc/DatBrowser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5e6164016c8a0868929f5ea84f856fb771c784e0
DatBrowser/undetectedChromedriver/README.md
Matthias Guillitte 2a7330bd08
All checks were successful
Test, build and push image to registry / phpunit-tests (push) Successful in 1m54s
Details
Test, build and push image to registry / build-image (push) Successful in 3m0s
Details
Moved from a custom selenium UC standalone to selenium hub with a custom UC node
2025-12-16 12:47:24 +01:00

1.0 KiB
Raw Blame History

Selenium Undetected Standalone-Chromedriver

Selenium Standalone-Chromedriver with Undected-Chromedriver applied

Bug

Could not start a new session. Response code 500. Message: session not created: probably user data directory is already in use,

Go into the /home/seluser director in the container and run rm -rf ~/.config/google-chrome/Singleton*

One-liner : rm -rf /home/seluser/.config/google-chrome/Singleton* && exit

If it doesn't work, the log can be found in the seluser chrome profile folder in the file chrome_debug.log

Could not start a new session. Response code 500. Message: session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause.

The log can be found in the seluser chrome profile folder in the file chrome_debug.log.

If the log file only says that the chrome profile folder seems to be in use by another chrome application, there is probably a problem with a file in the chrome profile folder like a version change. The best thing to do is to delete the folder.