Problem to deploy to Azure App Service by FTP

[Alberto Moreno]

Hi,

We are trying to do an FTP deployment of a repository to an App Service. The problem we have is that it indicates an error "Login failed: 530 User cannot log in." but with the same credentials we can access with, for example, Filezilla.

Does anyone know where the problem could be? The pipeline configuration is as follows:

name: Deploy to Develop - App Service

        clone:

          enabled: false

        script:

          - pipe: atlassian/ftp-deploy:0.7.0

            variables:

              USER: 'app-service-name\$app-service-name'

              PASSWORD: 'my-pass'

              SERVER: 'myurl-app-service.azurewebsites.windows.net'

              REMOTE_PATH: '/site/wwwroot'

              SET_ARGS: "ssl:verify-certificate false"

              LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/build'

Thank you in advance!

Alberto

[Patrik S]

Hello @Alberto Moreno ,

and thank you for reaching out to Atlassian Community.

The error message suggests it's an issue with the credentials or configuration of the destination FTP server. I found the following resources online that might help with the troubleshooting: 

• Azure App Service FTP Troubleshooting 
• FTP “530 User cannot log in” error and solution 

I would also recommend adding the DEBUG variable to the pipe as it will potentially bring more logs related to this error that can help on the troubleshooting : 

- pipe: atlassian/ftp-deploy:0.7.0
            variables:
              USER: 'app-service-name\$app-service-name'
              PASSWORD: 'my-pass'
              SERVER: 'myurl-app-service.azurewebsites.windows.net'
              REMOTE_PATH: '/site/wwwroot'
              SET_ARGS: "ssl:verify-certificate false"
              LOCAL_PATH: '${BITBUCKET_CLONE_DIR}/build'
              DEBUG: 'true'

Thank you, @Alberto Moreno .

Patrik S

[Alberto Moreno]

Thank you @Patrik S

I have reviewed the links you indicated and I have activated debug mode. In this way I have seen that the problem is in the username indicated in the Azure App Service, and more specifically in the "$" character.

Testing, the way to escape the characters "\" and "$" is as follows: app-service-name\\\$app-service-name

In any case, the way to avoid these problems is to register this value as a variable in the display and thus the value does not have to be escaped.

Thank you so much,
Alberto.

[Patrik S]

Hey @Alberto Moreno !

Happy to hear you were able to identify the solution and thank you very much for sharing it here in the Community, so other users who may come across this error may also try the steps that did work for you. 

If you ever need help in the future, feel free to reach out!

Patrik S