Error 500 on recurrences

Hi, I just setup an instance using docker compose, and after putting all data in, I’ve got recurrences/recurring payment registered, if I click on them, it tells me “Server Error (500)”.

Logs on container side says: (unable to catch anything better ?) silverstrike-ags-1 | [pid: 10|app: 0|req: 39/61] 172.22.0.1 () {66 vars in 1380 bytes} [Thu Dec 22 21:44:17 2022] GET /recurrences/3/ => generated 145 bytes in 20 msecs (HTTP/1.1 500) 8 headers in 287 bytes (1 switches on core 7)

Seems to be the same for any kind of recurrences, first two to be registered had “System Account” as Source or Destination, maybe it could be linked to this ? One has foreign account (non-System) to Personal account transaction, still can’t access it.

Am I not supposed to edit recurring transactions ?

On Demo: it looks like clicking on a recurring crashed the instance (if you can check logs it was around today 22:00 UTC)

(Setup detail: Linux server, Silverstrike runs in Docker on latest git commit, behind a Nginx reverse proxy, MySQL database hosted out of Docker but accessible)

[simhnna]

Yeah, looks like recurrences that don’t have any linked transactions cause issues. Should be an easy fix

[jusdepatate]

Update: I simply deleted everything i had about silverstrike except database, and got everything back on again and it works this time,

Can confirm original issue is solved on my side now, thanks for such a fast patch