New PageKite release, fixes relay connection issues

By Bjarni Rúnar 2020-10-14, 14:29

We have released two minor updates: pagekite.py version 1.5.2.201011, and version 1.0.1.201011 of our Debian packages.

This update fixes a problem with one of the embedded TLS CA certificates, which in some configurations would prevent connections to the relays after a routine update to our TLS certificate this weekend. This mostly effects users of our custom Debian package, and users running pagekite.py on Windows.

We are still investigating whether we can correct this at the relay by deploying a different certificate. If we find such a solution, this blog post will be updated.

Upgrading on Debian:

Assuming you subscribe to our repository, this should work:

sudo apt-get update && sudo apt-get upgrade

Otherwise you may need to manually download a new .deb package and install it yourself.

An alternate solution, for Debian package users who would rather not upgrade or use our repositories, is to add the following line to the very end of the file /etc/pagekite.d/20_frontends.rc:

ca_certs = /etc/ssl/certs/ca-certificates.crt

Upgrading on Windows

Simply download a new pagekite.py and replace your old pagekite.py with the new file.

Other systems

Following the advice on the downloads page to simply install a new version over the old one, should work fine.

The configuration workaround described above is also valid for users of pagekite.py, but then the ca_certs line needs to be added to your .pagekite.rc, pagekite.cfg, or any custom location you may have chosen.