Skip to content

[Bug]: Unable to obtain latest release due to missing AAAA records #2180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dmarks100 opened this issue Feb 21, 2025 · 0 comments
Open

[Bug]: Unable to obtain latest release due to missing AAAA records #2180

dmarks100 opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@dmarks100
Copy link

Steps to Reproduce

I don't have IPv4 addresses in my environment, so I am unable to pull the latest release:

[ec2-user@i-0c7d50cdd77cb708b ~]$ curl https://dl.smallstep.com/gh-release/cli/gh-release-header/v0.28.1/step-ca-0.28.1-1.aarch64.rpm -O -v
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Host dl.smallstep.com:443 was resolved.
* IPv6: (none)
* IPv4: 54.244.195.224, 34.213.189.139, 52.33.86.107
*   Trying 54.244.195.224:443...
* Immediate connect fail for 54.244.195.224: Network is unreachable
*   Trying 34.213.189.139:443...
* Immediate connect fail for 34.213.189.139: Network is unreachable
*   Trying 52.33.86.107:443...
* Immediate connect fail for 52.33.86.107: Network is unreachable
* Failed to connect to dl.smallstep.com port 443 after 2 ms: Couldn't connect to server
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Closing connection
curl: (7) Failed to connect to dl.smallstep.com port 443 after 2 ms: Couldn't connect to server
[ec2-user@i-0c7d50cdd77cb708b ~]$

Your Environment

  • OS - Amazon Linux 2023
  • step-ca Version - v0.28.1

Expected Behavior

I wanted to be able to pull the release directly on the machine, but I have to download it on another machine and rsync it to the intended server.

Actual Behavior

Unable to download releases without obtaining an IPv4 address ($$$)

Additional Context

This used to work months ago (this was part of a script that stopped working), I don't know exactly when this regression happened, sorry I couldn't provide more context here...

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@dmarks100 dmarks100 added bug needs triage Waiting for discussion / prioritization by team labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants