Updates and Packetriot v1.0

Published at July 1, 2020 ·  5 min read

We’re really excited to announce that we’ve finally reach version 1.0 for Packetriot! About one-and-half years ago in February of 2019 we released Packetriot to the public. It provided standard application tunneling for HTTP/S and TCP applications. Since then we’ve been iterating our client, website and server software. We added support for automatic certificate management and integration with Let’s Encrypt. We’re still one of the only application tunneling services that provide this integration....

Client Update v0.9.16

Published at June 16, 2020 ·  2 min read

This update includes some bug fixes and some new features. We fixed a dead-lock in our client that preventing tunnels from re-connecting when disconnected so this update is highly recommended. Fixed Dead-Lock We discovered a dead-lock issue that was introduced in an earlier release that impacted clients that used Let’s Encrypt for custom domains. The client periodically checks for opportunities to renew certificates with Let’s Encrypt and then does. This dead-lock would basically lock up any requests to custom domain using Let’s Encrypt after 12 hours....

Client Update v0.9.11

Published at April 17, 2020 ·  3 min read

This update includes several new features that will make using the Packetriot client easier and broader the use-cases it can support. We’ve also made some small updates on existing features too. Find the updates on our downloads page. Use docker pull packetriot/pktriot:0.9.10 to grab our latest x84-64 container image. New Features Instant TCP Forwarding Instant TCP Forwarding is identical to the Instant HTTP service available using the http command with the client....

Client Update v0.9.10

Published at March 23, 2020 ·  3 min read

We added DNS-over-HTTPS support in the last release (v0.9.9). It looks like some users may have had some issues. I think it may be due to some network blocking DNS requests to non-managed servers. E.g (blocking,, …). Some corporate network admins do this. We’ve added a new flag --doh in the configure command and also a field in the configuration file that can be set so that the client will use DNS-over-HTTPS or not (the local DNS system resolver)....

Recent posts

Client Update v0.10.4

Client Update v0.10.2

Client Update v0.10.1

Spokes v1.0.1