nginx - Connection reset by peer
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 161
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Network project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe the bug
This documentation: https://www.ory.sh/docs/hydra/self-hosted/deploy-hydra-example does not give the expected result.
Reproducing the bug
Follow this documentation as it is
https://www.ory.sh/docs/hydra/self-hosted/deploy-hydra-example
Relevant log output
2022/10/27 01:24:49 [error] 3017452#3017452: *2732 readv() failed (104: Connection reset by peer) while reading upstream, client: 136.158.83.131, server: sso.sunwatt.io, request: "GET /health?secret=CHANGE-ME-INSECURE-PASSWORD HTTP/1.1", upstream: "http://127.0.0.1:4445/health?secret=CHANGE-ME-INSECURE-PASSWORD", host: "sso.sunwatt.io"
Relevant configuration
serve:
cookies:
same_site_mode: Lax
urls:
self:
issuer: http://127.0.0.1:4444
consent: http://127.0.0.1:3000/consent
login: http://127.0.0.1:3000/login
logout: http://127.0.0.1:3000/logout
secrets:
system:
- youReallyNeedToChangeThis
oidc:
subject_identifiers:
supported_types:
- pairwise
- public
pairwise:
salt: youReallyNeedToChangeThis
dsn: postgres://hydra:Minski1234@127.0.0.1:5432/hydra?sslmode=disable&max_conns=20&max_idle_conns=4
urls:
self:
issuer: https://sso.sunwatt.io
log:
level: debug
format: text
leak_sensitive_values: true
Version
v1.11.10
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
No response
Additional Context
No response
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
Start with the linked deploy-hydra-example documentation and compare its nginx setup with the reported upstream log and supplied Hydra configuration. Confirm the cause of the connection reset, then update the deployment documentation so the documented setup works or clearly explains the required configuration; validate by following the reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, postgresql
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100