texas2step 1.3.0

What's new

• texas2step update upgrades a server to the newest release:

  texas2step update --check   # is a newer release out? (no sudo needed; exit status 100 if so)
  sudo texas2step update

  It downloads the release's package and setup tool to /var/cache/texas2step/update/<version>/, and uses each only if it matches the SHA-256 GitHub publishes with the release. It then runs that release's setup tool in update mode, which plans only the update of what is installed: the package, the settings merge and texas2step's own nginx files. Nothing is published anew, and no firewall rule or setting is added. It shows the plan and asks before it installs. --yes skips the question; --version <version> installs a given release, and --allow-downgrade goes back to an older one.

• Unattended updates: the package brings texas2step-update.timer, off until you turn it on:

  sudo systemctl enable --now texas2step-update.timer

  Every day between 04:00 and 05:00 it installs a newer release, but only when the plan changes nothing but the package and the settings. A release that would also change nginx or the firewall is left for you, with a warning in journalctl -u texas2step-update.

• update_url: where texas2step update looks for releases. By default it's GitHub; it can also be GitHub Enterprise, or a mirror on any web server for networks that can't reach GitHub. The install guide shows how to build one.

• nginx reloads by itself: the setup tool's install script, and so texas2step update, now reloads nginx when an upgrade changes one of the package's nginx files that nginx loads, such as snippets/texas2step.conf. If nginx -t fails with the new files, the previous ones are put back.

• The setup tool has a new --update option, which texas2step update uses. apt now waits for another apt run, such as unattended-upgrades, instead of failing.

Upgrade from 1.2.0

This upgrade is the last one done by hand; after it, sudo texas2step update does them. Download both files below into one directory on the server, then:

sudo ./texas2step-setup
# read texas2step-preflight.txt and texas2step-install.sh, then:
sudo ./texas2step-install.sh

The settings template gained an Updates section (a commented update_url line), so the setup tool shows the settings merge it will make; your values are kept and a dated backup is made. Or upgrade with sudo apt install ./texas2step-1.3.0-1-amd64.deb and run sudo texas2step config merge --write when apt reports the new template.

For a new install, give the setup tool --id, --name and --location, as in the install guide (linked below).

Files

File	SHA-256
texas2step-1.3.0-1-amd64.deb	02114a997d486d258c50136c44050750d20c6fd01138e0b59316f193a6686f7a
texas2step-setup	d62f54cd8b2e267719fc4e65ef143d216c69a2c50bac220c6cfd1865c930c879

The setup tool is built for this package and checks its checksum before using it.

Documentation

• Upgrade: texas2step update, unattended updates, mirrors
• Install guide
• All documentation

texas2step 1.2.0

What's new

• A quieter journal. The service no longer logs every successful request (INFO: 127.0.0.1:… "GET /api/v1/… HTTP/1.1" 200 OK), which an open browser tab produced every second. By default it logs start and stop, warnings and errors, and one line for each failed request (status 400 or above), such as an upload over max_upload_bytes:

  WARNING:  203.0.113.7 - "POST /api/v1/up HTTP/2.0" 413
  

  The address is now the client's, as /api/v1/whoami reports it (behind nginx, from X-Forwarded-For), not 127.0.0.1. Warnings from the WebRTC libraries behind the UDP probe, which were dropped before, now reach the journal too.

• debug: for troubleshooting, debug = true also logs every request and WebSocket, successful ones included, and the UDP probe's WebRTC detail (ICE, DTLS and data channel states). It is very verbose, so turn it off again when done.

  sudo texas2step config set debug=true --write
  sudo systemctl restart texas2step
  journalctl -u texas2step -f

• nginx access log: the package's nginx snippet, and the ones the setup tool writes for other paths, leave the Diag tab's once-a-second /api/v1/diag/http request out of nginx's access log. Every other request is logged as before.

Fixes

• The setup tool no longer prints two Notes that begin with an empty URL (" ends in /, but texas2step is published at /texas2step/ …") on servers without IPv4-only and IPv6-only URLs.

Updates

• FastAPI 0.149.0, websockets 17.3, and Swagger UI 5.34.0 for the API explorer.

Upgrade from 1.1.0

Download both files below into one directory on the server, then:

sudo ./texas2step-setup
# read texas2step-preflight.txt and texas2step-install.sh, then:
sudo ./texas2step-install.sh

The settings template gained a commented debug line, so the setup tool shows the settings merge it will make; your values are kept and a dated backup is made. Or upgrade with sudo apt install ./texas2step-1.2.0-1-amd64.deb and run sudo texas2step config merge --write when apt reports the new template.

If texas2step is published with the package's own snippet (include snippets/texas2step.conf;, at /texas2step/), reload nginx after the upgrade so it reads the new snippet:

sudo nginx -t && sudo systemctl reload nginx

If you edited that snippet, dpkg keeps your copy and saves the new one beside it as texas2step.conf.dpkg-dist. A snippet the setup tool made for another path, such as texas2step-at-speedtest.conf, is rewritten and reloaded by its install script.

For a new install, give the setup tool --id, --name and --location, as in the install guide (linked below).

Files

File	SHA-256
texas2step-1.2.0-1-amd64.deb	7455a6bc184b59494ef30a5e6f5acbed64f8a874b3d2ebc6295e865025c88d6c
texas2step-setup	9d1be09eb3db26c1f53871233709948ec6a1a88e97b0b6acf103ceb259fc031b

The setup tool is built for this package and checks its checksum before using it.

Documentation

• Install guide
• Configuration: logging
• All documentation

texas2step 1.1.0

What's new

• brand_credit: sets how the footer credits the project. link (the default) keeps "texas2step <version>" linked to the project's site; text keeps the words without the link; none leaves the project's name, version and "Powered by" out of the footer, for sites that carry only their own branding. The version is still at /api/v1/health.

  sudo texas2step config set brand_credit=none --write
  sudo systemctl restart texas2step

Upgrade from 1.0.0

Download both files below into one directory on the server, then:

sudo ./texas2step-setup
# read texas2step-preflight.txt and texas2step-install.sh, then:
sudo ./texas2step-install.sh

The settings template gained a commented brand_credit line, so the setup tool shows the settings merge it will make; your values are kept and a dated backup is made. Or upgrade with sudo apt install ./texas2step-1.1.0-1-amd64.deb and run sudo texas2step config merge --write when apt reports the new template.

For a new install, give the setup tool --id, --name and --location, as in the install guide (linked below).

Files

File	SHA-256
texas2step-1.1.0-1-amd64.deb	4bff155d21caca776f31f78539fbc997409d1b38924e7e6af6c95bcf98fafb3f
texas2step-setup	e49a03cf7fd3d03d9be0da003e80ea7254c8a26e546f219769d893fd89f99bfa

The setup tool is built for this package and checks its checksum before using it.

Documentation

• Install guide
• Configuration: branding and themes
• All documentation

texas2step 1.0.0

texas2step measures the network path between a browser and a server: multi-stream throughput, latency and jitter idle and under load, and packet loss over real UDP (WebRTC). It ships as a package for Ubuntu 26.04 LTS that runs behind your existing nginx site.

Highlights

• Test: download and upload over parallel streams, latency and jitter idle and under load with a bufferbloat grade, and UDP packet loss split into upstream and downstream. Results can be exported and shared.
• Monitor: continuous UDP probing with a live round-trip and loss trace, to one server or to two at once from the same browser and clock.
• Diag: HTTPS, WebSocket and UDP over IPv4 and IPv6, each tried once a second, with your addresses, NAT and egress, the HTTP version, TLS, the server's own TCP round trip, and an event log.
• History of saved results, and a REST API with an OpenAPI explorer, plus a command-line client.
• IPv4 and IPv6: with an IPv4-only and an IPv6-only hostname, visitors can hold every test to one family.
• Themes and branding: eight themes, your name, logo, organization, links and notice. Any tab can be hidden.
• Setup tool: texas2step-setup checks a server, reports what it will change and what you must fix, and writes an install script that installs, reinstalls or upgrades, merges your settings, publishes the site through nginx (at /texas2step/ or a path you choose) and opens the UDP range.

Install

Download both files below into one directory on an Ubuntu 26.04 LTS (amd64) server that runs nginx, then:

sudo ./texas2step-setup --id dallas --name dallas.example.net --location "Dallas, TX"
# read texas2step-preflight.txt and texas2step-install.sh, then:
sudo ./texas2step-install.sh

Or install the package yourself with sudo apt install ./texas2step-1.0.0-1-amd64.deb and follow the install guide (linked below).

Files

File	SHA-256
texas2step-1.0.0-1-amd64.deb	288b726d9ed9993165047f2de2f8f95cbe091361ea60dc1de775dc23402ad564
texas2step-setup	05e0953980175ce784e866519bf7f5eab9b3e71c62581463cc1a25d0387c2ec2

The setup tool is built for this package and checks its checksum before using it.

Documentation

• Install guide
• All documentation