How to configure Cron job with Synology Container Manager and Reverse Proxy?

[andreastanner]

⁸Hi there dear community

So happy that i finally found firefly!! Just amazing what you created here James, thank you very much!
Everythink works fine behind a reverse proxy where i mapped custom ports to firefly and the importer to make it reachable outside my home network. But just one thing making me headache since two weeks. I can't get cron running... i tried everythink, including asking dear Chatpgt ;).

This is my setup:

• Synology with Container Manager (formerly Docker)
• I have my own domainname and use a reverse proxy for firefly. Firefly and the importer are working fine.
• I use the standard cron phrase:
  cron:
  image: alpine
  restart: always
  container_name: firefly_iii_cron
  command: sh -c "echo "* * * * * wget -qO- https://firefly.[mydomainname].com/api/v1/cron/jpPT4E6m2nCWz4P4wWaAVdeMRDBikZQi\" | crontab - && crond -f -L /dev/stdout"
  networks:
  - firefly_iii

The STATIC_CRON_TOKEN is a 32 long string in the .env file. like described in the documentation. I also tried to put the 32 characters directly in the line but it changed nothing.

I tried to completely disable the routers and synology firewall in case it's a blocked portnumber or so... changed nothing. I gave permissions to all users on the folders, changed nothing.

The error i get when leave the firewall on:
wget: can't connect to remote host (my public ip): Operation timed oute
,stdout,crond: user root: process already running: wget -qO- https://firefly.[mydomainname].com/api/v1/cron/jpPT4E6m2nCWz4P4wWaAVdeMRDBikZQi

The stange thing is, that when i paste the URL directly into my browswer, it works!! The transaction was made. But why is it working in the browser but not when executed via the normal docker-compose.yml?
This was the URL that worked: https://firefly/.[mydomainname].com/api/v1/cron/jpPT4E6m2nCWz4P4wWaAVdeMRDBikZQi

If anyone has an idea, it would mean me a lot, really 😊.

[JC5]

Alright, so it tries to run but it can't reach the IP address. I don't know a lot about Synology, but I expect that you need to point to the internal IP plus port, so something like 172.16.0.1:8080. Which IP address I can't be sure, but I know you need to add :8080.

[andreastanner]

Hi James, hope you're fine and well.
Sorry for another question. The cron job worked fine liked described above until the new firefly update recenty. Now, i don't know exactly why, the cron job doesn't work even when i paste the URL directly in the browser.... all i get is this. Do you have an idea what is different now? Thanks

[andreastanner]

I just played around a litte bit and now downgraded to the previous version 6.1.15 and the cron tasks work perfectly. So i guess, something changed in 6.1.16 that the cron task is not working anymore? I can go with the previous version but it would be great if future updates work with cron again :).

[JC5]

Nothing changed in between those versions though. And if the count is indeed "0 seconds since the previous run", it simply won't run again.

[andreastanner]

Thanks for the reply. You're right, know the problem occured also in the previous version, the same thing like described above in version 16.
I did another research and found out, that HSTS is the problem... but I'm not sure why. Do you know something about that? The .wget-hsts file is automatically created by the cron job i guess and i see it, but i don't have a clue what to do in this case... I gave all user read and write rights to the file but that changed nothing.

[JC5]

Mmm, that file isn't mine I'm afraid. Is that something locally?