Fix scp SFTP subsystem error with -O flag
- Add -O flag to force legacy SCP protocol instead of SFTP - Bypasses 'subsystem request failed on channel 0' error - Works with Synology NAS without SFTP subsystem configuration - Prevents Exit code 255 from connection failures 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
83d6303477
commit
3e3f0ae0ef
2
.github/workflows/deploy.yml
vendored
2
.github/workflows/deploy.yml
vendored
@ -62,7 +62,7 @@ jobs:
|
||||
tar czf /tmp/deploy-build/deploy.tar.gz --exclude='.git' --exclude='*.tar.gz' --warning=no-file-changed .
|
||||
|
||||
- name: Copy archive to NAS
|
||||
run: scp -o ConnectTimeout=10 -o ServerAliveInterval=60 -P ${{ secrets.NAS_PORT }} /tmp/deploy-build/deploy.tar.gz admin@${{ secrets.NAS_HOST }}:/tmp/
|
||||
run: scp -O -o ConnectTimeout=10 -o ServerAliveInterval=60 -P ${{ secrets.NAS_PORT }} /tmp/deploy-build/deploy.tar.gz admin@${{ secrets.NAS_HOST }}:/tmp/
|
||||
|
||||
- name: Deploy with atomic swap
|
||||
run: |
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user