In our case, we were using the wrong subfolder/URL. Changing the URL to match the virtual folder configured in IIS fixed the issue.