helm-push icon indicating copy to clipboard operation
helm-push copied to clipboard

Error: 308: could not properly parse response JSON:

Open huangxiaojun8023 opened this issue 6 years ago • 5 comments

when i use the helm-push plugin to push a chart to harbor charts repository with command helm push demo2 hillstone, i get the result as below:

308 Permanent Redirect

308 Permanent Redirect


nginx/1.13.8

]]>.

helm version: v2.11.0 helm-push version: 0.7.1 harbor version: 1.7.0 and the chartmuseum version in harbor is 0.7.1

huangxiaojun8023 avatar Jan 09 '19 06:01 huangxiaojun8023

the same err to me: but using helm push url works fine

helm version: 3 beta4 helm-push version: 0.7.1 harbor version: 1.7.5

helm3 push ./helm-chart public

Pushing web-demo-0.0.1.tgz to public...
Error: 308: could not properly parse response JSON: <html>
<head><title>308 Permanent Redirect</title></head>
<body bgcolor="white">
<center><h1>308 Permanent Redirect</h1></center>
<hr><center>nginx/1.13.10</center>
</body>
</html>

Error: plugin "push" exited with error

helm3 push ./helm-chart https://my.harbor/chartrepo/charts --password=pwd --username=user
...
Done

archever avatar Oct 17 '19 08:10 archever

step1: helm repo add harbor-test https://harbor.test.com/chartrepo/test --username=admin --paasword=admin step2: helm push demo2 harbor-test 需要在添加chart源时,加入用户名和密码

qikang avatar Aug 25 '20 07:08 qikang

Who faced with the same problem: I have added repo with http protocol, but nginx redirected it to https. So, update you repo url from http to https explicilty

zifter avatar May 29 '21 20:05 zifter

我是将chart上传到neuxs上报错405,有人知道怎么解决吗? [root@master1 ~]# helm cm-push my-hello-world-0.1.1.tgz lbd-test -u admin -p 23123

Pushing my-hello-world-0.1.1.tgz to lbd-test... Error: 405: could not properly parse response JSON:

405 - Nexus Repository Manager
Exclamation point Error 405 Method Not Allowed
HTTP method POST is not supported by this URL

jinxbinder avatar Dec 02 '21 02:12 jinxbinder

Out of nowhere, I suddenly ran into this issue. I was able to resolve this by removing the chart and re-adding it again

smeeklai avatar Nov 03 '22 10:11 smeeklai