Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to interact with chrome after the latest chrome update (111.0.5563.64) #2192

Closed
waleed21155 opened this issue Mar 8, 2023 · 6 comments · Fixed by #2194
Closed
Assignees
Labels
dependencies Pull requests that update a dependency file not a bug
Milestone

Comments

@waleed21155
Copy link

waleed21155 commented Mar 8, 2023

Not able to interact with chrome after the latest chrome update (111.0.5563.64)

Logs:

[TestNG-test=Web test-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 111.0.5563.64 (resolved driver for Chrome 111)
[TestNG-test=Web test-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as /Users/waleedather/.cache/selenium/chromedriver/mac-arm64/111.0.5563.64/chromedriver
Starting ChromeDriver 111.0.5563.64 (c710e93d5b63b7095afe8c2c17df34408078439d-refs/branch-heads/5563@{#995}) on port 31021
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[TestNG-test=Web test-1] INFO com.codeborne.selenide.webdriver.SelenideNettyClientFactory - Changed readTimeout from PT3M to PT1M30S
[TestNG-test=Web test-1] INFO com.codeborne.selenide.webdriver.SelenideNettyClientFactory - Changed readTimeout from PT3M to PT1M30S
Mar 09, 2023 2:27:50 AM 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: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)

[TestNG-test=Web test-1] INFO org.testng.internal.Utils - Failed to invoke configuration method com.packageName.utility.library.BaseTest.setUp:Unable to establish websocket connection to http://localhost:49704/devtools/browser/1dd63e67-177f-4e3a-9dd9-1fbe8f8894ce
@asolntsev asolntsev added bug 🐛 dependencies Pull requests that update a dependency file not a bug and removed bug 🐛 labels Mar 8, 2023
@asolntsev asolntsev self-assigned this Mar 8, 2023
@asolntsev
Copy link
Member

@waleed21155 Seems like a Selenium or Chromedriver bug: SeleniumHQ/selenium#11747

@asolntsev
Copy link
Member

@waleed21155 In Selenide, there is a possible workaround.
Just add this line before opening a browser: System.setProperty("chromeoptions.args", "--remote-allow-origins=*");

@waleed21155
Copy link
Author

@asolntsev It worked, thanks

asolntsev added a commit that referenced this issue Mar 9, 2023
("Invalid Status code=403 text=Forbidden")
asolntsev added a commit that referenced this issue Mar 9, 2023
("Invalid Status code=403 text=Forbidden")
@asolntsev asolntsev linked a pull request Mar 9, 2023 that will close this issue
@asolntsev asolntsev added this to the 6.12.2 milestone Mar 9, 2023
@asolntsev
Copy link
Member

asolntsev commented Mar 9, 2023

@waleed21155 We have added a workaround in Selenide.

Just released Selenide 6.12.2

@svderiagin
Copy link

svderiagin commented Feb 23, 2024

@waleed21155 We have added a workaround in Selenide.

Just released Selenide 6.12.2

Was it resolved in 7.1.0?

Unfortunately it does not work like this
Configuration.browserCapabilities.setCapability("--remote-allow-origins=*", true);
or
Configuration.browserCapabilities.setCapability("chromeoptions.args", "--remote-allow-origins=*");

Only

    ChromeOptions options = new ChromeOptions();
    options.addArguments("--remote-allow-origins=*");
    Configuration.browserCapabilities = options;

@BorisOsipov
Copy link
Member

@svderiagin

Was it resolved in 7.1.0?

yes

Unfortunately it does not work like this
Configuration.browserCapabilities.setCapability("--remote-allow-origins=*", true);
or
Configuration.browserCapabilities.setCapability("chromeoptions.args", "--remote-allow-origins=*");

We have never written or said that this should work ¯_(ツ)_/¯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file not a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants