Here is a list of problems you may encounter, with the most common ones listed first. The single most common problem has been that the Taskserver Setup Instructions were not properly followed. Please review the steps you took.
It is always a good idea to make sure that you are using the latest release of Taskwarrior and Taskserver, not just because bugs are fixed that may help you, but also because the solutions below are geared toward the current releases.
If you upgrade from an older release of Taskserver, you will need to follow the upgrade instructions.
You are using version
If you installed Taskwarrior using your OS's package manager, you may be suffering from an out of date package. Prod your OS's package maintainer for an update.
Recent releases make GnuTLS support opt-out instead of
opt-in, so upgrading to the latest version may help.
Otherwise, you will need to build Taskwarrior from the
latest source tarball,
following the instructions in the
Verify that your Taskwarrior was built with GnuTLS support
$ task diagnostics | grep libgnutls libgnutls: 3.3.18
Despite the terrible wording, this means the Taskwarrior
Is it spelled correctly?
Is the domain correct?
Is there a valid DNS resolution for the name?
Is there a firewall between Taskwarrior and Taskserver that
is not letting through
By default, port
If you are unable to open firewall ports, you can use an SSH
Tunnel to route port
$ ssh -L localport:dsthost:dstport email@example.com
There are many reasons that the TLS handshake can fail.
When you generated certificates, you modified a
Additionally, that name must also be used in the
If you are using a self-signed certificate, did you specify
it using the
Certificates have expiration dates, and if you followed our instructions, you created a certificate that is valid for one year. Check your certificate with this command:
$ certtool -i --infile ~/.task/<YOUR NAME>.cert.pem
If your certificate has expired, you need a new one. You may also need to regenerate expired server certificates.
Note that creating certificates that never expire is a bad idea. Certificates may be compromised. A certificate that is considered secure today, may not be considered secure in a year. Is the key length you chose something that will remain suitable in the future? Will the algorithms you chose remain secure? For these reasons, choose an expiration date that lets you reevaluate your choices in the relatively near future.đd>
As a security product, it is imperative that you keep your GnuTLS up to date.
As with many security products, GnuTLS is maintained by a responsible and quick-responding team that takes security very seriously. Benefit from their diligence by keeping your GnuTLS up to date.
We have received reports of issues with older GnuTLS releases. Specifically, version 2.12.20 has problems validating certificates under certain conditions. Newer releases have addressed memory leaks that were able to take down Taskserver.đd>
Client sync key not found.
You skipped the important step of running:
$ task sync initThis performs an initial upload of your pending tasks, and sets up a local sync key, which identifies the last sync transaction. đd>
You may wish to try and debug the problem yourself. You will probably not. But if you do, here is how.
Both Taskwarrior and Taskserver have a
command, the purpose of which is to show you relevant
troubleshooting details. Additionally it will indicate problems
directly, for example, it will tell you if your cert/key files
are not readable. The output from
intended to be included in bug reports, and doing so saves you
a lot of time, because it's the first thing we'll ask for.
$ task diagnostics ... $ taskd diagnostics ...
Read the output of the
diagnostics commands carefully,
there may be several types of problems mentioned, which need to be
addressed before going further.
The next step would be to run the server in debug mode. First shutdown your Taskserver, then launch it interactively:
$ taskdctl stop ... $ taskd server ...
You can hit
Ctrl-C to stop this server. For highly
verbose output, try this:
$ taskd server --debug --debug.tls=2 ...
Similarly, Taskwarrior has a verbose debug mode, and debug TLS mode:
$ task rc.debug=1 rc.debug.tls=2 sync ...
As a last resort, ask for help. But please make sure you have carefully reviewed your setup, and gone through the checks above before asking. No one wants to lead you through the steps above to discover that you didn't.
We'll ask you to provide the
for both Taskwarrior and Taskserver, then we're going to go
through the steps above, because this is our checklist also.
Impress us and mention the codeword 'Weasel', to prove that you at least read this page all the way to the end.
There are several ways of getting help: