As described in title.
Please see my previous thread for the URL where the problem now occurs as well as login credentials.
@Tristanarkesteijn I can confirm this has been fixed for the upcoming maintenance release.