workspaces-issues
workspaces-issues copied to clipboard
kasmtech
registry enpoint being blocked by ISP
I know this is a weird one..
Log:
host: f92918fb2c12
ingest_date: 20251125134056
application: kasm_api
levelname: ERROR
kasm_user_name: [email protected]
process: admin_api_server
client_ip: 216.183.XXX.XXX
user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36 Edg/142.0.0.0
message
Invalid registry URL https://registry.kasmweb.com/: <urlopen error [Errno 101] Network is unreachable>
so i checked from every machine i found at my home network:
C:\Users\customicon>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : TABLET-H2N89QU6
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek USB FE Family Controller
Physical Address. . . . . . . . . : 00-E0-4C-36-2E-03
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.100.195(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, November 23, 2025 2:26:56 AM
Lease Expires . . . . . . . . . . : Wednesday, November 26, 2025 6:36:48 PM
Default Gateway . . . . . . . . . : 192.168.100.1
DHCP Server . . . . . . . . . . . : 192.168.100.53
DNS Servers . . . . . . . . . . . : 1.1.1.1
1.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
i used ping and curl to check whats going on:
root@pve-01:~# ping -c 3 registry.kasmweb.com
PING kasm-technologies.gitlab.io (35.185.44.232) 56(84) bytes of data.
64 bytes from 232.44.185.35.bc.googleusercontent.com (35.185.44.232): icmp_seq=1 ttl=100 time=254 ms
64 bytes from 232.44.185.35.bc.googleusercontent.com (35.185.44.232): icmp_seq=2 ttl=100 time=254 ms
64 bytes from 232.44.185.35.bc.googleusercontent.com (35.185.44.232): icmp_seq=3 ttl=100 time=254 ms
--- kasm-technologies.gitlab.io ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 254.358/254.363/254.370/0.005 ms
root@pve-01:~# curl -L -vvv https://registry.kasmweb.com
18:47:44.756024 [0-x] == Info: [READ] client_reset, clear readers
18:47:44.807026 [0-0] == Info: Host registry.kasmweb.com:443 was resolved.
18:47:44.807176 [0-0] == Info: IPv6: 2600:1901:0:7b8a::
18:47:44.807268 [0-0] == Info: IPv4: 35.185.44.232
18:47:44.807364 [0-0] == Info: [HTTPS-CONNECT] adding wanted h2
18:47:44.807519 [0-0] == Info: [HTTPS-CONNECT] added
18:47:44.807627 [0-0] == Info: [HTTPS-CONNECT] connect, init
18:47:44.807775 [0-0] == Info: Trying [2600:1901:0:7b8a::]:443...
18:47:44.808023 [0-0] == Info: Immediate connect fail for 2600:1901:0:7b8a::: Network is unreachable
18:47:44.808245 [0-0] == Info: Trying 35.185.44.232:443...
18:47:44.808427 [0-0] == Info: [HTTPS-CONNECT] connect -> 0, done=0
18:47:44.808552 [0-0] == Info: [HTTPS-CONNECT] Curl_conn_connect(block=0) -> 0, done=0
18:47:44.808733 [0-0] == Info: [HTTPS-CONNECT] adjust_pollset -> 1 socks
18:47:44.820924 [0-0] == Info: [HTTPS-CONNECT] connect -> 0, done=0
18:47:44.821081 [0-0] == Info: [HTTPS-CONNECT] Curl_conn_connect(block=0) -> 0, done=0
18:47:44.821280 [0-0] == Info: [HTTPS-CONNECT] adjust_pollset -> 1 socks
18:47:45.008632 [0-0] == Info: [HTTPS-CONNECT] connect -> 0, done=0
18:47:45.008794 [0-0] == Info: [HTTPS-CONNECT] Curl_conn_connect(block=0) -> 0, done=0
18:47:45.008985 [0-0] == Info: [HTTPS-CONNECT] adjust_pollset -> 1 socks
18:47:46.009433 [0-0] == Info: [HTTPS-CONNECT] connect -> 0, done=0
18:47:46.009543 [0-0] == Info: [HTTPS-CONNECT] Curl_conn_connect(block=0) -> 0, done=0
18:47:46.009676 [0-0] == Info: [HTTPS-CONNECT] adjust_pollset -> 1 socks
18:47:47.010443 [0-0] == Info: [HTTPS-CONNECT] connect -> 0, done=0
18:47:47.010767 [0-0] == Info: [HTTPS-CONNECT] Curl_conn_connect(block=0) -> 0, done=0
18:47:47.011114 [0-0] == Info: [HTTPS-CONNECT] adjust_pollset -> 1 socks
^C
root@pve-01:~# curl https://registry.kasmweb.com
<STUCK FOREVER>
from another network which is okay:
aman@MLE-IT-01:~$ curl https://registry.kasmweb.com
<a href="https://registry.kasmweb.com/1.1/">Moved Permanently</a>.
aman@MLE-IT-01:~$
i do selfhost a vpn where routing peer has warp enabled to access blocked sites. i might be on correct route
Hi there, thanks for providing the detailed logs.
The behavior you’re seeing isn’t related to the Kasm registry itself. Our registry is hosted on GitLab’s infrastructure (hence gets the IP from GitLab's IP Pool), which should be globally reachable and shouldn't require any special whitelisting. Since your curl/ping tests work normally from another network, this strongly suggests that something within your local environment is blocking or interfering with outbound connectivity to the registry.
Unfortunately, we’re not able to troubleshoot individual user network configurations.
