SSL errors on download
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 485
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I automatically install opm libraries when deploying OpenResty. This has a tendency to fail due to SSL errors from the upstream when performing this on AWS instances in the Sao Paolo region (sa-east-1). The other regions work fine.
docker run --rm --entrypoint=/usr/local/openresty/bin/opm --name lua-installation -v /usr/local/openresty/site/lualib/:/usr/local/openresty/site/lualib/ openresty/openresty:1.13.6.2-2-alpine-fat get pintsized/lua-resty-http
[10:31:32] stderr: |-
[10:31:32] * Fetching knyar/nginx-lua-prometheus
[10:31:32] curl: (35) error:14004438:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert internal error
[10:31:32] ERROR: failed to run command "curl -sS -i -A 'opm 0.0.5 (x86_64-linux-thread-multi, perl v5.26.2)' 'https://opm.openresty.org/api/pkg/fetch?account=knyar&;name=nginx-lua-prometheus&op=&version='"
From my local machine it works fine and uses servers in DigitalOcean Singapore.
$ dig +short opm.openresty.org
v2.openresty.com.
188.166.239.230
From my Sao Paolo instances it fails and uses DigitalOcean US servers.
11:01:30 ~ ip-10-102-134-106 % dig +short opm.openresty.org
v2.openresty.com.
174.138.55.201
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the documented docker run command and compare DNS resolution and download behavior between the working and failing regions. Inspect the opm package-fetch entry point and its TLS or upstream request handling, using the reported curl error as the starting symptom. Done means package downloads work reliably from the Sao Paulo AWS region or the failure is clearly diagnosed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100