-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
Download script failing due to Squarespace migration - TLS error #1056
Comments
As a workaround, you could install arkade directly from github. For example, in Github actions we're doing this: if ! [ -x "$(command -v curl)" ]; then
sudo apt update && sudo apt install -qy curl
fi
curl https://raw.githubusercontent.com/alexellis/arkade/master/get.sh | sudo sh
echo "PATH=$HOME/.arkade/bin:$PATH" >> $GITHUB_ENV |
Yes unfortunately there is nothing I can do about this. Squarespace won't allow me to edit any records, and say that they won't issue the certificate for up to 72 hours. This migration has been a terrible experience, with no warning. |
@nlamot there is no need to do that with GitHub Actions, there are custom actions for arkade already that download the tool and set it up. https://github.com/alexellis/arkade?tab=readme-ov-file#install-clis-during-ci-with-github-actions The arkade-get action doesn't use the domain to do the installation, but JavaScript and the latest URL: https://github.com/alexellis/arkade-get - uses: alexellis/arkade-get@master
with:
kubectl: latest
faas-cli: 0.14.10
- name: check for faas-cli
run: |
faas-cli version
- name: arkade version
run: arkade version Check out the README.. And for all the folks coming out of the woodwork to complain, please sponsor me for this project if you are using it. It's hard enough to run open source projects already 👍 |
curl -sLS https://get.arkade.dev
fails with "curl: (60) SSL: no alternative certificate subject name matches target host name 'get.arkade.dev'"
I've hosted something manually with Caddy, which is less than ideal. It fixed the issue, however Squarespace can't really expect people migrated to its platform to have 72 hours of downtime to provision a TLS cert, can they? Sponsorships accepted at https://github.com/sponsors/alexellis |
See the following log:
Expected Behaviour
curl -sLS https://get.arkade.dev
succeeds.Current Behaviour
curl -sLS https://get.arkade.dev
fails.The text was updated successfully, but these errors were encountered: