Remote deploy times out on steps that rely on hex.pm

Questions / Help
1

Hiya,

I’m trying to deploy a fairly straightforward Phoenix app, no tricks or anything, just following the tutorial on Phoenix’s (1.6.0-rc0) side.

When I deploy remotely (which I have to due to my M1 Mac), the builder seems to arbitrarily time out on either:

  • mix local.rebar --force (citing Could not install Rebar because Mix could not download metadata at https://repo.hex.pm/installs/rebar-1.x.csv.signed.)
  • mix deps.get --only $MIX_ENV. It complains about Failed to fetch record for 'hexpm/cowboy_telemetry' from registry (using cache instead). Of course, cowboy_telemetry exists on Hex.

I’m wondering if this is an availability problem on Hex’s side? Their status seems all green, and running the steps locally works fine as well. Did I mess up my networking config somehow, or is this a known problem?

2

That’s interesting. If you’re getting errors from those commands in the builder, it’s either a network issue between the builder and hex, or an actual hex problem. I think most Hex stuff is on S3 so it might just be a regional S3 problem.

How long has this been happening?

3

For a couple hours - though I remember when I tried to deploy something a week or so ago, I was also having issues with mix local.rebar on my remote builder.

4

Hrm, just ran deploy again and it worked for those steps. Maybe it’s just an AWS blip then?

5

What is weird, though, is that my builder is on fra, so it’s assumedly talking to the same AWS region that I am (being in Berlin). Locally, on my machine, it works consistently, but on the remote builder it seems less consistent.

6

I just moved your builder to Amsterdam, will you give that a try and see if it helps?

7

Yep, that seems to be fine for now.

8

Well that’s super weird. S3 is a pain.

1 Like