tux93

What usually works for me is using a search query to download: `gallery-dl "https://twitter.com/search?q=(from:USER)"`

> Sanity check: > * Delete ~/.nimble to refresh dependencies, recompile Done > * Run `flushdb` in redis-cli to clear Redis, restart nitter Done > * Does it happen if...

> > * Does it happen if you set `redisConnections` and `redisMaxConnections` to 0 in nitter.conf? (disables the connection pool) > > It has not happened again yet but I'd...

With `redisConnections` and `redisMaxConnections` set to 0 it seems to no longer happen, been stable for a day now

For testing purposes I set `redisConnections = 4` and `redisMaxConnections = 8` which also lead to the error and this time produced some async errors in the debug log [nitter_debug.log](https://github.com/zedeus/nitter/files/7900584/nitter_debug.log)

Updated and set the `redis*Connections` values back to default, lets see what'll happen > That's interesting, thank you. Is your Redis config default? Do you use a password? No, no...

For me the latest commit has improved the situation: profile pages no longer become inaccessible, but some RSS requests still time out, which wasn't the case with the `redis*Connections` settings...

Sadly no, the timeouts are still there

Since most other Nextcloud apps (Files, Talk, Notes) offer multi-account support now I'd like to bump this issue again

Pixelfed does have OAuth now, trying to authorize moa leads to a Error 500 page on moa