2.0.0 binary release failing with "Error: certificate has expired"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- cli
Research direction
Start by reproducing the failure with the 2.0.0 macOS package using brew install --cask logdna-cli and logdna login, then compare it with node index.js login, which reportedly works from source. Investigate the binary release path and verify that the installed binary can complete login without the certificate error.
Written by the indexing model from the issue text.
Description
As of a few days ago logdna-cli commands started failing with "certificate is expired".
Here's a reproducible example from a fresh install running on macOS Sonoma 14.4.1:
user@host ~ $ rm -f ~/.logdna.conf
user@host ~ $ ls -l ~/Library/Caches/Homebrew/downloads/
total 0
user@host ~ $ brew install --cask logdna-cli
==> Downloading https://github.com/logdna/logdna-cli/releases/download/2.0.0/logdna-cli.pkg
==> Downloading from https://objects.githubusercontent.com/github-production-release-asset-2e65be/55010834/55081e00-9aa8-11ea-89b6-11a05c1b6d27?X-Amz-Algorithm
######################################################################################################################################################## 100.0%
==> Installing Cask logdna-cli
==> Running installer for logdna-cli with sudo; the password may be necessary.
installer: Package name is logdna-cli
installer: Installing at base path /
installer: The install was successful.
🍺 logdna-cli was successfully installed!
user@host ~ $ logdna login
Email: [email protected]
Password: ********************
Error: Error: certificate has expired
Running from source (node index.js login etc) works, the problem seems to be only with the binary release.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logdna/logdna-cli
-
SSO login has brokenOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
logdna/logdna-cli#62 · 2 comments · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
logdna/logdna-cli#59 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
logdna/logdna-cli#57 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
logdna/logdna-cli#55 ·
-
CI enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
logdna/logdna-cli#51 · 2 comments · 2 reactions ·
All issues in logdna/logdna-cli
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
opensearch-project/security-dashboards-plugin#2543 ·
Maintainers usually reply within 1 day
-
[quality] refresh-radar-reports.yml runs on ubuntu-latest while every other job pins ubuntu-24.04Openagent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
godotengine/godot-website#1432 ·
-
Add: Mooz RetroOpenchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day