afonso
December 3, 2024, 1:03am
1
woovi
No error number but it shows a “DNS lookup failed error=Custom” on logs, “kind: Uncategorized” too
ERROR connectivity_check: DNS connectivity check failed to resolve host=“connectivity-check.warp-svc.” (showing some warns too on logs)
After warp-cli registration new (redirected and used the token to validate my access) the warp UI connects but not really (after verifying on trace page)
afonso
December 3, 2024, 2:13pm
3
the full logs from journalctl warp-svc
dez 03 11:10:25 Deathstar warp-svc[756]: 2024-12-03T14:10:25.681Z ERROR connectivity_check: DNS connectivity check failed to resolve host="connectivity-check.warp-svc."
dez 03 11:10:25 Deathstar warp-svc[756]: 2024-12-03T14:10:25.681Z WARN main_loop: warp::warp::tunnel: Connectivity checks failed, retrying trace_failed=Dns retry_after=1.102000418s
dez 03 11:10:26 Deathstar warp-svc[756]: 2024-12-03T14:10:26.786Z DEBUG connectivity_check: Resolved connectivity.cloudflareclient.com to [162.159.138.65, 162.159.137.65, 2606:4700:7::a29f:8941, 2606:4700:7::a29f:8a41]
dez 03 11:10:26 Deathstar warp-svc[756]: 2024-12-03T14:10:26.865Z DEBUG connectivity_check: fl=196f52
dez 03 11:10:26 Deathstar warp-svc[756]: h=engage.cloudflareclient.com
dez 03 11:10:26 Deathstar warp-svc[756]: ip=186.249.111.131
dez 03 11:10:26 Deathstar warp-svc[756]: ts=1733235026.856
dez 03 11:10:26 Deathstar warp-svc[756]: visit_scheme=https
dez 03 11:10:26 Deathstar warp-svc[756]: uag=WARP for Linux
dez 03 11:10:26 Deathstar warp-svc[756]: colo=FOR
dez 03 11:10:26 Deathstar warp-svc[756]: sliver=none
dez 03 11:10:26 Deathstar warp-svc[756]: http=http/1.1
dez 03 11:10:26 Deathstar warp-svc[756]: loc=BR
dez 03 11:10:26 Deathstar warp-svc[756]: tls=TLSv1.3
dez 03 11:10:26 Deathstar warp-svc[756]: sni=plaintext
dez 03 11:10:26 Deathstar warp-svc[756]: warp=off
dez 03 11:10:26 Deathstar warp-svc[756]: gateway=off
dez 03 11:10:26 Deathstar warp-svc[756]: rbi=off
dez 03 11:10:26 Deathstar warp-svc[756]: kex=X25519
dez 03 11:10:26 Deathstar warp-svc[756]: 2024-12-03T14:10:26.867Z DEBUG connectivity_check: fl=196f69
dez 03 11:10:26 Deathstar warp-svc[756]: h=connectivity.cloudflareclient.com
dez 03 11:10:26 Deathstar warp-svc[756]: ip=104.28.193.67
dez 03 11:10:26 Deathstar warp-svc[756]: ts=1733235026.857
dez 03 11:10:26 Deathstar warp-svc[756]: visit_scheme=https
dez 03 11:10:26 Deathstar warp-svc[756]: uag=WARP for Linux
dez 03 11:10:26 Deathstar warp-svc[756]: colo=FOR
dez 03 11:10:26 Deathstar warp-svc[756]: sliver=none
dez 03 11:10:26 Deathstar warp-svc[756]: http=http/1.1
dez 03 11:10:26 Deathstar warp-svc[756]: loc=BR
dez 03 11:10:26 Deathstar warp-svc[756]: tls=TLSv1.3
dez 03 11:10:26 Deathstar warp-svc[756]: sni=plaintext
dez 03 11:10:26 Deathstar warp-svc[756]: warp=plus
dez 03 11:10:26 Deathstar warp-svc[756]: gateway=off
dez 03 11:10:26 Deathstar warp-svc[756]: rbi=off
dez 03 11:10:26 Deathstar warp-svc[756]: kex=X25519
dez 03 11:10:26 Deathstar warp-svc[756]: 2024-12-03T14:10:26.914Z WARN connectivity_check: DNS lookup failed error=Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" } host="connectivity-check.warp-svc."
dez 03 11:10:27 Deathstar warp-svc[756]: 2024-12-03T14:10:27.914Z WARN connectivity_check: DNS lookup failed error=Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" } host="connectivity-check.warp-svc."
dez 03 11:10:28 Deathstar warp-svc[756]: 2024-12-03T14:10:28.914Z WARN connectivity_check: DNS lookup failed error=Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" } host="connectivity-check.warp-svc."
afonso
December 3, 2024, 5:03pm
4
Already tried this but didnt solved this problem
---
pcx_content_type: troubleshooting
title: Troubleshooting
weight: 4
meta:
description: Review common troubleshooting scenarios for Cloudflare Zero Trust.
---
[❮ Back to FAQ](/cloudflare-one/faq/)
# Troubleshooting
## I tried to register the WARP client with my Zero Trust domain but received the following error messages: `Authentication Expired` and `Registration error. Please try again later`.
When a user logs into an organization, WARP will open a web page so the user can sign in via Cloudflare Access. Access then generates a JSON Web Token (JWT) that is passed from the web page to the WARP client to authenticate the device. This JWT has a timestamp indicating the exact time it was created, as well as a timestamp indicating it will expire 50 seconds into the future.
This error message means that when the JWT is finally passed to the WARP client, it has already expired. One of two things can be happening:
1. (Most likely): Your computer system clock is not properly synced using Network Time Protocol (NTP). Visit [https://time.is](https://time.is) on the affected machine to validate your clock is properly synchronized within 20 seconds of the actual time.
show original
