Closed traycerb closed 2 months ago
There is taskd 1.2.0 available which afaik solves some of the TLS issues. Well, I cannot tell if yours is solved with the new version, too.
While running taskd keep this in mind.
well, definitely i should upgrade to see if I can replicated, it would have to be upgraded in the Docker image by the owner.
In fact, I had seen your earlier comment about taskd and switching over to syncthing in light of the port scanning issues. I was still hoping to get taskd working , but I use resilio sync for some things, and may try that. Though it's behind a firewall (geo-restricted to US addresses and booting IPs after multiple attempts), security is a complicated thing so that does worry me.
[!IMPORTANT] Taskserver is only compatible with Taskwarrior 2.x, and is no longer actively developed. See
man task-sync
for task synchronization with Taskwarrior 3
I had this issue trying to run taskserver on Docker container ( https://github.com/ogarcia/docker-taskd) on a Synology NAS. Initially, it worked fine, but on server restart, trying to use the same certificates, it would silently exit, and the debug wasn't revealing. Here is what happened when I tried launching the server directly from within docker using verbose logging:
taskd silently fails, or at least I can't understand why the process is no longer running.
As mentioned, when I first created the container from the image, and gave it the relevant environment variables to create new certificates, it worked fine, remotely and all. I copied the brand-new certificates to my client and created permanent volume for the docker image so I wouldn't have to copy the certificates to the client again, as was advised:
This worked great, and even remotely too, but I needed to update and restart my server (Synology NAS running it's own flavor of Linux), and upon restarting the Docker
taskd
server , nothing works. There are no errors, thetaskd
server starts and exits within a few seconds.docker run -d --name=taskd -p 53589:53589 -v /srv/taskd:/var/taskd connectical/taskd
running
docker ps -a
showstaskd
exits after starts (this was screenshotted later, which is why it says57 minutes
)I thought it might be a permissions thing so I opened a session using interactive mode:
sudo docker run -ti -p 53589:53589 -v /srv/taskd:/var/taskd connectical/taskd /bin/sh
Running the diagnostics, I don't see any issue:
The log provides no extra information:
My config is pretty straightforward:
Any ideas? Can you replicate this? Strangely, removing the existing certificates and generated them again, the taskd server will work fine, but copying the certificates each time isn't practical. I'm not sure if it's a
taskd
thing or aDocker
thing, but I'm at the limits of my ability to understand it.Any ideas how to pry more debug information from taskd? More info about why it's failing would be helpful.
Originally posted by @traycerb in https://github.com/ogarcia/docker-taskd/issues/11#issuecomment-1546764399