admin/dyolink
0
0
Fork 0
Code Issues 24 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

resolve failed handshake connection with https://wixur.ir:3000
All checks were successful
Production — tag build, push, deploy / build-and-push (push) Successful in 42s
Details
Production — tag build, push, deploy / deploy (push) Successful in 21s
Details

Browse Source
This commit is contained in:
rameen
2026-08-31 10:04:30 +03:30
parent 50eda34e8e
commit 19364ad5c2
2 changed files with 39 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
infrastructure/DEPLOY.md
View File

@@ -439,6 +439,19 @@ docker volume rm dyolink_postgres_data_prod
Add `"insecure-registries": ["wixur.ir:3000"]` to `/etc/docker/daemon.json` and restart Docker.
### `connection reset by peer` while pulling `:v*` from Gitea
`docker login` succeeded, then `compose pull` failed on a frontend/backend manifest or layer from `wixur.ir:3000`. Auth is fine — the Windows Gitea registry dropped the TCP connection (common right after a large push, or when both images pull in parallel).
Images are already in the registry. Re-run only the **deploy** job, or on the VPS:
```bash
cd /opt/dyolink/infrastructure
./scripts/prod-remote-deploy.sh v1.0.2
```
`prod-remote-deploy.sh` pulls backend then frontend with retries. If every attempt RSTs, check Gitea is up and `insecure-registries` includes `wixur.ir:3000`.
### View logs
```bash