D
Да
Size: a a a
2020 August 25
АА
попробуйте и посмотрите в лог
АБ
Кто-нибудь пробовал это решение? Не прокатывает чёт ваще ни в каком виде
JD
На ровном месте прилетает ошибка) код не менялся. Что за чудеса?))
JD
При создании драйвера
MT
Hello guys,
I have some simple selenoid docker-compose setup just to play around before implementing something more further and I have the service which I want to open from firefox (that service is hosted locally on port 7070 on my OSX), but the problem is when for example I open manually new firefox session trough selenoid ui and enter
I have some simple selenoid docker-compose setup just to play around before implementing something more further and I have the service which I want to open from firefox (that service is hosted locally on port 7070 on my OSX), but the problem is when for example I open manually new firefox session trough selenoid ui and enter
localhost:7070 or 127.0.0.1:7070 or {docker_gateway_ip}:7070 I cannot access the service. Any ideas where to look for?MT
Perhaps somebody else have faced with similar problem and have fond good solution?
MT
version: '3.6'
networks:
selenoid:
name: selenoid
services:
selenoid:
networks:
selenoid: null
image: "aerokube/selenoid"
ports:
- "4444:4444"
command: ["-limit", "5", "-container-network", "selenoid"]
volumes:
- "$PWD/:/etc/selenoid/" # assumed current dir contains browsers.json
- "/var/run/docker.sock:/var/run/docker.sock"
selenoid-ui:
networks:
selenoid: null
image: "aerokube/selenoid-ui"
command: -selenoid-uri 'http://selenoid:4444'
ports:
- "8080:8080"
links:
- selenoid
IK
Martins Tararujs
Hello guys,
I have some simple selenoid docker-compose setup just to play around before implementing something more further and I have the service which I want to open from firefox (that service is hosted locally on port 7070 on my OSX), but the problem is when for example I open manually new firefox session trough selenoid ui and enter
I have some simple selenoid docker-compose setup just to play around before implementing something more further and I have the service which I want to open from firefox (that service is hosted locally on port 7070 on my OSX), but the problem is when for example I open manually new firefox session trough selenoid ui and enter
localhost:7070 or 127.0.0.1:7070 or {docker_gateway_ip}:7070 I cannot access the service. Any ideas where to look for?hey,
localhost is Docker container is not the same stuff as localhost outside of containerIK
this is how containers work
IK
however Docker gateway IP should work
IK
under Mac and Windows there are aliases like
docker.for.mac.localhostMT
under Mac and Windows there are aliases like
docker.for.mac.localhostActually I tried this before as got pointed out about such a thing and didn't worked before. Now after like 3rd restart of docker this particular started to work.
MT
Still have prooblems when trying to use gateway ip, though, but at this point it is going to be good for now
DA
Коллеги, здравствуйте!
Очень нужна помощь. С чем может быть связана подобная ошибка?
Пытался сам разобраться, не получается(
Очень нужна помощь. С чем может быть связана подобная ошибка?
01:03:03 [2020-08-24 22:03:03:394] [LittleProxy-0-ProxyToServerWorker-0] INFO ProxyToServerConnection - (HANDSHAKING) [id: 0xabc04f11, L:0.0.0.0/0.0.0.0:23902 ! R:accounts.google.com/216.58.211.109:443]: Connection to upstream server failed
01:03:03 java.nio.channels.ClosedChannelException
01:03:03 at io.netty.handler.ssl.SslHandler.channelInactive(SslHandler.java:1076)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
01:03:03 at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
01:03:03 at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)
01:03:03 at io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:818)
01:03:03 at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
01:03:03 at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
01:03:03 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:497)
01:03:03 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
01:03:03 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
01:03:03 at java.lang.Thread.run(Thread.java:745)Пытался сам разобраться, не получается(
IK
Martins Tararujs
Actually I tried this before as got pointed out about such a thing and didn't worked before. Now after like 3rd restart of docker this particular started to work.
I think gateway should work under Linux, probably in Windows \ Mac it will not work because there Docker is running in VM too
IK
Коллеги, здравствуйте!
Очень нужна помощь. С чем может быть связана подобная ошибка?
Пытался сам разобраться, не получается(
Очень нужна помощь. С чем может быть связана подобная ошибка?
01:03:03 [2020-08-24 22:03:03:394] [LittleProxy-0-ProxyToServerWorker-0] INFO ProxyToServerConnection - (HANDSHAKING) [id: 0xabc04f11, L:0.0.0.0/0.0.0.0:23902 ! R:accounts.google.com/216.58.211.109:443]: Connection to upstream server failed
01:03:03 java.nio.channels.ClosedChannelException
01:03:03 at io.netty.handler.ssl.SslHandler.channelInactive(SslHandler.java:1076)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
01:03:03 at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
01:03:03 at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
01:03:03 at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)
01:03:03 at io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:818)
01:03:03 at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
01:03:03 at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
01:03:03 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:497)
01:03:03 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
01:03:03 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
01:03:03 at java.lang.Thread.run(Thread.java:745)Пытался сам разобраться, не получается(
мне кажется это либо сеть у вас развалилась или фаервольных правил нет для доступа на accounts.google.com
DA
мне кажется это либо сеть у вас развалилась или фаервольных правил нет для доступа на accounts.google.com
Я тоже так подумал. Но при отсутствии каких-либо изменений в настройках фаервола и проблем с сетью - ошибка эта всплывает не регулярно, но весьма часто
IK
Я тоже так подумал. Но при отсутствии каких-либо изменений в настройках фаервола и проблем с сетью - ошибка эта всплывает не регулярно, но весьма часто
DA
Осталось понять, почему внезапно стали закрывать канал…) Проявилось только после перехода на латест селеноид