Similar issue as in #137: "Server sent FIN packet unexpectedly"
See original GitHub issueBug Description Just like in #137 I’m not able to deploy to the FTP server however, I’m confident my hosting provider provides FTP (port 21) and an SFTP(port 5544). When attempting to connect I use the default port number 21 and therefore, as far as I understand connect over the normal FTP protocol. When using Filezilla with the credentials stored in the secrets it works as it should, but not with the action.
My Action Config
on:
push:
branches:
- main
name: 🚀 Deploy to production
jobs:
web-deploy:
name: 🎉 Prod Deployment
runs-on: ubuntu-latest
steps:
- name: 🚚 Get latest code
uses: actions/checkout@v2
- name: 📂 Sync files
uses: SamKirkland/FTP-Deploy-Action@4.0.0
with:
server: ${{ secrets.ftp_server }}
username: ${{ secrets.ftp_user_prod }}
password: ${{ secrets.ftp_password_prod }}
My Action Log
Run SamKirkland/FTP-Deploy-Action@4.0.0
with:
server: ***
username: ***
password: ***
log-level: verbose
----------------------------------------------------------------
🚀 Thanks for using ftp-deploy. Let's deploy some stuff!
----------------------------------------------------------------
If you found this project helpful, please support it
by giving it a ⭐ on Github --> https://github.com/SamKirkland/FTP-Deploy-Action
or add a badge 🏷️ to your projects readme --> https://github.com/SamKirkland/FTP-Deploy-Action#badge
Creating local state at ./.ftp-deploy-sync-state.json
Local state created
Connected to 116.202.46.46:21 (No encryption)
----------------------------------------------------------------
--------------- 🔥🔥🔥 A error occurred 🔥🔥🔥 --------------
----------------------------------------------------------------
----------------------------------------------------------------
---------------------- Full Error below ----------------------
Error: Server sent FIN packet unexpectedly, closing connection.
at Socket.<anonymous> (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:3602:56)
at Socket.emit (events.js:215:7)
at endReadableNT (_stream_readable.js:1184:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Error: Error: Server sent FIN packet unexpectedly, closing connection.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
A brand new website interface for an even better experience!
Similar issue as in #137 : "Server sent FIN packet unexpectedly"
Read more >server sent FIN but didn't accept any data after keep-alive from ...
i have observed this in wireshark packet captures that server sent FIN,ACK. The client sends post request at the same time. server is ......
Read more >Discussion topic: It's the server's fault! - Page 6 - FileZilla Forums
'GnuTLS error -9: A TLS packet with unexpected length was received.' They're stuck there, they can't see the server doing anything wrong, and ......
Read more >TroubleShooting: Object Request Broker (ORB) problems - IBM
TroubleShooting for ORB problems with IBM WebSphere Application Server. ... a connection and then sending FIN-ACK TCP packets to close the connection.
Read more >Citrix Client SSL Error Codes
If you are experiencing this issue and you are not a System Administrator, ... 39 The TTL on the packet sent the destination...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also have the same problem if I use SFTP. Moreover, 1&1 by Ionos does not offer FTP and FTPS anymore, but only SFTP. GitHub Actions are bad and unusable. I hope the author (@SamKirkland) will succeed in seducing us with new features.
Edit 👍 Otherwise, with version 3.3.1 everything works fine! I can’t wait for version 4 to be operational!
on: push name: 🚀 Déployer le site web en push jobs: web-deploy: name: 🎉 Déployer runs-on: ubuntu-latest steps: - name: 🚚 Obtenir le code le plus récent uses: actions/checkout@v2 with: lfs: true fetch-depth : 100
Thanks a lot @lecomteb27!
I had the same issue. I switched to version 3.1.1, and it works now.
I just figured out that the option
--dry-run
is not working in version 3.1.1 (especially in combination with the option--insecure
). I added dry-run for testing purpose in the first place, when I removed that option, it works for me.