Shopify / Shopify/shopify-api-ruby
SSL_connect, SSL_read, TCP connection errors
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.1k
- Forks
- 484
- PR merge metrics
- No merged PRs in 30d
Description
Issue summary
Before opening this issue, I have:
- [ x] Upgraded to the latest version of the package
shopify_apiversion: 16.1.0- Ruby version: 3.3.6
- Operating system:
- [x ] Set
log_level: :debugin my configuration, if applicable - [ x] Found a reliable way to reproduce the problem that indicates it's a problem with the package
- [x ] Looked for similar issues in this repository
- [x ] Checked that this isn't an issue with a Shopify API
- If it is, please create a post in the Shopify community forums or report it to Shopify Partner Support
We are constantly getting SSL_connect, SSL_read, and TCP connection errors. For example, we had 40,000+ errors in last 2 weeks. Shopify support is pointing us to shopify_api as the culprit. Is anyone else having similar issues?
See example errors below:
SSL_connect returned=1 errno=0 peeraddr=xx.xx.xx.xx:443 state=error: unexpected eof while reading
SSL_read: unexpected eof while reading
SSL_connect returned=1 errno=107 peeraddr=(null) state=error: unexpected eof while reading
Failed to open TCP connection to xxxxx.myshopify.com:443 (execution expired)
Expected behavior
Not have similar errors.
Actual behavior
What actually happens?
Steps to reproduce the problem
Debug logs
// Paste any relevant logs here
Contributor guide
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.
Research direction
The report provides SSL_connect, SSL_read, and TCP connection error examples but names no files, tests, or request entry points. Start by reproducing the reported failures with shopify_api 16.1.0 on Ruby 3.3.6 and tracing where these connection errors are surfaced; done should identify a package-specific cause and include a verified fix or a clearly documented reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100