blocks|key|2165357|text|我刚刚测试了我们的帐户，这里有一个例子：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2165358|FTP：ftp://waws-prod-bay-014.ftp.azurewebsites.windows.net/site/wwwroot|offset|length|2165359|UserName:+fake__dev\$fake__dev|2165360|密码:不|2165361|港口:+21|2165362|我想一定要确保用户名中有\。|2165363|entityMap|0|LINK|mutability|MUTABLE|url|ftp://waws-prod-bay-014.ftp.azurewebsites.windows.net/site/wwwroot^0|0|4|1U|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

I just tested our account here is an example:

FTP: <a href="ftp://waws-prod-bay-014.ftp.azurewebsites.windows.net/site/wwwroot">ftp://waws-prod-bay-014.ftp.azurewebsites.windows.net/site/wwwroot</a>

UserName: fake__dev\$fake__dev

Password: Nope

Port: 21

I think make sure the username has the \ in it.

blocks|key|1122055|text|我和微软一起打开了一个案例，在反复测试之后，出现了两件事：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122056|有一个服务问题，可能或没有影响我们-它不清楚，因为这是一个部分中断边缘的情况。|ordered-list-item|1122057|Windows10FTP命令行客户端在构建10130时似乎有一个错误，它无法正确处理凭据。我还没有做过网络捕获或其他任何事情；使用另一个客户似乎是有效的，所以我提交了一个反馈项，然后继续前进。|1122058|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|K|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

I opened a case with Microsoft, and after some back and forth and testing, two things came out:

<ol>
<li>There was a service issue which may or may not have impacted us - it's not clear as it was a partial outage edge case situation.</li>
<li>There seems to be a bug in the Windows 10 FTP command-line client as of build 10130 where it doesn't properly handle the credentials. I haven't done a network capture or anything; using another client seemed to work, so I filed a Feedback item and moved on.</li>
</ol>

blocks|key|2165425|text|最近，我也遇到了类似的问题，我试图使用像Filezilla这样的ftp软件，使用定制的部署凭据来访问waws-prod-....azurewebsites.net。我可以使用发布凭据访问服务器，但不能使用部署凭据。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2165426|对我来说，Filezilla有时选择HTTP协议，而不是FTP。在我的例子中，这意味着Filezilla在使用发布凭据时转到ftp://waws...，而在使用部署凭据时转到http://waws...。|2165427|简单修复:始终在url前面使用ftp://。|2165428|entityMap^0|1E|V|0|1Q|D|2F|E|0|F|6|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|K|$]]

I had similar problems lately, while trying to reach <code>waws-prod-....azurewebsites.net</code> with my custom deployment credentials, using ftp software like Filezilla. I could reach the server using the publish credentials, but not with my deployment credentials.

For me it turns out that Filezilla sometimes chooses for a HTTP protocol, rather than the FTP. In my case it meant that Filezilla went to <code>ftp://waws...</code> when I used the publish credentials, but goes to <code>http://waws...</code> when using the deployment credentials.

Simple fix: always use <code>ftp://</code> in front of the url.

blocks|key|1122095|text|这是因为您正在使用的userId和密码在连接时不会使用。在overview.Download+it.Open中有一个Get发布配置文件选项，它使用记事本或可视studio.There是另一个userId和密码given.Use。欲了解更多信息，请参阅本官方指南。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1122096|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/app-service-web/app-service-deployment-credentials^0|36|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This is because userId and password you are using is not to be used while connecting.
There is a Get publish profile option in overview.Download it.Open it with notepad or visual studio.There is another userId and Password given.Use that.
<a href="https://learn.microsoft.com/en-us/azure/app-service-web/app-service-deployment-credentials" rel="nofollow noreferrer">For more info refer this official guide</a>

blocks|key|166962|text|当我通过git命令配置git-ftp.user设置user_name\$user_name时，它无法工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166963|但是，当我编辑.+.git/config文件时，我注意到\缺少。我把它换成了双倍|166964|整个配置文件：|166965|[git-ftp]
++++url+=+ftp://waws-prod-qwerty.ftp.azurewebsites.windows.net:21/site/
++++password+=+qwerty
++++user+=+user_name\\$user_name|code-block|syntax|javascript|166966|现在起作用了。|166967|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

When I set user_name\$user_name by git command config git-ftp.user it was not working.

But when I edited .git/config file I noticed that \ was missing.
I replaced it to double \

Whole config file:

<pre><code>[git-ftp]
 url = ftp://waws-prod-qwerty.ftp.azurewebsites.windows.net:21/site/
 password = qwerty
 user = user_name\\$user_name
</code></pre>

And now it's working.

blocks|key|1122153|text|当您使用App凭据时，它会工作。Azure文档提到了使用用户凭据进行部署的以下内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122154|备注
使用用户级凭据请求者对FTP/FTPS端点进行身份验证的用户名格式如下：\由于用户级凭据链接到用户，而不是特定资源，因此用户名必须以这种格式将登录操作定向到正确的app端点。|blockquote|1122155|来源|offset|length|1122156|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/app-service/deploy-ftp^0|0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|S|8|@]|9|@$G|T|H|U|1|V]]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

It works when you use the App Credentials. Azure docs mention the following for deploying with user credentials.
<blockquote>
Note
Authenticating to an FTP/FTPS endpoint using user-level credentials
requirers a username in the following format:
</blockquote>
<blockquote>
 \ 
</blockquote>
<blockquote>
Since user-level credentials are linked to the user and not a specific
resource, the username must be in this format to direct the sign-in
action to the right app endpoint.
</blockquote>
<a href="https://learn.microsoft.com/en-us/azure/app-service/deploy-ftp" rel="nofollow noreferrer">SOURCE</a>

blocks|key|1122184|text|在我的例子中，我只需转到这个官方指南，在“配置用户范围凭据”标题下，打开Azure门户选项卡，并按照说明获得FTPS凭据。然后，我只需复制并粘贴凭据到我的FTP客户端(FileZilla)，它就能工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1122185|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/azure/app-service/deploy-configure-credentials?tabs=portal^0|E|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

In my case, I simply went to this <a href="https://learn.microsoft.com/en-us/azure/app-service/deploy-configure-credentials?tabs=portal" rel="nofollow noreferrer">official guide</a> and under &quot;Configure user-scope credentials&quot; heading, I opened the Azure portal tab and followed the instructions to get my FTPS credentials. Then, I simply copied and pasted the credentials to my FTP Client (FileZilla) and it worked.

I'm trying to update an Azure Web Site using FTP. In the past, I was able to do this fine using the credentials from the <code>.publishsettings</code> file as has been widely documented. Today, I can't do that. Instead, I get a <code>530 User cannot log in.</code> - even if I regenerate the publish settings and redownload them, the new ones give me the same issue.

Back in October 2013, there was a set of these, e. g. <a href="https://stackoverflow.com/questions/19695178/windows-azure-and-filezilla-ftp">Windows Azure and FileZilla FTP</a> and <a href="https://stackoverflow.com/questions/19704127/trying-to-access-ftp-with-deployment-credentials-530-user-cannot-log-in">Trying to access FTP with deployment credentials: 530 User cannot log in</a>, that were a service failure on the Azure side, but the dashboard at <a href="http://azure.microsoft.com/en-us/status/" rel="nofollow noreferrer">http://azure.microsoft.com/en-us/status/</a> shows clean at the moment, so I don't think that's the same issue.

I don't want to create a new FTP/Git deployment user, because according to both the old and new portals, those credentials apply to all sites in the subscription, and I only want credentials for this site specifically.

What else should I be looking at here?

Thanks!

Azure web site FTP access / 530 User cannot log in

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在尝试使用FTP更新Azure网站。在过去，我能够使用.publishsettings文件中的凭据来很好地完成这一任务，这一点已经被广泛记录下来。今天，我不能那样做。相反，我得到一个530 User cannot log in. --即使我重新生成发布设置并重新下载它们，新的设置也给了我同样的问题。早在2013年1...

问Azure网站FTP access / 530用户无法登录
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Azure网站FTP access / 530用户无法登录EN