2020-10-09 00:28:57 UTC - Mike Ludwig: Did you ever resolve this? I'm getting the same thing: ```[2020-10-09T00:22:41.102Z] [INFO] Querying for pods with label selector: [name=openwhisk-controller]. Namespace: [openwhisk]. Port: [None] [2020-10-09T00:22:41.177Z] [WARN] Resolve attempt failed! Cause: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure``` The only thing that's configured for SSL is the ingress URL (which uses an AWS ALB), though it doesn't show the URL anywhere in the logs. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602203337041800?thread_ts=1591845812.410700&cid=C3TPCAQG1 ---- 2020-10-09 15:58:09 UTC - Anas: Hi @Rodric Rabbah I tried running standalone openwhisk in a docker compose file alongside Postgres and another app and I'm trying to send a request to the openwhisk REST API but I get a 406 Not Acceptable error, though when execute the request from Chrome the status code is 200 Ok.
The request is: `GET http://${WSK_API_HOST}/api/v1/namespaces/guest/actions` And the docker compose file is: ```version: '3' services: pragma-postgres: image: postgres restart: always environment: POSTGRES_USER: test POSTGRES_PASSWORD: test POSTGRES_DB: test ports: - 5433:5432 command: [ "postgres", "-c", "log_statement=all" ] openwhisk: image: openwhisk/standalone:nightly restart: always hostname: openwhisk ports: - 3233:3233 - 3232:3232 volumes: - /var/run/docker.sock:/var/run/docker.sock pragmad: image: pragmad restart: always ports: - 3030:3030 environment: DAEMON_HOSTNAME: pragmad DAEMON_PORT: 3030 DAEMON_PG_URI: 'jdbc:<postgresql://pragma-postgres:5432/test>' DAEMON_PG_USER: 'test' DAEMON_WSK_API_HOST: 'openwhisk:3233' DAEMON_WSK_AUTH_TOKEN: '23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP' DAEMON_PG_PASSWORD: 'test' DAEMON_WSK_API_VERSION: 1 depends_on: - openwhisk - pragma-postgres ``` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602259089045900 ---- 2020-10-09 15:59:37 UTC - Anas: Is it possible that OpenWhisk Standalone assumes that the request from the other container is a remote request that should be denied, but the one from localhost is, well, local and hence can be permitted? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602259177047400 ---- 2020-10-09 18:05:04 UTC - Anas: Never mind, the request was missing the `Accept: application/json` HTTP header partyparrot : Rodric Rabbah https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602266704048200 ---- 2020-10-09 20:31:51 UTC - Brendan Doyle: I'm not sure where the best place I would be able to get this kind of feedback from a group of people, but I'm curious what openwhisk operators use blocking activations vs. non-blocking activations? What use cases do you use non-blocking activations for and is it a very limited subset of use cases that are reserved for non-blocking. My following of the project seems to indicate that many use cases just use blocking activations and I'm trying to gauge whether that theory has any truth https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602275511051100?thread_ts=1602275511.051100&cid=C3TPCAQG1 ----
