style95 commented on issue #4945:
URL: https://github.com/apache/openwhisk/issues/4945#issuecomment-677044764
Then I suspect your controller is not running well because of the above
issue.
If you don't need to secure the connection between nginx and controller, I
suggest changing controller protocol to `http` as @rabbah mentioned above.
You can add this line to `environments/local/group_vars/all` or your
environment configuration.
```
controller_protocol: http
```
Regarding the direct access to a controller, you can check the controller
port using `docker ps`.
```
$ docker ps
CONTAINER ID IMAGE
COMMAND CREATED STATUS PORTS
NAMES
4b01049c888d whisk/controller:latest "/bin/sh -c 'exec /i…" 44
hours ago Up 44 hours 0.0.0.0:15000->15000/tcp,
0.0.0.0:16000->16000/tcp, 0.0.0.0:8000->2551/tcp, 0.0.0.0:10001->8080/tcp
controller0
```
You can access to `http://localhost:10001/ping` and the controller would
return just `pong`.
```
$ curl http://localhost:10001/ping
pong
```
You can also check whether your controller is running well or not via logs.
The default location of the logs is `/tmp/wsklogs/controller0/`.
Even you can configure your wsk cli to directly connect to the controller as
well.
```
$ wsk property set --apihost http://localhost:10001
```
In this case, the cli will directly communicate with a controller. So the
Nginx would do nothing here.
BTW, did you just clone the openwhisk repo and use it or change anything?
You anyway would need to solve the controller directory issue so I want to
make sure the codes are intact.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
