Error: Client is closed / Closing reason: Error: read ECONNRESET (data socket) #153
Comments
Work aroundI was able to get it to work on |
|
Wanted to make a new issue, but since i have exactly the same problem, i will post here. Will try #153 (comment) and update my post main.yml name: "🚀 Upload to FTP"
on:
push:
branches:
- main
jobs:
web-deploy:
name: 🎉 Deploy
runs-on: ubuntu-latest
steps:
- name: 🚚 Get latest code
uses: actions/checkout@v2.3.2
with:
lfs: true
fetch-depth: 2
- name: 📂 Sync files
uses: SamKirkland/FTP-Deploy-Action@4.1.0
with:
server: ${{ secrets.FTP_HOST }}
username: ${{ secrets.FTP_USER }}
password: ${{ secrets.FTP_PASSWORD }}
exclude: "[**/.git*/**, **/node_modules/**, **/build/, .README.MD, .gitignore]"
protocol: ftps
log-level: verboseaction log: |
|
#153 (comment) is working after hours. Only cause i thought ftpes:// was a mistake so i replaced it with ftps:// God damn i'm stupid. |
|
Same error here |
|
I'm struggling to create a FTP with explizit TLS connect. If I understand the code correct, the The pipeline action prints an error: How can I establish a ftp connection to publish my files? I checked the connection with WinSCP. It's working. |
|
For me, I had to create the server directory in the server myself rather than allowing the tool to create the directory |
|
Lies, I think I just got lucky. Still not happening on large uploads. |
|
The workaround for adding an empty sync state json file seems to work. This is the second time this workaround has been helpful. |
Worked for me as well 😄 |
I have also ran into this problem for the initial deployment and adding the empty |
|
same solution for me, i just create an empty ".ftp-deploy-sync-state.json" file on my repo and the problem fixed. |
|
Always coming back to this issue when after months I need to create a new deployment action and already forgotten that I need that empty file. |
|
|
- based on an open issue in FTP-Deploy-Action: SamKirkland/FTP-Deploy-Action#153 - empty file should help
- based on an open issue in FTP-Deploy-Action: SamKirkland/FTP-Deploy-Action#153 - empty file should help
- based on an open issue in FTP-Deploy-Action: SamKirkland/FTP-Deploy-Action#153 - empty file should help
- based on an open issue in FTP-Deploy-Action: SamKirkland/FTP-Deploy-Action#153 - empty file should help
- based on an open issue in FTP-Deploy-Action: SamKirkland/FTP-Deploy-Action#153 - empty file should help
|
did it for me too lol |
|
This error is now regularly happening for me after it worked for a long time without a problem - I tried it with the empty json file as mentioned above but it's not helping (and the file is not empty anymore which is by design I think) - just restarting my job for the fourth time now (often times restarting once or twice did "fix" it) I'm starting to feel I need to look for another solution if this is regularly failing now :/ |
Bug Description
First time using the action,
so not sure if this is a regressionconfirmed new in4.0.0, works in3.1.1(see comment below)Followed README and action appears to work (due to #123) but log inspection shows otherwise.
Opening this issue specifically for the
Error: Client is closed/Closing reason: Error: read ECONNRESET (data socket)error (see log below).My Action Config
My Action Log
IIS Log
The text was updated successfully, but these errors were encountered: