It would work fine off and on for me, but the server error always remained; it would show up well after Connections has finished running, showing in the page footer. The lack of any error message isn’t helpful, but in my experience usually means PHP has hot some sort of resource wall, usually memory. I see you have that set to 256MB, but honestly, you can set that to anything because web hosts will hard cap the limit. I would too. You site seems to use about 70MB. It’s hard to image listing 120+ entries soaking up the remaining of the 256MB, but if the hard cap was much lower, that would explain the server error message. And if it isn’t memory, it almost certainly has to be another resource limit; but I wouldn’t know what.
Paginating the results cleared up the error message. That would seem to support a resource limit being the cause. Really, this isn’t a Connections limitation; if you tried to list 120+ WordPress posts on the same page, there would be issues too.
Any ay, the solution is to have the results paginated. There’s not another way around it that I can see.