人工版本：EnterpriseX许可证7.15.3版本71503900
我对目标存储库具有管理员级别的访问权限。我试图上传一个接近10 GB长的工件（air-gapped .tgz）文件。我得到以下错误。
当我尝试使用Artifactory UI上传文件时（单击目标存储库上的Deploy按钮），它将我踢回登录屏幕，而上传显示100%完成，但用于将工件部署为“bundle artifact”或根据用户定义的“Layout”的复选框/选项未显示，弹出窗口底部的Deploy按钮也变灰。
已根据此处的文档使用Access Key尝试curl：https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API，但它给了我一个错误消息后，很长一段时间（12-13+小时）约502坏网关。
我还尝试使用**-x“"选项绕过代理或前缀相同的命令与no_proxy="10.20.30.40" curl ....，但得到相同的错误。尝试-u user：pass，给出相同的错误。工件设置/数据库配置已更改，允许更多连接和更长时间分配超时，但仍然得到相同的错误。
PS：注意第二行258 M下的0，即行下我们完全上传和罚款**这告诉我，没有得到上传。
$ curl -H "X-JFrog-Art-Api:akfljkljkALDJALKDALKJDALKDJLASJDLAKDJALKDJALKDJALKDJALKDJALJKDLKAJFLANCMNLLgoEjcfZ-c7v58FmyaAUsJ8c0gFV6VVHp2WpvYbU7IftRyzirHEmsGJ3MRL0eZqCkyZYI_pkrcgXb3H2QcQ6RxDpbY2UYgX5AKQlrLhtb644wlBtK1VelsJ90d-6TPrr59ss-igGDhS-HUpSMAYMBl9cXQtT5hAR8Q" -X PUT "https://artifactory.company.com/artifactory/AlphaPipeline-PRJ-ProjectABCPipeline-Production-Local/Pipeline-release-3.0.0.tgz" -T Pipeline-release-3.0.0.tgz -v
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 10.20.30.40...
* TCP_NODELAY set
* Connected to artifactory.company.com (10.20.30.40) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: C:/tools/installed/Git/mingw64/ssl/certs/ca-bundle.crt
CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [76 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4146 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ABCDE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=Denver; L=Centennial; O=Spotair Technologies; CN=artifactory.company.com
* start date: Feb 24 20:54:47 2021 GMT
* expire date: Feb 24 20:54:46 2022 GMT
* subjectAltName: host "artifactory.company.com" matched cert's "artifactory.company.com"
* issuer: C=US; O=Entrust, Inc.; OU=See www.entrust.net/legal-terms; OU=(c) 2012 Entrust, Inc. - for authorized use only; CN=Entrust Certification Authority - L1K
* SSL certificate verify ok.
} [5 bytes data]
> PUT /artifactory/AlphaPipeline-PRJ-ProjectABCPipeline-Production-Local/Pipeline-release-3.0.0.tgz HTTP/1.1
> Host: artifactory.company.com
> User-Agent: curl/7.60.0
> Accept: */*
> X-JFrog-Art-Api:akfljkljkALDJALKDALKJDALKDJLASJDLAKDJALKDJALKDJALKDJALKDJALJKDLKAJFLANCMNLLgoEjcfZ-c7v58FmyaAUsJ8c0gFV6VVHp2WpvYbU7IftRyzirHEmsGJ3MRL0eZqCkyZYI_pkrcgXb3H2QcQ6RxDpbY2UYgX5AKQlrLhtb644wlBtK1VelsJ90d-6TPrr59ss-igGDhS-HUpSMAYMBl9cXQtT5hAR8Q
> Content-Length: 11629208547
> Expect: 100-continue
>
{ [5 bytes data]
< HTTP/1.1 100 Continue
} [5 bytes data]
99 10.8G 0 0 99 10.7G 0 357M 0:00:31 0:00:30 0:00:01 258M* We are completely uploaded and fine
100 10.8G 0 0 100 10.8G 0 239k 13:11:33 13:11:33 --:--:-- 0{ [5 bytes data]
< HTTP/1.1 502 Bad Gateway
< Date: Wed, 07 Jul 2021 18:55:33 GMT
< Server: Apache/2.4.46 (Unix) OpenSSL/1.1.1k
< Content-Length: 232
< Content-Type: text/html; charset=iso-8859-1
<
{ [232 bytes data]
100 10.8G 0 232 100 10.8G 0 239k 13:11:33 13:11:33 --:--:-- 54<!DOCTYPE HTML PUBLIC "-//IETF//DPRJ HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
</body></html>
* Connection #0 to host artifactory.company.com left intact另一个奇怪/恼人的事情：如果我在一个小文件上使用相同的API访问密钥（比如几KB），那么我会立即遇到下面的403 Bad props auth token错误。如果我传递另一个文件（ex：> 2 MB）而不更改命令中的任何内容，它会给我上面的502 Bad Gateway错误。
{ [824 bytes data]
100 2576 100 824 100 1752 675 1437 0:00:01 0:00:01 --:--:-- 2113{
"errors" : [ {
"status" : 403,
"message" : "Bad props auth token: apiKey=my_long_apiAccessKeyHere."
} ]
}PS：使用Artifactory GUI上传文件时的相关帖子。Artifactory - Can't upload or see DEPLOY button getting highlighted - can't upload artifact .tar .tgz
1条答案
按热度按时间ztyzrc3y1#
需要注意的一件事是使用的API密钥，我在标题中看到了这一点，
“X-JFrog-Art-Api：akfljkljkALDJALKDALKJDALKDJLASJDLAKDJALKDJALKDJALKDJALJKDLKAJFLANCMNLLgoEjcfZ-c7v58FmyaAUsJ8c0gFV6VVHp2WpvYbU7IftRyzirHEmsGJ3MRL0eZqCkyZYI_pkrcgXb3H 2QcQ6RxDpbY2UYgX5AKQlrLhtb644wlBtK1VelsJ90d-6TPrr59ss-igGDhS-HupSMAYMBl 9cXQtT5hAR8Q”
您从哪里生成API密钥？作为一个测试，您可以使用凭据作为-u：。另外，从配置文件页面生成API密钥，并在头文件中使用它。