CODEWITHSUNDEEP
google-apps-scriptgoogle-sheetshttp-status-code-404google-sitesmultiple-accounts
Rick Lugg
Rick Lugg

Reputation: 51

Google Apps scripts called from Google sites now (suddenly) returning 404 error

I have a Google site (https://sites.google.com/site/kitchenergaffers/) which has many pages where scripts are launched. This morning (18 August 2020 EDT) I see that none of the script pages are working and the script seems to be reporting a 404 error of some sort.

The scripts interact with a series of Google sheets

Here is an example of one such page https://sites.google.com/site/kitchenergaffers/home/general-gaffers-information/publish/directory-of-results?display=directory

============= 404. That's an error.

The requested URL /accounts was not found on this server. That's all we know.

There are many pages that run the same script, and some pages that have different scripts. All scripts are set to run Anonymously, anyone can execute

Nothing on the site or within the scripts code or Sheets has changed to create this issue.

UPDATE: Although the error comes up using Chrome browser when logged into the creator account, or my personal account if I open an incognito window they run correctly!

UPDATE2: My PC suffered a Windows update yesterday that may be related however, my Chromebook shows the same problem. This problem does not happen if I use Edge browser.

UPDATE3: If I log out of all my accounts, and only sign in to one of them, the problem does not happen. Once I log into an additional account, the problem recurs. Signing out of all, then back into one only is then necessary.

Upvotes: 1

Views: 2012

Answers (1)

Rick Lugg
Rick Lugg

Reputation: 51

as of 15:00EDT 20 August the issue seems to be resolved. I am not sure if it was something I did experimentally or what, but it has gone.

As it seemed to be related to my account and using Chrome I turned off sync, cleared cookies (also disabling Chrome extensions and bookmarks it seems) then "repaired" or reenabled extensions, resync'd to get the bookmarks from the Chromebook or phone and tried again.

The issue seems to have been resolved - maybe by these actions :)

Upvotes: 1

Related Questions