trizzosk

Hi, this problem occurs not only on clean installations but also appeared on my instance which was upgraded from 2.4.184 to 2.4.188.