curl: (56) Recv failure: Connection reset by peer - with podman 5.4.2 on debian 13 host #405

New Issue

MrUnknownDE · 2026-04-05T21:09:45+02:00

MrUnknownDE commented

2026-04-05 21:09:45 +02:00

Originally created by @KsmoinO on 8/15/2025

Prerequisites

I have searched the existing Closed AND Open Issues AND Discussions
I have searched and read the documentation

Vaultwarden Support String

Not possible

Vaultwarden Build Version

quay.io/vaultwarden/server:latest

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

N/A

Host/Server Operating System

Linux

Operating System Version

Debian 13.0

Clients

CLI

Client Version

N/A

Steps To Reproduce

/usr/bin/podman run --rm --replace --name vaultwarden -p [::1]:8081:80/tcp -v vaultwarden:/data/ quay.io/vaultwarden/server:latest

/--------------------------------------------------------------------\
|                        Starting Vaultwarden                        |
|                           Version 1.34.3                           |
|--------------------------------------------------------------------|
| This is an *unofficial* Bitwarden implementation, DO NOT use the   |
| official channels to report bugs/features, regardless of client.   |
| Send usage/configuration questions or feature requests to:         |
|   https://github.com/dani-garcia/vaultwarden/discussions or        |
|   https://vaultwarden.discourse.group/                             |
| Report suspected bugs/issues in the software itself at:            |
|   https://github.com/dani-garcia/vaultwarden/issues/new            |
\--------------------------------------------------------------------/

[2025-08-15 18:45:25.736][vaultwarden::auth][INFO] Private key 'data/rsa_key.pem' created correctly
[2025-08-15 18:45:25.793][start][INFO] Rocket has launched from http://0.0.0.0:80

on the host :

curl http://[::1]:8081
curl: (56) Recv failure: Connection reset by peer

No more logs in the container

running nginx insted of vaultwarden works

Expected Result

Access to the wen interface

Actual Result

no access

Logs

None

Screenshots or Videos

No response

Additional Context

I tried it on 2 different computers I also tried 1.34.1 release, same issues

*Originally created by @KsmoinO on 8/15/2025* ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String Not possible ### Vaultwarden Build Version quay.io/vaultwarden/server:latest ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy N/A ### Host/Server Operating System Linux ### Operating System Version Debian 13.0 ### Clients CLI ### Client Version N/A ### Steps To Reproduce ``` /usr/bin/podman run --rm --replace --name vaultwarden -p [::1]:8081:80/tcp -v vaultwarden:/data/ quay.io/vaultwarden/server:latest /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.34.3 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://github.com/dani-garcia/vaultwarden/discussions or | | https://vaultwarden.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [2025-08-15 18:45:25.736][vaultwarden::auth][INFO] Private key 'data/rsa_key.pem' created correctly [2025-08-15 18:45:25.793][start][INFO] Rocket has launched from http://0.0.0.0:80 ``` on the host : ``` curl http://[::1]:8081 curl: (56) Recv failure: Connection reset by peer ``` No more logs in the container running nginx insted of vaultwarden works ### Expected Result Access to the wen interface ### Actual Result no access ### Logs ```text None ``` ### Screenshots or Videos _No response_ ### Additional Context I tried it on 2 different computers I also tried 1.34.1 release, same issues

MrUnknownDE closed this issue

2026-04-05 21:09:45 +02:00

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#405