This was fixed yesterday evening, and some fixed a little while earlier. So maybe the user tried to access ExcelFox before the issue was resolved. Could you highlight this there as well.