@jmcouffin maybe try to use Ping?

@jmcouffin maybe try to use Ping?

I will have a look eventually,
I am a bit swamped with work right now.

Do we really need to check the connection before doing anything? It makes sense if we don't want to crash the code with timeout exceptions... anyway:

• can_access_url is only used by check_internet_connection;
• check_internet_connection uses (not-so-)random urls that have nothing to do with the update process (well, only github.com does), and returns the first successful url, but nobody cares about it
• check_internet_connection is only used by versionmgr.updater._check_connection that actually "cares" about that url, just to display a debug message and return True

This SO answer suggests using socket and a fixed ip address and tcp port instead of relying on name resolutions and application layers.
Here's the code, that I would put in the _check_connection function and discard the other two functions
Not sure if it plays well with IronPython/python.net, though...

import socket

def _check_connection(host="8.8.8.8", port=53, timeout=3):
    """
    Host: 8.8.8.8 (google-public-dns-a.google.com)
    OpenPort: 53/tcp
    Service: domain (DNS/TCP)
    """
    try:
        socket.setdefaulttimeout(timeout)
        socket.socket(socket.AF_INET, socket.SOCK_STREAM).connect((host, port))
        return True
    except socket.error as ex:
        print(ex)  # change it with some logging
        return False

Obviously the .net Ping solution could be the best solution, so that we can port the core of pyrevit to .NET more easily 😉

I didn't test it, but something like this should work

from System.Net.NetworkInformation import Ping, IPStatus

def _check_connection(ip_address="8.8.8.8"):
    ping_sender = Ping()
    try:
        reply = ping_sender.Send(ip_address)
    except Exception:
        return False
    return reply.Status == IPStatus.Success

I didn't test it, but something like this should work

from System.Net.NetworkInformation import Ping, IPStatus

def _check_connection(ip_address="8.8.8.8"):
    ping_sender = Ping()
    try:
        reply = ping_sender.Send(ip_address)
    except Exception:
        return False
    return reply.Status == IPStatus.Success

this did not work.

Do we really need to check the connection before doing anything? It makes sense if we don't want to crash the code with timeout exceptions... anyway:

• can_access_url is only used by check_internet_connection;
• check_internet_connection uses (not-so-)random urls that have nothing to do with the update process (well, only github.com does), and returns the first successful url, but nobody cares about it
• check_internet_connection is only used by versionmgr.updater._check_connection that actually "cares" about that url, just to display a debug message and return True

This SO answer suggests using socket and a fixed ip address and tcp port instead of relying on name resolutions and application layers. Here's the code, that I would put in the _check_connection function and discard the other two functions Not sure if it plays well with IronPython/python.net, though...

import socket

def _check_connection(host="8.8.8.8", port=53, timeout=3):
    """
    Host: 8.8.8.8 (google-public-dns-a.google.com)
    OpenPort: 53/tcp
    Service: domain (DNS/TCP)
    """
    try:
        socket.setdefaulttimeout(timeout)
        socket.socket(socket.AF_INET, socket.SOCK_STREAM).connect((host, port))
        return True
    except socket.error as ex:
        print(ex)  # change it with some logging
        return False

Obviously the .net Ping solution could be the best solution, so that we can port the core of pyrevit to .NET more easily 😉

on the contrary, this did work (tested in 2022 and 2025)

📦 New work-in-progress (wip) builds are available for 5.0.0.24309+2043-wip

Testing WIP build: [5.0.0.24309+2043-wip]

IronPython Traceback:
Traceback (most recent call last):
File "C:\Program Files\pyRevit-Master\bin\netcore\engines\pyRevitLoader.py", line 30, in
File "C:\Program Files\pyRevit-Master\pyrevitlib\pyrevit\loader\sessionmgr.py", line 30, in
File "C:\Program Files\pyRevit-Master\pyrevitlib\pyrevit\versionmgr\updater.py", line 14, in
ImportError: No module named NetworkInformation

📦 New work-in-progress (wip) builds are available for 5.0.0.24315+1435-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24325+1012-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24338+2325-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24340+1616-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24340+1645-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24345+0715-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24351+0714-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24354+1726-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24364+2228-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24364+2256-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.24365+2215-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25006+1041-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25009+2113-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25010+1021-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25010+1128-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25013+1201-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25013+1638-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25013+1855-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25013+1857-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25015+1341-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25015+1357-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25024+1520-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25024+1957-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25025+1310-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25030+1056-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25030+1130-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25030+1138-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25031+1700-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25032+1615-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25032+1635-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25032+1841-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25033+1337-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25033+1402-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25034+1241-wip

📦 New work-in-progress (wip) builds are available for 5.0.0.25034+1511-wip

📦 New public release are available for 5.0.0.24174+2300