Getting 502 from Hex.pm, when trying to publish a package

Questions / Help
1

Hi there - I am not having much of success with this, on Slack’s #hex channel - I apologize for reposting, but I hope someone here has some info about the current state of hex.pm? I am trying since yesterday to publish a package, and getting 502s every time I reach the docs publishing part. I can see the package published (at hex.pm), but the docs are throwing 404. This is basically what I see from my end:

...
Publishing package...
[#########################] 100%
Publishing failed

<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>502 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>

If hex.pm is known to work properly at this time, how can I debug this from my end, in case my mix has any gremlins in it?! For brevity, I can mix hex.publish with --dry-run, and can also generate the docs locally, w/o any issues.

My local env:

erlang 22.0.7
elixir 1.9.1-otp-22
nodejs 12.0.6

Any hints appreciated, many thanks!

2

I have the same problem, I run after mix hex.publish docs and the docs were published, the package is listed in my account, but when I tried to use it from anther project I got

** (Mix) No matching version

1 Like
3

I tried mix hex.publish docs, but then see 404, on HexDocs, even tho’ the command ends up successfully(?!) . I wish I knew a way to debug this better :confused:

$ mix hex.publish docs
Docs successfully generated.
View them at "doc/index.html".
[#########################] 100%
Docs published to https://hexdocs.pm/closure_table/0.1.1
4

Could throw the issue up on the Hex github page?

5

@frigidcode - thought I should first try to exhaust the less “protocolar” avenues i.e. Slack, here… , before opening an issue there, they probably have more important issues to focus on :slight_smile: If I’d had a way to make sure I’m not at fault, I would.

6

@Florin and @nadsat - it isn’t anything you are doing wrong. We are currently having a very specific infrastructure issue related to docs. Working on it now.

3 Likes
7

Thank you!

8

Thanks

9

The issue has been resolved for @Florin and also tested by a couple other users.
@nadsat - can you also try it out to make sure?

5 Likes
10

thank you so much, Todd!

11

When I ran into this issue when running mix hex.publish, my package got published but the new version is not available in the registry: https://hex.pm/packages/chrome_remote_interface. Is this related? @supersimple

12

@supersimple it’s working thak you

13

yes - this is related. There was an issue with the registry timing out. You can try to publish again, the problem has (hopefully) been solved.