Indico pages hung up

Hello, as of this morning our indico is not working properly. In particular events’ timetables are not generated: the “Building timetable” is shown but it is spinning forever and nothing is rendered. See, e.g., Theory Service for the Low Energy Nuclear Physics Community: a Hands-on Workshop (7-9 July 2025): Timetable · ECT* Indico.
Similarly when looking at the Events > Workshops and Collaboration Meetings (Workshops and Collaboration meetings · ECT* Indico), the list gets generated but when one requests to see future or past events again nothing is rendered.
I checked that there is free space on the disk, and I do not see anything particularly off on the server. I have also restarted the machine to no effect. I see some Apache errors, stuff like:

[10/Jun/2025:11:43:46 +0200] “GET /event/236/contributions/5647/Web/ HTTP/1.0” 404
[10/Jun/2025:11:43:48 +0200] “GET /wp-content/uploads/2021/01/Web/ HTTP/1.0” 404
[10/Jun/2025:11:43:48 +0200] “GET /wp-content/et-cache/global/Web/ HTTP/1.0” 404

but I cannot correlate these with what is happening.
Any idea/pointers?
Thanks!

Do you have some cache in front of it? When loading e.g. https://indico.ectstar.eu/assets/js-vars/global.js with Chrome it has some garbage characters at the end…

According to my lords and masters, we do not have any cache mechanism. In addition they told me that the js file looks ok in Firefox, and when opened with an hexadecimal editor. So they are a bit lost as well…

I report it here just in case somebody has the same problem. The issue appeared when the admins in my institutions have abilitated the HTTP/2 protocol on their Nginx reverse proxy which somehow conflicted with the configuration of Indico’s Apache reverse proxy. The problem has been partly solved by disabling compression on Apache (a2dismod deflate).

They report that only Indico has suffered this issue, whereas all other sites served by Apache reverse proxy where running normally.

Still notice that Safari can’t open our indico page reporting that “the server has unexpectedly dropped the connection”. Will update this post if/when also this problem get solved.

Why two reverse proxies? I’m using two indico (one production and one for testing) behind nginx without issues.
The docs let you choose between apache and nginx, and honestly, I find nginx performance better than apache (may because I am more accustomed to using nginx and I don’t know how to fine-tune apache).