GTM App Engine tagging server - error while updating server

[sudeeshketto]

I am following this guide to update the server - https://developers.google.com/tag-platform/tag-manager/server-side/app-engine-setup#update_the_taggi...

bash -c "$(curl -fsSL https://googletagmanager.com/static/serverjs/setup.sh)"

getting error - Your runtime version for nodejs is past End of support.

how can I change runtime?
My server version is still testing.. I want to change it to production.
On GCP console I can only view the nodejs runtime version. Not able to edit.

[jaydubu]

Hi @sudeeshketto,

Welcome to Google Cloud Community!

I’ve come up with a similar error after following the guide for creating a Google App Engine Standard app with Nodejs runtime + Google Tag Manager setup guide for App Engine. Deploying to the testing version works fine but fails when deploying to the production version due to the error.

Issue: While testing this with the Node.js versions(nodejs18,nodejs20, and nodejs22), Google App Engine Standard and Google Tag Manager integration potentially have compatibility issues and likely doesn't support that version yet. This means GAE won't recognize those as a valid runtime environment and default back to legacy runtimes that reached the end of support.

Troubleshooting: I've attempted the following steps in the Google Cloud CLI / Cloud Shell which you can try and see if it would resolve the issue on your end:

• gcloud components update: to ensure you are using the latest versions.
• npm install: installs a package and any packages that it depends on.
• Install latest Node.js: latest supported version of Node.js.
• Update app.yaml: utilize latest elements for Google App Engine Standard via CLI.
  • Launch CLI / Cloud Shell
  • Update via terminal or Cloud Shell Editor
  • Make sure to save and double check if changes to app.yaml are applied
    • e.g. run cat app.yaml in your app directory

Recommendations: 

1. Create a new project: the documentation indicates that you have to create a new project to follow these steps, so that the script can configure the deployment with the default project values.
   Haven’t tried this due to org restrictions and I don’t have a billing account for personal environment.
2. Enabling deployments for legacy runtimes reaching end of support:  specify organization policy to allow legacy runtimes that have reached the end of support timeline.
3. Consider using Google App Engine flexible environment (if possible): more flexible in terms of runtime versions. It may allow you to use newer versions that aren't yet supported in Google App Engine Standard.

If the issue persists, it would be best to create a bug on the public issue tracker or submit a ticket to Google Cloud Support for further investigation with your project.

I hope the above information is helpful.