Was that all of the log messages from ziti-edge-tunnel in your previous post? Id' expect to see either a message about the identity being loaded, like this:
(61043)[ 0.000] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1119 load_identities() loading identity file: zet.shawns-m1-mbp.json
...
(61043)[ 0.038] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1134 load_id_cb() identity[/tmp/zet/zet.shawns-m1-mbp.json] loaded
Or an error message that explains why the file isn't getting loaded. Did you only share the first few lines of the logs?
I have always posted the owl log. I also try to always include command so that one can either check the command itself, and read from the start.
The fact that it is not loading the identity, that would explain why it is not working while everything seems to be set up correctly.
Any way to maybe specify to load exactly that "http_test_identity.json" file that I have, instead of moving it into the folder? Maybe it has some problem with the path.
I am just guessing.
Here I try to use the command identity on/off, to see if something happens. I don't know if it may be useful:
$ sudo ziti-edge-tunnel run
(741012)[ 0.000] INFO ziti-sdk:utils.c:201 ziti_log_set_level() set log level: root=3/INFO
(741012)[ 0.000] INFO ziti-sdk:utils.c:170 ziti_log_init() Ziti C SDK version 0.36.11 @c9993c3(HEAD) starting at (2024-05-29T18:23:21.625)
RTNETLINK answers: File exists
(741012)[ 0.000] ERROR ziti-edge-tunnel:utils.c:31 run_command_va() cmd{ip route add 100.64.0.0/10 dev ziti1} failed: 512/0/Success
(741012)[ 0.000] INFO tunnel-sdk:ziti_tunnel.c:60 create_tunneler_ctx() Ziti Tunneler SDK (v0.22.29-local)
(741012)[ 0.000] INFO tunnel-cbs:ziti_dns.c:164 seed_dns() DNS configured with range 100.64.0.0 - 100.127.255.255 (4194302 ips)
(741012)[ 0.000] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1642 make_socket_path() effective group set to 'ziti' (gid=998)
(741012)[ 0.036] INFO ziti-edge-tunnel:resolvers.c:68 init_libsystemd() Initializing libsystemd
(741012)[ 0.036] INFO ziti-edge-tunnel:resolvers.c:356 try_libsystemd_resolver() systemd-resolved selected as DNS resolver manager
(741012)[ 3.756] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:662 on_cmd() received cmd <{"Command":"IdentityOnOff","Data":{"Identifier":"http_test_identity.json","OnOff":true}}
>
(741012)[ 3.756] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:226 on_command_resp() resp[0,len=61] = {"Success":false,"Error":"ziti context not found","Code":500}
(741012)[ 3.756] WARN ziti-edge-tunnel:ziti-edge-tunnel.c:647 on_cmd() received from client - EOF. Closing connection.
(741012)[ 3.756] WARN ziti-edge-tunnel:ziti-edge-tunnel.c:659 on_cmd() IPC client connection closed, count: 0
(741012)[ 45.249] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:662 on_cmd() received cmd <{"Command":"SetLogLevel","Data":{"Level":"DEBUG"}}
>
(741012)[ 45.249] INFO ziti-sdk:utils.c:201 ziti_log_set_level() set log level: root=4/DEBUG
(741012)[ 45.249] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:398 process_tunnel_commands() Log level is set to DEBUG
(741012)[ 45.249] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:226 on_command_resp() resp[1,len=25] = {"Success":true,"Code":0}
(741012)[ 45.249] DEBUG ziti-edge-tunnel:instance-config.c:131 save_tunnel_status_to_file() Deleted backup config file /var/lib/ziti/config.json.backup
(741012)[ 45.249] DEBUG ziti-edge-tunnel:instance-config.c:134 save_tunnel_status_to_file() Copied config file to backup config file /var/lib/ziti/config.json.backup
(741012)[ 45.249] DEBUG ziti-edge-tunnel:instance-config.c:156 save_tunnel_status_to_file() Saved current tunnel status into Config file /var/lib/ziti/config.json
(741012)[ 45.249] WARN ziti-edge-tunnel:ziti-edge-tunnel.c:647 on_cmd() received from client - EOF. Closing connection.
(741012)[ 45.249] WARN ziti-edge-tunnel:ziti-edge-tunnel.c:659 on_cmd() IPC client connection closed, count: 0
(741012)[ 50.068] DEBUG ziti-edge-tunnel:ziti-edge-tunnel.c:689 on_cmd_client() Received IPC client connection request, count: 1
(741012)[ 50.068] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:662 on_cmd() received cmd <{"Command":"IdentityOnOff","Data":{"Identifier":"http_test_identity.json","OnOff":true}}
>
(741012)[ 50.068] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:226 on_command_resp() resp[0,len=61] = {"Success":false,"Error":"ziti context not found","Code":500}
(741012)[ 50.068] WARN ziti-edge-tunnel:ziti-edge-tunnel.c:647 on_cmd() received from client - EOF. Closing connection.
(741012)[ 50.068] WARN ziti-edge-tunnel:ziti-edge-tunnel.c:659 on_cmd() IPC client connection closed, count: 0
(741012)[ 60.096] DEBUG tunnel-sdk:tunnel_udp.c:269 recv_udp() intercepted address[udp:100.64.0.2:53] client[udp:100.64.0.1:52410] service[ziti:dns-resolver]
(741012)[ 60.096] DEBUG tunnel-cbs:ziti_dns.c:234 on_dns_client() new DNS client
(741012)[ 60.096] DEBUG tunnel-sdk:ziti_tunnel.c:221 ziti_tunneler_dial_completed() ziti dial succeeded: client[udp:100.64.0.1:52410] service[ziti:dns-resolver]
(741012)[ 60.096] DEBUG tunnel-sdk:ziti_tunnel.c:434 ziti_tunneler_close() closing connection: client[udp:100.64.0.1:52410] service[ziti:dns-resolver]
(741012)[ 60.096] DEBUG tunnel-sdk:tunnel_udp.c:126 tunneler_udp_close() closing src[udp:100.64.0.1:52410] dst[udp:100.64.0.2:53] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-sdk:tunnel_udp.c:269 recv_udp() intercepted address[udp:100.64.0.2:53] client[udp:100.64.0.1:55956] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-cbs:ziti_dns.c:234 on_dns_client() new DNS client
(741012)[ 60.097] DEBUG tunnel-sdk:ziti_tunnel.c:221 ziti_tunneler_dial_completed() ziti dial succeeded: client[udp:100.64.0.1:55956] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-sdk:ziti_tunnel.c:434 ziti_tunneler_close() closing connection: client[udp:100.64.0.1:55956] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-sdk:tunnel_udp.c:126 tunneler_udp_close() closing src[udp:100.64.0.1:55956] dst[udp:100.64.0.2:53] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-sdk:tunnel_udp.c:269 recv_udp() intercepted address[udp:100.64.0.2:53] client[udp:100.64.0.1:59565] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-cbs:ziti_dns.c:234 on_dns_client() new DNS client
(741012)[ 60.097] DEBUG tunnel-sdk:ziti_tunnel.c:221 ziti_tunneler_dial_completed() ziti dial succeeded: client[udp:100.64.0.1:59565] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-sdk:ziti_tunnel.c:434 ziti_tunneler_close() closing connection: client[udp:100.64.0.1:59565] service[ziti:dns-resolver]
(741012)[ 60.097] DEBUG tunnel-sdk:tunnel_udp.c:126 tunneler_udp_close() closing src[udp:100.64.0.1:59565] dst[udp:100.64.0.2:53] service[ziti:dns-resolver]
I do see one issue. When you run ziti-edge-tunnel run from the command line as you are, you must specify the identity files that you want to load (with the "-i" / "--identity" command line option) and/or the directories to load identity files from (with the "-I" / "--identity-dir" command line option).
Good catch. Just tried hoping was something that stupid, but still curl to http.ziti gives nothing 
.
$ sudo ziti-edge-tunnel run -i http_test_identity.json
(757362)[ 0.000] INFO ziti-sdk:utils.c:201 ziti_log_set_level() set log level: root=3/INFO
(757362)[ 0.000] INFO ziti-sdk:utils.c:170 ziti_log_init() Ziti C SDK version 0.36.11 @c9993c3(HEAD) starting at (2024-05-29T18:38:25.751)
RTNETLINK answers: File exists
(757362)[ 0.000] ERROR ziti-edge-tunnel:utils.c:31 run_command_va() cmd{ip route add 100.64.0.0/10 dev ziti1} failed: 512/0/Success
(757362)[ 0.000] INFO tunnel-sdk:ziti_tunnel.c:60 create_tunneler_ctx() Ziti Tunneler SDK (v0.22.29-local)
(757362)[ 0.000] INFO tunnel-cbs:ziti_dns.c:164 seed_dns() DNS configured with range 100.64.0.0 - 100.127.255.255 (4194302 ips)
(757362)[ 0.000] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1642 make_socket_path() effective group set to 'ziti' (gid=998)
(757362)[ 0.026] INFO ziti-edge-tunnel:resolvers.c:68 init_libsystemd() Initializing libsystemd
(757362)[ 0.026] INFO tunnel-cbs:ziti_tunnel_ctrl.c:907 load_ziti_async() attempting to load ziti instance[http_test_identity.json]
(757362)[ 0.026] INFO tunnel-cbs:ziti_tunnel_ctrl.c:914 load_ziti_async() loading ziti instance[http_test_identity.json]
(757362)[ 0.026] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1135 load_id_cb() identity[http_test_identity.json] loaded
(757362)[ 0.026] WARN ziti-edge-tunnel:instance.c:40 find_tunnel_identity() Identity ztx[http_test_identity.json] is not loaded yet or already removed.
(757362)[ 0.028] INFO ziti-sdk:ziti.c:454 ziti_init_async() ztx[0] using tlsuv[v0.28.5], tls[Mbed TLS 2.28.5]
(757362)[ 0.028] INFO ziti-sdk:ziti.c:456 ziti_init_async() ztx[0] Loading ziti context with controller[https://ziti-edge-controller:1280]
(757362)[ 0.028] INFO ziti-sdk:ziti.c:933 ziti_re_auth_with_cb() ztx[0] starting to re-auth with ctrl[https://ziti-edge-controller:1280] api_session_status[0] api_session_expired[TRUE]
(757362)[ 0.029] INFO ziti-edge-tunnel:resolvers.c:356 try_libsystemd_resolver() systemd-resolved selected as DNS resolver manager
(757362)[ 0.062] INFO ziti-sdk:ziti.c:1698 version_cb() ztx[0] connected to controller https://ziti-edge-controller:1280 version v1.0.0(a3186132e5eb 2024-04-10T19:42:37Z)
(757362)[ 0.133] INFO ziti-sdk:ziti.c:1589 ziti_set_api_session() ztx[0] api session set, setting api_session_timer to 17940s
(757362)[ 0.133] INFO tunnel-cbs:ziti_tunnel_ctrl.c:767 on_ziti_event() ziti_ctx[http-client] connected to controller
(757362)[ 0.133] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1165 on_event() ztx[http_test_identity.json] context event : status is OK
(757362)[ 0.139] INFO ziti-sdk:channel.c:271 new_ziti_channel() ch[0] (ziti-edge-router) new channel for ztx[0] identity[http-client]
(757362)[ 0.139] INFO tunnel-cbs:ziti_tunnel_ctrl.c:839 on_ziti_event() ztx[http-client] added edge router ziti-edge-router@ziti-edge-router
(757362)[ 0.139] INFO ziti-sdk:channel.c:777 reconnect_channel() ch[0] reconnecting NOW
(757362)[ 10.150] INFO ziti-sdk:posture.c:206 ziti_send_posture_data() ztx[0] first run or potential controller restart detected
(757362)[ 10.180] INFO tunnel-cbs:ziti_tunnel_cbs.c:409 new_ziti_intercept() creating intercept for service[http.svc] with intercept.v1 = {"addresses":["http.ziti"],"portRanges":[{"high":80,"low":80}],"protocols":["tcp"]}
(757362)[ 10.180] INFO tunnel-cbs:ziti_dns.c:292 new_ipv4_entry() registered DNS entry http.ziti -> 100.64.0.3
(757362)[ 10.180] INFO tunnel-cbs:ziti_tunnel_ctrl.c:727 on_service() starting intercepting for service[http.svc]
(757362)[ 10.180] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1290 on_event() =============== service event (added) - http.svc:7NkXfYANG2wP2Qqt8LkaeF ===============
(757362)[ 10.180] INFO ziti-edge-tunnel:tun.c:196 tun_commit_routes() starting 2 route updates
(757362)[ 10.187] INFO ziti-edge-tunnel:tun.c:118 route_updates_done() route updates[2]: 0/OK
(757362)[ 12.717] INFO tunnel-cbs:ziti_dns.c:509 format_resp() found record[100.64.0.3] for query[1:http.ziti]
(757362)[ 20.158] ERROR ziti-sdk:channel.c:903 on_channel_connect_internal() ch[0] failed to connect to ER[ziti-edge-router] [-3001/temporary failure]
(757362)[ 20.158] INFO ziti-sdk:channel.c:775 reconnect_channel() ch[0] reconnecting in 6692ms (attempt = 1)
(757362)[ 36.855] ERROR ziti-sdk:channel.c:903 on_channel_connect_internal() ch[0] failed to connect to ER[ziti-edge-router] [-3001/temporary failure]
(757362)[ 36.855] INFO ziti-sdk:channel.c:775 reconnect_channel() ch[0] reconnecting in 11592ms (attempt = 2)
(757362)[ 58.458] ERROR ziti-sdk:channel.c:903 on_channel_connect_internal() ch[0] failed to connect to ER[ziti-edge-router] [-3001/temporary failure]
(757362)[ 58.458] INFO ziti-sdk:channel.c:775 reconnect_channel() ch[0] reconnecting in 21698ms (attempt = 3)
Still, this is progress!
You can see that your hostname is being looked up, and an answer is being provided:
[12.717] INFO tunnel-cbs:ziti_dns.c:509 format_resp() found record[100.64.0.3] for query[1:http.ziti]
Now it seems that the hostname that your edge router is advertising to clients is not usable from this host:
[20.158] ERROR ziti-sdk:channel.c:903 on_channel_connect_internal() ch[0] failed to connect to ER[ziti-edge-router] [-3001/temporary failure]
Damn, I checked my host file, I missed an 'r'...I wrote
192.168.96.5 ziti-edge-route
Sorry, I had to share this.
Anyway. here it is the new attempt:
$ curl http.ziti
curl: (7) Failed to connect to http.ziti port 80 after 10070 ms: Connection refused
While the tunnel log is:
$ sudo ziti-edge-tunnel run -I /opt/openziti/etc/identities/
(771304)[ 0.000] INFO ziti-sdk:utils.c:201 ziti_log_set_level() set log level: root=3/INFO
(771304)[ 0.000] INFO ziti-sdk:utils.c:170 ziti_log_init() Ziti C SDK version 0.36.11 @c9993c3(HEAD) starting at (2024-05-29T18:51:09.572)
(771304)[ 0.000] INFO ziti-edge-tunnel:instance-config.c:86 load_tunnel_status_from_file() Loading config file from /var/lib/ziti/config.json
(771304)[ 0.000] INFO ziti-sdk:utils.c:201 ziti_log_set_level() set log level: root=3/INFO
RTNETLINK answers: File exists
(771304)[ 0.000] ERROR ziti-edge-tunnel:utils.c:31 run_command_va() cmd{ip route add 100.64.0.0/10 dev ziti1} failed: 512/0/Success
(771304)[ 0.000] INFO tunnel-sdk:ziti_tunnel.c:60 create_tunneler_ctx() Ziti Tunneler SDK (v0.22.29-local)
(771304)[ 0.000] INFO tunnel-cbs:ziti_dns.c:164 seed_dns() DNS configured with range 100.64.0.0 - 100.127.255.255 (4194302 ips)
(771304)[ 0.000] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1716 run_tunneler_loop() Loading identity files from /opt/openziti/etc/identities/
(771304)[ 0.000] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1120 load_identities() loading identity file: http_test_identity.json
(771304)[ 0.000] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1642 make_socket_path() effective group set to 'ziti' (gid=998)
(771304)[ 0.023] INFO ziti-edge-tunnel:resolvers.c:68 init_libsystemd() Initializing libsystemd
(771304)[ 0.023] INFO tunnel-cbs:ziti_tunnel_ctrl.c:907 load_ziti_async() attempting to load ziti instance[/opt/openziti/etc/identities//http_test_identity.json]
(771304)[ 0.023] INFO tunnel-cbs:ziti_tunnel_ctrl.c:914 load_ziti_async() loading ziti instance[/opt/openziti/etc/identities//http_test_identity.json]
(771304)[ 0.023] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1135 load_id_cb() identity[/opt/openziti/etc/identities//http_test_identity.json] loaded
(771304)[ 0.032] INFO ziti-sdk:ziti.c:454 ziti_init_async() ztx[0] using tlsuv[v0.28.5], tls[Mbed TLS 2.28.5]
(771304)[ 0.032] INFO ziti-sdk:ziti.c:456 ziti_init_async() ztx[0] Loading ziti context with controller[https://ziti-edge-controller:1280]
(771304)[ 0.032] INFO ziti-sdk:ziti.c:933 ziti_re_auth_with_cb() ztx[0] starting to re-auth with ctrl[https://ziti-edge-controller:1280] api_session_status[0] api_session_expired[TRUE]
(771304)[ 0.033] INFO ziti-edge-tunnel:resolvers.c:356 try_libsystemd_resolver() systemd-resolved selected as DNS resolver manager
(771304)[ 0.063] INFO ziti-sdk:ziti.c:1698 version_cb() ztx[0] connected to controller https://ziti-edge-controller:1280 version v1.0.0(a3186132e5eb 2024-04-10T19:42:37Z)
(771304)[ 0.089] INFO ziti-sdk:ziti.c:1589 ziti_set_api_session() ztx[0] api session set, setting api_session_timer to 17940s
(771304)[ 0.089] INFO tunnel-cbs:ziti_tunnel_ctrl.c:767 on_ziti_event() ziti_ctx[http-client] connected to controller
(771304)[ 0.089] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1165 on_event() ztx[/opt/openziti/etc/identities//http_test_identity.json] context event : status is OK
(771304)[ 0.104] INFO ziti-sdk:channel.c:271 new_ziti_channel() ch[0] (ziti-edge-router) new channel for ztx[0] identity[http-client]
(771304)[ 0.104] INFO tunnel-cbs:ziti_tunnel_ctrl.c:839 on_ziti_event() ztx[http-client] added edge router ziti-edge-router@ziti-edge-router
(771304)[ 0.104] INFO ziti-sdk:channel.c:777 reconnect_channel() ch[0] reconnecting NOW
(771304)[ 0.107] INFO tunnel-cbs:ziti_tunnel_cbs.c:409 new_ziti_intercept() creating intercept for service[http.svc] with intercept.v1 = {"addresses":["http.ziti"],"portRanges":[{"high":80,"low":80}],"protocols":["tcp"]}
(771304)[ 0.107] INFO tunnel-cbs:ziti_dns.c:292 new_ipv4_entry() registered DNS entry http.ziti -> 100.64.0.3
(771304)[ 0.107] INFO tunnel-cbs:ziti_tunnel_ctrl.c:727 on_service() starting intercepting for service[http.svc]
(771304)[ 0.107] INFO ziti-edge-tunnel:ziti-edge-tunnel.c:1290 on_event() =============== service event (added) - http.svc:7NkXfYANG2wP2Qqt8LkaeF ===============
(771304)[ 0.107] INFO ziti-edge-tunnel:tun.c:196 tun_commit_routes() starting 2 route updates
(771304)[ 0.112] INFO ziti-edge-tunnel:tun.c:118 route_updates_done() route updates[2]: 0/OK
(771304)[ 0.172] INFO ziti-sdk:channel.c:669 hello_reply_cb() ch[0] connected. EdgeRouter version: v1.0.0|a3186132e5eb|2024-04-10T19:42:37Z|linux|amd64
(771304)[ 0.172] INFO tunnel-cbs:ziti_tunnel_ctrl.c:843 on_ziti_event() ztx[http-client] router ziti-edge-router connected
(771304)[ 1.089] INFO ziti-sdk:posture.c:206 ziti_send_posture_data() ztx[0] first run or potential controller restart detected
(771304)[ 7.925] INFO tunnel-cbs:ziti_dns.c:509 format_resp() found record[100.64.0.3] for query[1:http.ziti]
(771304)[ 17.994] ERROR ziti-sdk:connect.c:963 connect_reply_cb() conn[0.0/ELbPSLP2/Connecting] failed to connect, reason=exceeded maximum [2] retries creating circuit [c/OhjAC6V7k]: error creating route for [s/OhjAC6V7k] on [r/ZvI0NtGbB] (error creating route for [c/OhjAC6V7k]: dial tcp: lookup test-blue: i/o timeout)
(771304)[ 17.994] ERROR tunnel-cbs:ziti_tunnel_cbs.c:103 on_ziti_connect() ziti dial failed: connection is closed
I see errors now, but I am not sure how to interpreter those.
dial tcp: lookup test-blue
I'm guessing this "test-blue" hostname is in your host.v1 service configuration? If so the problem is originating on the tunneler (or edge router) that's hosting your open ziti service. Can you check the logs on the hosting router or tunneler?
Sorry for the delay, but I took some time looking at the configurations and did some test. Here it is what I found out. The tunnel it is it is surely more working than not. And that's good.
I have tried (from my host machine) to ping http.ziti and....it answered. Nice. But maybe was simply connected in some way with the underlying docker, so I took the Tunnel down, and the ping stopped. Bringing the tunnel up, and I can ping http.ziti once again. I think we are surely in a good position.
Now, regarding that "test-blue", I really can't remember to have it defined, I always specified "web-test-blue", so I am not sure where it come from.
How can I check the logs you are asking? For the tunnel it was that one?
sudo journalctl -u ziti-edge-tunnel.service > zet.log 2>&1
And what about the ziti-edge-router inside the docker?
Ah,ok sorry I missed that you're running the quickstart.
To get the logs from ziti-edge-router you'd run docker compose logs ziti-edge-router while you're in the directory that contains your compose file.
Yes, I have started from the Docker Compose quickstart and I wanted to "link" this other scenario in order to try to build a first service.
Since the logs are too much this time, I am sending them here as suggested before.
Sorry for the delay.
Looking back at your earlier posts I see that the "test-blue" hostname was introduced when you created the host.v1 configuration:
ziti edge create config http.host.v1 host.v1 '{"protocol":"tcp", "address":"'"${web-test-blue}"'", "port":8000}'
The original quickstart documentation references the ${http_server} variable, and has you set that variable to "web-test-blue" which will get you to the container that's running the http server. When you replaced ${http_server} with ${web-test-blue}, you (inadvertently, I suspect) invoked a shell parameter substation which caused the address to be "test-blue" instead of the intended "web-test-blue".
echo "${web-test-blue}"
test-blue
We can fix this by going back to the controller and updating the host.v1 configuration like this:
ziti edge update config http.host.v1 -d '{"protocol":"tcp", "address":"web-test-blue", "port":8000}'
@scareything, you did the trick. Now it works. I can both ping and curl from my host the server, with the tunneler up.
Since I can't express both you and @TheLumberjack my gratitude enough, and spent spent many hours trying to help me, would you accept a coffee from me?
Does the project has some funding link or a place where I can support it?
1 Like
I write a small recap if anyone else find this thread, so that he may find the problem faster, since it got quite long. Here it is a complete run down of my errors:
-
DNS on Host system. Names were not resolved. Manually added to /etc/hosts (Controller and Edge Router)
-
Manually enroll the token into the tunneler solved (or better, did a workaround) the "-111" error
-
Non specifying the identity when running the tunneler caused it to not work (obviously)
-
Typo in the hosts file, spelled a name wrong, hence it could still not resolve
-
Made an error during the creation of host.v1 file
Now it is working as intended. So this could be a small check list to things you can look at while troubleshooting.
Cheers.
1 Like
Just tell all your friends and go to the github repo and give it a star if you have an account. That's the best way to help the project. Thanks for the recap, too.
Sure, will do! Thanks again!
We will probably ear again so as the more I try to do things 