Ninluc/DatBrowser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Moved from a custom selenium UC standalone to selenium hub with a custom UC node
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

Browse Source
This commit is contained in:
Matthias Guillitte
2025-12-16 12:47:24 +01:00
parent 062f428fbc
commit 2a7330bd08
12 changed files with 142 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
undetectedChromedriver/README.md
View File

@@ -10,4 +10,15 @@ Could not start a new session. Response code 500. Message: session not created:
Go into the `/home/seluser` director in the container and run `rm -rf ~/.config/google-chrome/Singleton*`
If it doesn't work, the log can be found in the set profile folder in the file `chrome_debug.log`
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`
```txt
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.