Originally created by @ViRb3 on GitHub (Aug 20, 2020).
Subject of the issue
When attempting to purge account:
[2020-08-20 01:06:04.025][request][INFO] POST /api/ciphers/purge
When importing 5MB KeePass 2 XML:
[2020-08-20 01:03:36.760][request][INFO] POST /api/ciphers/import
In both cases, after ~1 minute the client returns An unexpected error occured. If importing, only a part of the data has been imported. If purging, it seems to succeed regardless the error. No more log messages are provided via docker logs.
Could this be a timeout issue? The Raspberry Pi 4 is not a powerful machine, and given the size of my operations, it may be taking longer than expected. Is there a way to customize the timeout?
Your environment
Bitwarden_rs version: Version 1.16.3
Install method: Docker
Clients used: Web client (vault)
Reverse proxy and version: nginx 1.17
Version of mysql/postgresql: N/A
Other relevant information:
Ubuntu 20.04, arm64
Originally created by @ViRb3 on GitHub (Aug 20, 2020).
### Subject of the issue
- When attempting to purge account:
```
[2020-08-20 01:06:04.025][request][INFO] POST /api/ciphers/purge
```
- When importing 5MB KeePass 2 XML:
```
[2020-08-20 01:03:36.760][request][INFO] POST /api/ciphers/import
```
In both cases, after ~1 minute the client returns `An unexpected error occured`. If importing, only a part of the data has been imported. If purging, it seems to succeed regardless the error. No more log messages are provided via `docker logs`.
Could this be a timeout issue? The Raspberry Pi 4 is not a powerful machine, and given the size of my operations, it may be taking longer than expected. Is there a way to customize the timeout?
### Your environment
* Bitwarden_rs version: Version 1.16.3
* Install method: Docker
* Clients used: Web client (vault)
* Reverse proxy and version: nginx 1.17
* Version of mysql/postgresql: N/A
* Other relevant information:
Ubuntu 20.04, arm64
The problem was indeed a timeout, but in nginx. To solve it, I had to increase the proxy_read_timeout up from the default 60 seconds:
proxy_read_timeout360;
@ViRb3 commented on GitHub (Aug 20, 2020):
The problem was indeed a timeout, but in nginx. To solve it, I had to increase the [proxy_read_timeout](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout) up from the default 60 seconds:
```nginx
proxy_read_timeout 360;
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ViRb3 on GitHub (Aug 20, 2020).
Subject of the issue
In both cases, after ~1 minute the client returns
An unexpected error occured. If importing, only a part of the data has been imported. If purging, it seems to succeed regardless the error. No more log messages are provided viadocker logs.Could this be a timeout issue? The Raspberry Pi 4 is not a powerful machine, and given the size of my operations, it may be taking longer than expected. Is there a way to customize the timeout?
Your environment
Ubuntu 20.04, arm64
@ViRb3 commented on GitHub (Aug 20, 2020):
The problem was indeed a timeout, but in nginx. To solve it, I had to increase the proxy_read_timeout up from the default 60 seconds: