Incus remote setup: Error: Get "https://192.168.0.111:8443": Unable to connect to: 192.168.0.111:8443 ([dial tcp 192.168.0.111:8443: connect: no route to host])

samSand · August 4, 2025, 4:09am

Hello Everyone,

I was previously running incus in my homelab server (it is actually just a PC) for a while. The server had only one HDD but now I upgraded it to 1 ssd and 3 more HHDs. I wipe the everything and made a clean install of Rocky Linux. I reinstalled incus and setup the server according to the the documentation.

`[root@localhost ~]# incus version

Client version: 6.8
Server version: 6.8
[root@localhost ~]#
`

The host is reachable from my work station as shown below:

`╰─ ping 192.168.0.111 ─╯

PING 192.168.0.111 (192.168.0.111): 56 data bytes
64 bytes from 192.168.0.111: icmp_seq=0 ttl=64 time=7.031 ms
64 bytes from 192.168.0.111: icmp_seq=1 ttl=64 time=5.407 ms
^C
— 192.168.0.111 ping statistics —
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.407/6.219/7.031/0.812 ms`

`╰─ curl -k https://192.168.0.111:8443 ─╯

{“type”:“sync”,“status”:“Success”,“status_code”:200,“operation”:“”,“error_code”:0,“error”:“”,“metadata”:[“/1.0”]}`

But I am always getting the same error message as shown below.

Incus remote setup: Error: Get "https://192.168.0.111:8443": Unable to connect to: 192.168.0.111:8443 ([dial tcp 192.168.0.111:8443: connect: no route to host])

Now I don’t know where to look at to solve this problem. I can ssh into the host and work via the ssh connection but since I had it working in my previous setup and not now is bothering me a little bit.

Is it possible that the previous setup on my workstation is conflicting with the new setup I am trying to do? The current incus host has the same ip address as before. I deleted the incus remote server entry that was in the remote list of the workstation before trying to add the refreshed server.

I went over the other post but I did not see anybody with similar issue. ChatGPT did not help me much either.

Thank you all

osch · August 4, 2025, 4:21am

First of all welcome…

I would start checking if there is a firewall installed on your new server (disable it for a test), you have configured Incus to accept remote connections and verify all open ports ss -turlp on your server.

Next step would be to test the connection from your client to the server with nc -vz 192.168.0.111 8443.

These are the first basic steps narrow down the issue…

samSand · August 4, 2025, 5:51am

Hello @osch,

Thank you for the response.

Incus seems to be listing on all ports which is it should be right?


Netid     State       Recv-Q      Send-Q           Local Address:Port                   Peer Address:Port     Process                                
udp       UNCONN      0           0                    localhost:323                         0.0.0.0:*         users:(("chronyd",pid=871,fd=5))      
udp       UNCONN      0           0                    localhost:323                            [::]:*         users:(("chronyd",pid=871,fd=6))      
tcp       LISTEN      0           4096                   0.0.0.0:pcsync-https                0.0.0.0:*         users:(("incusd",pid=1178,fd=20))     
tcp       LISTEN      0           128                    0.0.0.0:ssh                         0.0.0.0:*         users:(("sshd",pid=899,fd=3))         
tcp       LISTEN      0           128                       [::]:ssh                            [::]:*         users:(("sshd",pid=899,fd=4))

I am also able to connect to the server.

nc -vz 192.168.0.111 8443                                                                                                                      ─╯
Connection to 192.168.0.111 port 8443 [tcp/pcsync-https] succeeded!

I have disabled all firewall on the host machine

[root@localhost ~]# systemctl status firewalld.service
○ firewalld.service - firewalld - dynamic firewall daemon
     Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:firewalld(1)

But it is still not working somehow. I find the error message at a little insouciant for a newbie like me to detect where the issue is.

incus --debug remote add homelab https://192.168.0.111:8443 --token eyJjbGllbnRfbmFtZSI6ImhvbWVsYWIiLCJmaW5nZXJwcmludCI6IjYyMDk1NjQ0YjY2NzZkY2VmMmI5ODRiMWQ4MWY2Zjc4YjgyOGZlMTIzZmY2MmZjMTJkMDgxZmE4ZjRiZmM0OGIiLCJhZGRyZXNzZXMiOlsiMTkyLjE2OC4wLjExMTo4NDQzIl0sInNlY3JldCI6ImI0M2ZhNzhmYWQ2NGJkZWUwMjQ2NDc3MTU0YzgyY2UzMzc1YjYyZWM3ODRjZmEyMzhjNTYzMDlkZmI5ZDFhMTciLCJleHBpcmVzX2F0IjoiMDAwMS0wMS0wMVQwMDowMDowMFoifQ==
DEBUG  [2025-08-04T00:15:33-05:00] Connecting to a remote Incus over HTTPS       url="https://192.168.0.111:8443"
DEBUG  [2025-08-04T00:15:33-05:00] Sending request to Incus                      etag= method=GET url="https://192.168.0.111:8443/1.0"
Error: Get "https://192.168.0.111:8443": Unable to connect to: 192.168.0.111:8443 ([dial tcp 192.168.0.111:8443: connect: no route to host])

I was about to submit this post but thought I should use another machine to try the setup to check whether the issue is with the server or my main workstation. I am glad to say that I successfully connected my server from the Windows machine. I freshly install incus client using choco install incus and followed the installation guide form the documentation. The issue might be from my iMac. Now I am noticing that the client version on the work station is 6.0.0 and the server is version 6.8. Could that be the reason? let me try it tomorrow.

Thank you

I upgraded the client on the workstation to version 6.15, tried the setup again and it is still producing the same issue.

osch · August 4, 2025, 6:12am

Glad to read that you can connect from Windows. It confirms Incus is working indeed.

Regarding IMac / MacOS you might run into a firewall issue there. On newer MacOs versions you need to allow applications to connect to your local network. Somewhere under System Settings => Privacy & Security => Local Network, check if Terminal is listed and enabled.

Apple has changed and increased their security to protect your system from incoming and outgoing traffic. Without explicit permissions from the enduser it won’t allow connections for installed applications etc. Kind of annoying, not well known and has been quiet buggy from my experience.

Having the same version for both client and server is recommended but for just testing it shouldn’t really matter.

samSand · August 4, 2025, 2:00pm

Hello @osch ,

You are absolutely right. My MacOS was blocking the traffic. I went to System Settings => Privacy & Security => Local Network and enable VS Code to communicate with other devices in the network. After that I did not event have to try twice. I t just work. I didn’t really think about that until you said.

So thank you very much and have a good week.