websocket_debugger_url failing on windows erlang26/elixir15.7 about chromic_pdf

[maltoe]

Hi @joshamb

first of all, thank you for the detailed issue description!

econnrefused sounds like either the TestInitChrome failed to launch or bind to port :29224, or the ChromicPDF.Connection process inside the test fails to connect to that port due to firewall issues. I'm leaning towards the latter. You could try to manually start a chrome process like this with the ChromeRunner on console, and see if the port is open (netstat or whatever is available on Windows). Or follow the docs on "remote" Chrome instance and find out if ChromicPDF can talk to a Chrome inside a docker container.

Is this an actual bug for you? i.e. are you trying to use a remote chrome in your app?

and could it be erlang 26 related potentially?

Anything could be related to Erlang/OTP 26, it broke sooo much 😃 Though in this case, I am more suspicious of Windows than anything else. My uneducated guess would be that you are in fact the first person to try ChromicPDF on Windows.

[maltoe]

Hey @joshamb

I'm going to close this for now. Feel free to reopen if it turns out to be related to ChromicPDF.