I wasn't able to find that exact support case, but there have been a few related to that error over the years. Several were caused by not using https, and one was using https that was terminated at a reverse proxy but the proxy didn't add the expected "X-Forwarded-Proto: https" request header.