Elm init results in InternalException (HostCannotConnect "package.elm-lang.org" [Network.Socket.setSockOpt: unsupported operation (Protocol not available)])

Learn
1

Hi all,

Installed elm 0.19.2 (upgraded from 0.19.1), but cannot elm init a new project, resulting in the following error message instead:

InternalException (HostCannotConnect “package.elm-lang.org” [Network.Socket.setSockOpt: unsupported operation (Protocol not available)])

https://package.elm-lang.org/all-packages works fine with all browsers. Host is macOS 10.15.8. Any ideas on how to fix this? Thanks!

2

This may all be obvious but make sure to expand the download for Mac which is compressed, rename it “elm”, move it to /usr/local/bin, and run “chmod a+x /usr/local/bin/elm”. Make sure your elm.json, etc, now references “0.19.2” and that you have /usr/local/bin on your PATH and that you don’t have an old npm version of Elm hanging around, which you can uninstall.

But maybe GitHub is just offline again…

3

Github is in fact having more issues. It’s been down 3 times this week as of right now. Not sure if that’s the cause of the initial issue.

4

Thank you for the comments! I tried elm init with 0.19.2 on a Mac running 11.7.11 and it worked. This was also an upgrade from 0.19.1.

The issue still persists on the macOS 10.15.8 machine though so it seems this is either OS-specific (I guess not that many devs running 10.15 these days) or something specific to this particular machine.

I’m gonna try creating a new user account on the older machine to exclude most environment-specific causes and report back on any findings.