Nick Benson

Having this problem on a 1.16.3 server running on an AWS t3a.medium instance. Johannes' workaround works for me.