Fresh Install on Proxmox VMs no route to host

[neul0n]

Hello,

I've downloaded the ISO and created VMs (Control Plane + Workers), while doing the first install of the CP over the VM deployed in Proxmox I'm not able to reach the VM using the talosctl to apply the configuration.

I'm able to ping the IP that got the VM through DHCP, also using nc I do get response on port 50000 but ctl is failing

❯ nc -zv 192.168.1.31 50000
Connection to 192.168.1.31 port 50000 [tcp/*] succeeded!
❯ talosctl apply-config --insecure --nodes $CONTROL_PLANE_IP --file talos-k8s-master01.yaml
error applying new configuration: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 192.168.1.31:50000: connect: no route to host"

On the VM console I do see connectivity and IP is configured, the IP set is 192.168.1.31/24

Any idea what can be wrong?

[smira]

Do you have HTTP proxy configured by chance? If you do, remove it from the environment.

You can also test by trying to do https:// request to that port ignoring the certificate, which will be closer to what talosctl does, e.g. with curl -k -v https://192.168.1.31:50000/

[neul0n]

No proxy is used and neither configured in the env.
I tested the curl and I got response

curl -k -v https://192.168.1.31:50000/
*   Trying 192.168.1.31:50000...
* Connected to 192.168.1.31 (192.168.1.31) port 50000 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=maintenance-service.talos.dev
*  start date: Jan 29 16:45:42 2025 GMT
*  expire date: Jan 30 16:45:42 2025 GMT
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x55a28c185eb0)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/2
> Host: 192.168.1.31:50000
> user-agent: curl/7.81.0
> accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 4294967295)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 415
< content-type: application/grpc
< grpc-status: 3
< grpc-message: invalid gRPC request content-type ""
<
* Connection #0 to host 192.168.1.31 left intact

Regarding talosctl here is the version:

❯ talosctl version
Client:
	Tag:         v1.9.2
	SHA:         09758b3f
	Built:
	Go version:  go1.23.4
	OS/Arch:     darwin/arm64
Server:
error constructing client: failed to determine endpoints

[smira]

The last thing I would check is $CONTROL_PLANE_IP, run a command without vars. It should be just an IP.

But it's something simple that you're doing wrong probably.

[neul0n]

Was what initially tested to discard there was a problem with the env variable but result is / was the same

EDIT: seems there is something wrong with the talosctl installed in my Mac, I spin a Windows computer to try there the cli and is able to reach it...