ChromeDriver 111.0.5563.19 unable to establish connection to chrome

34,243 views
Skip to first unread message

xinchao zhang

unread,
Feb 14, 2023, 5:39:23 AM2/14/23
to ChromeDriver Users
Hi,

Our selenium tests against Chrome Beta all started to fail a few days ago since Chrome 111 moved into beta. All the tests throw exception when initializing the ChromiumDriver (version 111.0.5563.19):

Feb 14, 2023 6:22:46 PM org.openqa.selenium.remote.http.WebSocket$Listener onError
WARNING: Invalid Status code=403 text=Forbidden
java.io.IOException: Invalid Status code=403 text=Forbidden
    at org.asynchttpclient.netty.handler.WebSocketHandler.abort(WebSocketHandler.java:92)
    at org.asynchttpclient.netty.handler.WebSocketHandler.handleRead(WebSocketHandler.java:118)
Invalid Status code=403 text=Forbidden

    at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
    at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346)
    at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:333)
    at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:454)
    at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290)
    at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
    at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.base/java.lang.Thread.run(Thread.java:833)

Exception in thread "main" org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:55989/devtools/browser/d9f96e05-4316-4f7c-b431-8b5586d81a28
Build info: version: '4.8.0', revision: '267030adea'
System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '13.1', java.version: '17.0.3'
Driver info: driver.version: ChromeDriver
    at org.openqa.selenium.remote.http.netty.NettyWebSocket.<init>(NettyWebSocket.java:102)
    at org.openqa.selenium.remote.http.netty.NettyWebSocket.lambda$create$3(NettyWebSocket.java:128)
    at org.openqa.selenium.remote.http.netty.NettyClient.openSocket(NettyClient.java:107)
    at org.openqa.selenium.devtools.Connection.<init>(Connection.java:78)
    at org.openqa.selenium.chromium.ChromiumDriver.lambda$new$2(ChromiumDriver.java:116)
    at java.base/java.util.Optional.map(Optional.java:260)
    at org.openqa.selenium.chromium.ChromiumDriver.<init>(ChromiumDriver.java:114)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:82)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:71)


It is the same even with a minimal setup:

System.setProperty("webdriver.chrome.driver","/Users/xinchao/.cache/selenium/chromedriver/mac-arm64/111.0.5563.19/chromedriver");
ChromeOptions ops = new ChromeOptions();
ops.setBinary("/Applications/Google Chrome Beta.app/Contents/MacOS/Google Chrome Beta");
WebDriver driver = new ChromeDriver(ops);
driver.get("https://www.google.com");

Not sure if it is an issue with the driver or an issue with selenium. Any help will be very much appreciated!

xinchao zhang

unread,
Feb 14, 2023, 6:09:53 AM2/14/23
to ChromeDriver Users
Actually, I have it figured out after enabling verbose logging of chromedriver:

[32332:259:0214/190812.204658:ERROR:devtools_http_handler.cc(766)] Rejected an incoming WebSocket connection from the http://localhost:58642 origin. Use the command line flag --remote-allow-origins=http://localhost:58642 to allow connections from this origin or --remote-allow-origins=* to allow all origins.

So I added the --remote-allow-origin=* to the ChromeOptions and I can successfully connect:

ChromeOptions ops = new ChromeOptions();
ops.addArguments("--remote-allow-origins=*");

Mark Owen

unread,
Mar 7, 2023, 5:48:05 PM3/7/23
to ChromeDriver Users
I'm seeing this as well with 111.0.5563.19 when running tests on my machine on apps using Selenium 4.1.4.  It spins up browser windows but no content loads.
 This does not happen with an app using Selenium 3.14159.

John Castberg

unread,
Mar 7, 2023, 7:04:42 PM3/7/23
to ChromeDriver Users
Chromedriver: 110.0.5481.77
Selenium: 4.3.0

adding the --remote-allow-origins=* got windows to start popping up, but i still got the same exception

java.io.IOException: Invalid Status code=403 text=Forbidden

Could not instantiate class net.thucydides.core.webdriver.ProvidedDriver
net.thucydides.core.webdriver.DriverConfigurationError: Could not instantiate class net.thucydides.core.webdriver.ProvidedDriver

Caused by: org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:50730/devtools/browser/0050b064-7c41-4ac6-a0f3-357a5acecf68
Build info: version: '4.3.0', revision: 'a4995e2c09*'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '13.2.1', java.version: '17.0.5'

John Castberg

unread,
Mar 7, 2023, 7:38:51 PM3/7/23
to ChromeDriver Users
temporary fix here is to use firefox driver instead, working as expected

James Lawry

unread,
Mar 7, 2023, 8:32:13 PM3/7/23
to ChromeDriver Users
We are getting the same error.  Started today a couple hours ago after 111 released both locally and in our gitlab runners.

org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:50519/devtools/browser/d39d5d78-a788-495e-b43a-5c945d974ce9
Build info: version: '4.4.0', revision: 'e5c75ed026a'
System info: host: 'sdg-mac334.local', ip: '2601:681:8004:57a0:0:0:0:5bfc%en0', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '12.1', java.version: '17.0.4.1'

Here are the Selenium dependencies:

<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>4.4.0</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-devtools-v108</artifactId>
<version>4.7.2</version>
</dependency>

Dolph Lei

unread,
Mar 8, 2023, 1:21:28 AM3/8/23
to ChromeDriver Users
I got the same error, when the V111 is released. I've applied to the chromeDriver  v 111.0.5563.41.
No matter it's executed in headless or not, and for both windows/linux, the error the same.
And I even tried the --remote-allow-origins=*, 
the error still the same.

 [AsyncHttpClient-1-4] o.o.s.r.h.WebSocket$Listener: Invalid Status code=403 text=Forbidden

java.io.IOException: Invalid Status code=403 text=Forbidden

And cause the Google doesn't provide previous V110 download, may system is down there,
what a nightmare.



James Lawry 在 2023年3月8日 星期三上午9:32:13 [UTC+8] 的信中寫道:

sharanaprasad Mailar

unread,
Mar 8, 2023, 3:37:46 AM3/8/23
to ChromeDriver Users
Even I am getting same error with Chrome version  Version 111.0.5563.65 and Chrome driver version  ChromeDriver 111.0.5563.64

org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:49183/devtools/browser/5e8d2420-a9be-4d67-9ae9-6511ba5c7786

Build info: version: '4.8.0', revision: '267030adea'
System info: os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_331'

Driver info: driver.version: ChromeDriver
        at org.openqa.selenium.remote.http.netty.NettyWebSocket.<init>(NettyWebSocket.java:102)
        at org.openqa.selenium.remote.http.netty.NettyWebSocket.lambda$create$3(NettyWebSocket.java:128)
        at org.openqa.selenium.remote.http.netty.NettyClient.openSocket(NettyClient.java:107)
        at org.openqa.selenium.devtools.Connection.<init>(Connection.java:78)
        at org.openqa.selenium.chromium.ChromiumDriver.lambda$new$2(ChromiumDriver.java:116)
        at java.util.Optional.map(Optional.java:215)

        at org.openqa.selenium.chromium.ChromiumDriver.<init>(ChromiumDriver.java:114)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:82)
        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:71)
        at Genericlibrary.Base.launchApp(Base.java:146)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)
        at org.testng.internal.MethodInvocationHelper.invokeMethodConsideringTimeout(MethodInvocationHelper.java:59)
        at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:458)
        at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:222)
        at org.testng.internal.Invoker.invokeMethod(Invoker.java:523)
        at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719)
        at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989)
        at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
        at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)



Ciddagoni Ravi

unread,
Mar 8, 2023, 3:41:29 AM3/8/23
to ChromeDriver Users
Even I got the same error using chrome V111 is released. 
but the workaround is reverting chrome-driver to the previous version 
WebDriverManager.chromedriver().driverVersion("110.0.5481").setup();
it's working for me.  pls, try it.

Just Like That !!

unread,
Mar 8, 2023, 3:50:38 AM3/8/23
to ChromeDriver Users
I was facing this issue from today morning, but after this it worked for me 


//WebDriverManager.chromedriver().browserVersion("111.0.5563.64").setup();

WebDriverManager.chromedriver().setup();

ChromeOptions options = new ChromeOptions();

//options.addArguments("--headless");

options.addArguments("--disable-notifications");

options.addArguments("--disable-gpu");

options.addArguments("--disable-extensions");

options.addArguments("--no-sandbox");

options.addArguments("--disable-dev-shm-usage");

options.addArguments("--remote-allow-origins=*");  // this i added  this and it worked, Thanks a ton  xinchao zhang !! 

DesiredCapabilities capabilities = new DesiredCapabilities();

capabilities.setCapability(ChromeOptions.CAPABILITY, options);

options.merge(capabilities);

wd = new ChromeDriver(options);

wd.manage().window().maximize();

wd.manage().timeouts().pageLoadTimeout(Duration.ofSeconds(20));

wd.manage().timeouts().implicitlyWait(Duration.ofSeconds(20));



Sivaramakrishnan Selvakumar

unread,
Mar 8, 2023, 4:10:42 AM3/8/23
to ChromeDriver Users
Thanks xinchao zhang!
options.addArguments("--remote-allow-origins=*"); 
it's resolved my issue.

Dolph Lei

unread,
Mar 8, 2023, 4:24:32 AM3/8/23
to ChromeDriver Users
Yes,
options.addArguments("--remote-allow-origins=*"); 
did the trick!!

There's a typo on my previous revision.

Thank you all !!

Sivaramakrishnan Selvakumar 在 2023年3月8日 星期三下午5:10:42 [UTC+8] 的信中寫道:

sharanaprasad Mailar

unread,
Mar 8, 2023, 4:32:43 AM3/8/23
to ChromeDriver Users
Thanks a lot @ Just Like That !!,  xinchao zhang!

options.addArguments("--remote-allow-origins=*");  

is working !!!  .

usama sohail

unread,
Mar 8, 2023, 5:07:22 AM3/8/23
to ChromeDriver Users
@ sharanaprasad Mailar

options.addArguments("--remote-allow-origins=*");  

is working !!!  . 

Not working for me please help 


tarting ChromeDriver 111.0.5563.41 (976ef12907ef9b413c2d929c043307b415d27b9e-refs/branch-heads/5563@{#737}) on port 64403
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
Mar 08, 2023 3:05:28 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected upstream dialect: W3C
Mar 08, 2023 3:05:28 PM org.openqa.selenium.remote.http.WebSocket$Listener onError

WARNING: Invalid Status code=403 text=Forbidden
java.io.IOException: Invalid Status code=403 text=Forbidden
at org.asynchttpclient.netty.handler.WebSocketHandler.abort(WebSocketHandler.java:92)
at org.asynchttpclient.netty.handler.WebSocketHandler.handleRead(WebSocketHandler.java:118)
at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:327)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:314)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:435)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:279)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerCo

David Goodridge

unread,
Mar 8, 2023, 5:18:13 AM3/8/23
to ChromeDriver Users
Thanks, chromeOptions.addArguments("--remote-allow-origins=*"); does workaround the issue.

Could this be the change that introduced this behaviour? https://github.com/chromium/chromium/commit/0154caeefc74530d5cb57ce71608beb1b77bca39
PR description states "This CL should not affect non-browser clients such as Puppeteer and WebDriver" so I guess its a bug.

Milica Popovic

unread,
Mar 8, 2023, 5:57:04 AM3/8/23
to ChromeDriver Users
Thanks xinchao zhang ,  options.addArguments("--remote-allow-origins=*"); workaround also worked out for me!

Raider ALH

unread,
Mar 8, 2023, 6:33:21 AM3/8/23
to ChromeDriver Users
Thank you  xinchao zhang, it works for me with  "--remote-allow-origins=*"

Jitendra Reddy TS

unread,
Mar 8, 2023, 6:36:12 AM3/8/23
to ChromeDriver Users
This is not working when I'm trying to execute my script through debugger mode. 

String cmdCommand = "chrome.exe -remote-debugging-port=2708 --no-first-run --no-default-browser-check --user-data-dir=C:\\Users\\user1\\OneDrive\\Documents\\Chromedata";
String chromePath = "C:\\Program Files\\Google\\Chrome\\Application";
Runtime.getRuntime().exec("cmd /c start cmd.exe /K " + cmdCommand, null, new File(chromePath));
Thread.sleep(500);
Runtime.getRuntime().exec("taskkill /f /im cmd.exe");
WebDriverManager.chromedriver().setup();
ChromeOptions opt = new ChromeOptions();
opt.setExperimentalOption("debuggerAddress", "localhost:2708");
opt.addArguments("--disable notifications");
opt.addArguments("--remote-allow-origins=http://localhost:2708");

Any help with this?

Message has been deleted

jayachandran ramachandran

unread,
Mar 8, 2023, 10:27:47 AM3/8/23
to ChromeDriver Users
help me with this issue////
options.addArguments("--remote-allow-origins=*"); 
how and where to add this

John Guin

unread,
Mar 8, 2023, 10:52:33 AM3/8/23
to ChromeDriver Users
Jayachandran,

Without seeing your code, we won't be able to tell you where to add it.

In my codebase, I looked for the class where we were creating the WebDriver.  In my case, this named Browser.java.  We were already setting some arguments there using  the .addArguments() method on a ChromeOptions class and I added this command there.

So you could search your codebase for a few things.
1. Where you are creating a WebDriver object
2. Where you are already adding arguments to a ChromeOptions object

If #2 does not exist, you can set this up right before you create the WebDriver.  Again, for my codebase we do this with a call to new RemoteWebDriver(url, options) so you may want to see if you are calling that method.  That method is in the RemoteWebDriver class from Selenium, so you might want to look for usages of that class as well.

Ideally, you could also invoke and debug a unit test to validate behavior for your implementation here, but no such unit test may exist.

In any case, good luck!

James Lawry

unread,
Mar 8, 2023, 10:53:11 AM3/8/23
to ChromeDriver Users
Confirmed, the above does work.

you need to add it like this:

ChromeOptions chromeOptions = new ChromeOptions();

so here you declare a new ChromeOptions instance.

chromeOptions.addArguments("--remote-allow-origins=*");

then you add the argument like that ^^^

Titus Fortner

unread,
Mar 8, 2023, 11:28:01 AM3/8/23
to ChromeDriver Users
If people are using Java 11+ can you try using the new http client and see if that fixes the issue without needing to update the options?

Антон Страшевський

unread,
Mar 8, 2023, 11:52:03 AM3/8/23
to ChromeDriver Users
The Java 11+  variant with new http client worked for me with Selenium 4.5.0. Thank you Titus!

середа, 8 березня 2023 р. о 18:28:01 UTC+2 Titus Fortner пише:

James Lawry

unread,
Mar 8, 2023, 11:52:36 AM3/8/23
to ChromeDriver Users
https://bugs.chromium.org/p/chromium/issues/detail?id=1422444

I submitted this bug yesterday and got responses this morning.  Sounds like it was intentional and will need to file a bug with Selenium to stop setting the origin header.

James Lawry

unread,
Mar 8, 2023, 12:00:27 PM3/8/23
to ChromeDriver Users
https://github.com/SeleniumHQ/selenium/issues/11750

Here is the bug I submitted with Selenium.

Nicole Horner

unread,
Mar 8, 2023, 12:43:46 PM3/8/23
to ChromeDriver Users
This fixed it for me too, thanks!

Titus Fortner

unread,
Mar 8, 2023, 12:55:18 PM3/8/23
to ChromeDriver Users
TL;DR

1. If you are Java 11+ please use the new HTTP Client
2. Selenium will add this parameter to the Chrome service class by default for Java < 11 users (we already do this for Firefox); It will be in Selenium 4.9
3. If you can't update to Selenium 4.9 (when we release it) and can't upgrade to Java 11, you'll need to use: chromeOptions.addArguments("--remote-allow-origins=*")

Mohammad asghar Meo

unread,
Mar 8, 2023, 1:27:38 PM3/8/23
to ChromeDriver Users
Thank you it worked

Phaneesh Kashyap

unread,
Mar 8, 2023, 2:13:02 PM3/8/23
to ChromeDriver Users
version 111.0.5563.65

Works fine!!! 
when you add dependency

<dependency>

<groupId>org.seleniumhq.selenium</groupId>

<artifactId>selenium-http-jdk-client</artifactId>

<version>4.5.0</version>

</dependency>


and add 

System.setProperty("webdriver.http.factory", "jdk-http-client");


Haonan Zhu

unread,
Mar 8, 2023, 6:59:22 PM3/8/23
to ChromeDriver Users
Use playwright to run npx playwright install to install chrome does not work.
Error message:
$ npx playwright install Downloading Chromium 111.0.5563.19 (playwright build v1048) from https://playwright.azureedge.net/builds/chromium/1048/chromium-linux.zip | | 0% of 143.7 Mb Failed to install browsers Error: Failed to download Chromium 111.0.5563.19 (playwright build v1048), caused by Error: end of central directory record signature not found at /home/vsts/work/1/s/Cloud-RPA/playwright-testing/node_modules/playwright-core/lib/zipBundleImpl.js:1:24033 at /home/vsts/work/1/s/Cloud-RPA/playwright-testing/node_modules/playwright-core/lib/zipBundleImpl.js:1:31712 at /home/vsts/work/1/s/Cloud-RPA/playwright-testing/node_modules/playwright-core/lib/zipBundleImpl.js:1:17288 at FSReqCallback.wrapper [as oncomplete] (node:fs:671:5) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. yarn run v1.22.19

Should I file a bug to yarn? 

Praveen Christopher Joseph

unread,
Mar 8, 2023, 8:21:54 PM3/8/23
to ChromeDriver Users
Hi All,

I have added the below line but it does not work out to my problem.

System.setProperty("webdriver.chrome.driver", "C:\\Praveen\\SeleniumTesting\\chromedriver_win32\\chromedriver.exe");

WebDriver driver = new ChromeDriver();

ChromeOptions ops = new ChromeOptions();
ops.addArguments("--remote-allow-origins=*");

driver.quit();

Invalid Status code=403 text=Forbidden
java.io.IOException: Invalid Status code=403 text=Forbidden


Exception in thread "main" org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:51723/devtools/browser/3ad2985f-1c9e-475b-8dbe-81071c677ec4

Kindly help me to resolve this issue.

On Wednesday, March 8, 2023 at 12:04:42 AM UTC John Castberg wrote:
Chromedriver: 110.0.5481.77
Selenium: 4.3.0

adding the --remote-allow-origins=* got windows to start popping up, but i still got the same exception

java.io.IOException: Invalid Status code=403 text=Forbidden

Could not instantiate class net.thucydides.core.webdriver.ProvidedDriver
net.thucydides.core.webdriver.DriverConfigurationError: Could not instantiate class net.thucydides.core.webdriver.ProvidedDriver

Caused by: org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:50730/devtools/browser/0050b064-7c41-4ac6-a0f3-357a5acecf68
Build info: version: '4.3.0', revision: 'a4995e2c09*'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '13.2.1', java.version: '17.0.5'
On Tuesday, March 7, 2023 at 2:48:05 PM UTC-8 Mark Owen wrote:
I'm seeing this as well with 111.0.5563.19 when running tests on my machine on apps using Selenium 4.1.4.  It spins up browser windows but no content loads.
 This does not happen with an app using Selenium 3.14159.


Bojana Radonjic

unread,
Mar 9, 2023, 5:01:57 AM3/9/23
to ChromeDriver Users
For me this not working, I have sesion error and message this is not permitted

Randall Wessel

unread,
Mar 9, 2023, 5:07:26 AM3/9/23
to ChromeDriver Users
For the FitNesse users, I got my test working again by adding a simple profile:

|script         |map fixture                       |
|set value      |remote-allow-origins=*|for|args[0]|
|$chromeProfile=|copy map                          |

|script          |selenium driver setup             |
|start driver for|chrome|with profile|$chromeProfile|



Op donderdag 9 maart 2023 om 11:01:57 UTC+1 schreef Bojana Radonjic:

Videomaster724

unread,
Mar 9, 2023, 6:19:45 AM3/9/23
to ChromeDriver Users
this works pretty well, thanks

Sugandha K.A.D.P

unread,
Mar 9, 2023, 7:00:45 AM3/9/23
to ChromeDriver Users
Thanks Just Like That !! ,  xinchao zhang . This was working for me.
 [AsyncHttpClient-1-4] o.o.s.r.h.WebSocket$Listener: Invalid Status code=403 text=Forbidden

java.io.IOException: Invalid Status code=403 text=Forbidden

And cause the Google doesn't provide previous V110 download, may system is down there,
what a nightmare.



James Lawry 在 2023年3月8日 星期三上午9:32:13 [UTC+8] 的信中寫道:
We are getting the same error.  Started today a couple hours ago after 111 released both locally and in our gitlab runners.

org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://localhost:50519/devtools/browser/d39d5d78-a788-495e-b43a-5c945d974ce9
Build info: version: '4.4.0', revision: 'e5c75ed026a'
System info: host: 'sdg-mac334.local', ip: '2601:681:8004:57a0:0:0:0:5bfc%en0', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '12.1', java.version: '17.0.4.1'

Here are the Selenium dependencies:

<dependency>
<groupId>org.seleniumhq.selenium</groupId>

<artifactId>selenium-java</artifactId>
<version>4.4.0</version>
</dependency>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>

<artifactId>selenium-devtools-v108</artifactId>
<version>4.7.2</version>
</dependency>
On Tuesday, March 7, 2023 at 5:38:51 PM UTC-7 John Castberg wrote:
temporary fix here is to use firefox driver instead, working as expected

On Tuesday, March 7, 2023 at 4:04:42 PM UTC-8 John Castberg wrote:
Chromedriver: 110.0.5481.77
Selenium: 4.3.0

adding the --remote-allow-origins=* got windows to start popping up, but i still got the same exception

java.io.IOException: Invalid Status code=403 text=Forbidden

Could not instantiate class net.thucydides.core.webdriver.ProvidedDriver
net.thucydides.core.webdriver.DriverConfigurationError: Could not instantiate class net.thucydides.core.webdriver.ProvidedDriver

Caused by: org.openqa.selenium.remote.http.ConnectionFa