Closed thunderZH963 closed 2 years ago
Generally, the 3233 port is for standalone deployment. I think you need to use 80 or 443.
setting --apihost to local IP directly is ok.
I also meet this problem,could i inquire some questions?I used local ip and 172.17.0.1:3223 are not ok. Is it because I'm not using a docker image?My docker ps is empty。
error: Unable to create action 'hello': The connection failed, or timed out. (HTTP status code 500)
@immortalsman In this issue, he deployed a standard deployment using ansible but he tried to use an endpoint for standalone deployment. Which type of deployment are you using?
Hello,friends!Thank you for your answer.I use ansible.I changed it to the local ip address so there is no error message, but there is a new problem that I haven't solved yet.
This is my reference blog https://blog.csdn.net/supergxt/article/details/118114893 ------------------ 原始邮件 ------------------ 发件人: "apache/openwhisk" @.>; 发送时间: 2022年11月10日(星期四) 下午2:35 @.>; 抄送: "pony @.**@.>; 主题: Re: [apache/openwhisk] error: Unable to create action and dial tcp 172.17.0.1:3233: connect: connection refused (Issue #5336)
@immortalsman In this issue, he deployed a standard deployment using ansible but he tried to use an endpoint for standalone deployment. Which type of deployment are you using?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Environment details:
Steps to reproduce the issue:
cat ansible/files/auth.guest
Outputs
'wsk action create hello hello.js' shows that,
'wsk list' shows that,
wsk property set --apihost '172.17.0.1', wsk property set --apihost '172.17.0.1:80', wsk property set --apihost '172.17.0.1:443' were all be tried, but failed.
'Docker ps' shows
According to my observation, all related containers are running, especially the 'nginx'. I can't find which part of my deployment has gone wrong and caused the failure of the 'wsk action create'.
I also want to know how I should configure ‘--apihost' for 'wsk' and which port to check.