jamcalli
jamcalli
I am experiencing the exact same issue. Did you manage to resolve?
I was able to resolve my issue. I was spacing on running dev specifying the preserve symlinks. `npm run dev -- -- --preserve-symlinks` This made my error go away. When...
I had thought that image was causing the crash, but after replacing said image and trying again, I am receiving a new error: `Failed to check for new Dockerhub image...
I can confirm that the 500 error does not show in the logs. However, watchlistarr is not functioning and nothing is sent to any of the arrs. When I restart...
@saschabrockel Did you manage to find a solution?
Did you manage to get it working? After upgrading, and remaking the hosts, they still don't work. I believe it's related the Lua issue with crowdsec a few months back.
@malynel How did you get the config to persist? Every time I restart the container it appends that new config. Tried changing to read only, but the startup sequence changes...
My volumes were configured differently and that wouldn't work for me. I had to do the following after `docker exec -it containername` `nano /etc/s6-overlay/s6-rc.d/cs-crowdsec-bouncer/script.sh` And then manually modify the startup...
A workaround for ESM: ``` import { createRequire } from 'node:module' const require = createRequire(import.meta.url) const cronValidate = require('cron-validate').default ```
@Anubarak @cheddarbob5 Give [Pulsarr](https://github.com/jamcalli/Pulsarr) a try. It's the same workflow under the hood but can route different genres to different folders, etc.