JustAnotherArchivist

#401 is a partial fix for this and checks whether `www` resolves. But of course that subdomain might not exist while others do, and it only applies to new/updated pipelines...

There are two ways how this could be implemented: there could be a cookie jar in the pipeline directory, or it could be pulled from the control node on starting...

The underlying bug is presumably still present in the code, so until it's fixed (or verified that it was already fixed), this issue should stay open. Although yes, in practice...

If you know of an actual bug in the code for it, sure. I think it was just never reconfigured or restarted after a server reboot.

More specifically, it looks like `job.fail` only removes the job from the standard queue but not from `pending-ao`, `pending-large`, or any of the `--pipeline` queues (`pending:*`).

@falconkirtaran Yes, it is broken at least on your pipelines. This is due to falconkirtaran/wpull@56138077, where you removed support for CONNECT. As a result, tunnelling of youtube-dl doesn't work and...

Yes, #217 is definitely still very relevant. > I don't see how this could be related to issues with phantomjs. Not in the technical sense. I just wanted to say...

Upstream issue: ArchiveTeam/wpull#392

~~The new websocket server (#367) crashed. It has been restarted since, but I'm not sure what caused this, so I'm turning this issue into a general one.~~

Turns out that I misunderstood this issue. This was not related to the dashboard server crash in the early morning hours UTC of 2019-05-18 but is a general problem on...