vsock_proxy problem

[longtranv]

I start vsock_proxy installed along with nitro enclave cli and nothing happened. Log of service gives warnings "Unable to resolve allow listed host: "kms.ap-southeast-1.amazonaws.com"."

Application running inside nitro enclave also could not connect to kms after that. Please help!

[atanzu]

Hi longtranv, could you please share your network configuration? It might be that your instance has a specific firewall or network configuration which blocks the connection.

Could you also check if the host is available via running nslookup kms.ap-southeast-1.amazonaws.com and ping kms.ap-southeast-1.amazonaws.com ?

[longtranv]

Hi longtranv, could you please share your network configuration? It might be that your instance has a specific firewall or network configuration which blocks the connection.

Could you also check if the host is available via running nslookup kms.ap-southeast-1.amazonaws.com and ping kms.ap-southeast-1.amazonaws.com ?

there is no firewall enable in my parent isntance, I use nslookup and ping or telnet for kms.ap-southeast-1.amazonaws.com successfully. Do you know any the clearest possible signs that the vsock proxy running properly because the problem is that i cannot exactly know the proxy run or not :))

[longtranv]

Hi longtranv, could you please share your network configuration? It might be that your instance has a specific firewall or network configuration which blocks the connection.
Could you also check if the host is available via running nslookup kms.ap-southeast-1.amazonaws.com and ping kms.ap-southeast-1.amazonaws.com ?

there is no firewall enable in my parent isntance, I use nslookup and ping or telnet for kms.ap-southeast-1.amazonaws.com successfully. Do you know any the clearest possible signs that the vsock proxy running properly because the problem is that i cannot exactly know the proxy run or not :))

and when I use vsock proxy binary directly, it hangs forever

[atanzu]

and when I use vsock proxy binary directly, it hangs forever

You mean, your terminal is stuck when you execute e.g. vsock-proxy 8000 kms.us-east-1.amazonaws.com 443? That's the expected behaviour.

This section of the Readme tells how to enable more logs, could you please try that?

Do you know any the clearest possible signs that the vsock proxy running properly

I'd recommend to try running this example modified with a ping command, so if pings from an Enclave work, then the proxy is up and running.

[atanzu]

Hi @longtranv , could you please let us know if you've solved the problem?

[longtranv]

Hi @longtranv , could you please let us know if you've solved the problem?

Everything connected successfully, that is just it’s normal behavior. Just enable vsock-proxy service and done. Then we have to transform vsock client into http client for connecting KMS through proxy. Because the developers of this service did not set up any log so it makes me confused 😅. Also, Thank you so much anyway