Deploy the script as a web app and use the exec address, with access set to anyone.
What the message means
The script answers with a redirect. A client that does not follow it, or a deployment with limited access, gets an error page instead of your data.
Fix it in this order
- Deploy the script as a web app and copy the exec URL.
- Set access to anyone, knowing the link is then public, and keep it secret.
- Make the HTTP client follow redirects.
- Use HTTPS with the setting your library needs.
- After editing the script, deploy a new version, since the old one is still served.
- Test the URL in a browser first.
If you see this, do this
| You see | Do this |
|---|---|
| Receives a login page | Access is not set to anyone. |
| Gets a redirect code only | Follow redirects. |
Related
HTTPS errors, HTTP error codes.
Last reviewed: November 2026. These are the usual causes and the order that finds them fastest. Test on your own board; clones and cables differ.