Good news, I found another workaround, in case anyone else is experiencing the same issue: opening the link in Chrome, which I otherwise never use, for some reason worked fine. I guess that establishes the issue must be with Firefox?
