Riccardo Trivellato

I saw the same problem starting yesterday and I'm using https://hub.docker.com/r/ultrafunk/undetected-chromedriver, but from docker hub I see no changes in the dockerfile in 15 days. This problem raise up only...

I tried to run into CloudRun and I have this issue. I run it on Heroku for 1 week and everything was good until today

I think the same problem happens with Sickchill. When you try to reach it, it returns 404 meanwhile accessing through tunnel show the dashboard

This feature will be useful for certain libraries that require .so files

@asimptot @phl0yd @Anticope12 this solution is not working in a docker file unfortunately

Same as the title `Message: unknown error: cannot connect to chrome at 127.0.0.1:50276`. My dockerfile is [here](https://github.com/rtrive/f1-telegram-fantasy-bot/blob/fix/docker-not-working/Dockerfile) and the Chrome options are [there](https://github.com/rtrive/f1-telegram-fantasy-bot/blob/6bb7fa08701bd3211fc102d5f4a3046d9c88182d/src/main.py#L49)

Very interesting feature! Is there a reason why it was not merged?

I have the same issue with airvpn. But how can i do this without OPNVPN_CONFIG env?