Azure sftp seems to be broken again

Nick White 40

sftp waws-prod-blu-xxx.ftp.azurewebsites.windows.net

ssh: Could not resolve hostname waws-prod-blu-xxx.ftp.azurewebsites.windows.net: No such host is known.

(where xxx is a 3 digit number)

I have had this before and ended up making a new App Service, with all the complications this causes.

Lex Li 6,037 Reputation points

2024-06-26T06:35:02.9+00:00

That URL pattern matches Azure App Service FTPS service (FTP over SSL). You need to use a specific FTPS client (FileZilla or any other) to connect to it, not ssh.

Note that FTPS is completely different from SFTP (Secure File Transfer Protocol).

And "I have had this before and ended up making a new App Service" might not be relevant.
Nick White 40 Reputation points

2024-06-26T06:39:09.3833333+00:00

Apologies, I should have written ftps. I use SmartFtp etc.

for example, this yields

ssh: Could not resolve hostname waws-prod-blu-xxx.ftp.azurewebsites.windows.net: No such host is known.

ssh -t waws-prod-blu-xxx.ftp.azurewebsites.windows.net

1 answer

Ganeshkumar R 680 Reputation points

2024-06-26T06:44:50.4+00:00
Test if the hostname can be resolved to an IP address using tools like nslookup or ping.

nslookup waws-prod-blu-xxx.ftp.azurewebsites.windows.net

or

ping waws-prod-blu-xxx.ftp.azurewebsites.windows.net

If these commands return errors, it indicates a DNS resolution issue.

Ensure that your network configuration, including DNS settings, is correct. Sometimes corporate or local network settings might block or interfere with DNS resolution.

Make sure that your App Service is up and running. Sometimes, if the App Service is stopped or if there are issues with the service itself, it might cause hostname resolution issues.

And verify that you are using the correct FTP credentials (username and password) provided in the Azure portal for your App Service.

Here is an example of how you might connect using SFTP with the correct hostname and credentials:

sftp ******@waws-prod-blu-123.ftp.azurewebsites.windows.net
Please sign in to rate this answer.
Nick White 40 Reputation points

2024-06-26T06:49:28.21+00:00

nslookup waws-prod-blu-583.ftp.azurewebsites.windows.net

Server: UnKnown

Address: 192.168.0.1

Non-authoritative answer:

Non-authoritative answer:

Name: waws-prod-blu-583.ftp.azurewebsites.windows.net

ping waws-prod-blu-583.ftp.azurewebsites.windows.net

Ping request could not find host waws-prod-blu-583.ftp.azurewebsites.windows.net. Please check the name and try again.

It was working until this afternoon.

Nick White 40 Reputation points

2024-06-26T06:51:15.1566667+00:00

I should add I have tested from other computers on other networks.

Ganeshkumar R 680 Reputation points

2024-06-26T06:54:28.6233333+00:00

Its definitely DNS resolution issue.

Ensure that your network configuration, including DNS settings, is correct.

Sometimes, DNS cache can cause issues. You can try clearing the DNS cache on your local machine.

For Windows:

ipconfig /flushdns

For macOS:

sudo killall -HUP mDNSResponder

For Linux:

sudo systemd-resolve --flush-caches

Nick White 40 Reputation points

2024-06-26T06:54:40.7366667+00:00

To further illustrate that, I logged into the SCM webssh and also a Cloud Shell and the ssh commands at both gives the same result.

Nick White 40 Reputation points

2024-06-26T06:56:09.9366667+00:00

Thanks. I have done that (Windows), but I think the problem is in Azure (see comment above).

Ganeshkumar R 680 Reputation points

2024-06-26T07:00:42.7366667+00:00

Double-check the configuration settings of your App Service to ensure that FTPS is enabled and correctly configured.

Navigate to your App Service in the Azure portal.

Go to "Deployment Center" -> "FTPS Credentials". Verify the FTPS credentials and endpoint.

Go to "Configuration" -> "General settings" and ensure that FTPS is enabled.

Ganeshkumar R 680 Reputation points

2024-06-26T07:01:01.2566667+00:00

Review the logs for your App Service to see if there are any errors or warnings that might indicate issues with FTPS.

Navigate to your App Service in the Azure portal.

Go to "Logs" or use the "Log Stream" feature to review real-time logs.

Ganeshkumar R 680 Reputation points

2024-06-26T07:01:36.9566667+00:00

If possible, try creating a new App Service in a different Azure region to see if the issue is specific to the region where your current App Service is hosted. This can help isolate the problem.

Ganeshkumar R 680 Reputation points

2024-06-26T07:02:15.1+00:00

If you have access to another App Service or a different FTPS endpoint, try connecting to it to see if the issue is isolated to the specific waws-prod-blu-583.ftp.azurewebsites.windows.net endpoint.

Nick White 40 Reputation points

2024-06-26T07:07:01.35+00:00

I have checked the settings and all are OK. Last time this happened, I created another and that was OK.

Nick White 40 Reputation points

2024-06-26T08:48:02.4+00:00

I tested with an App service in another region and all was ok.

I do think this is an Azure NS issue.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Your answer