You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
My pipeline is not working with the following error:
* Connected to sftp.domain.com (157.90.40.40) port 5544 (#0)
< SSH-2.0-sFTP Server ready.
* server response timeout
* Closing connection 0
curl: (28) server response timeout
Between the "Server ready" and the timeout message there are more messages that create something like a wave. My pipeline yaml:
image: php:7.4
pipelines:
branches:
master:
- step:
name: Deploy to production
deployment: production
script:
- apt-get update
- apt-get -qq install git-ftp
- git ftp init -vv --user $LiveFTPUsername --passwd $LiveFTPPassword ftp://sftp.domain.com:5544
I also tried with different ports and with ftp but i get errors all the time. Do you have an idea what the problem could be?
Hey @Pascal Bieri
Welcome to the community!
The error message you share seems to be a generic error message that happens when a connection unable to establish between client and server.
In this case, the pipeline received a timeout from your FTP server. So I wonder if your FTP server is accessible externally. I would suggest you verify
That said, I believe you'll have to configure your git FTP before running the init as per the documentation here
# Setup git config git-ftp.url "ftp://ftp.example.net:21/public_html" git config git-ftp.user "ftp-user" git config git-ftp.password "secr3t" # Upload all files git ftp init
Do try to set up the config first before FTP init the repository. Let me know how it goes.
Cheers,
Syahrul
Thx @Syahrul
Im just checking with the hosting provider. It just happens on a specific one, might be a problem with the firewall.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.