# Issues with Self-Hosted n8n on Google Cloud (Docker Install)

**URL:** <https://community.n8n.io/t/issues-with-self-hosted-n8n-on-google-cloud-docker-install/77142>\
**Category:** Questions\
**Tags:** google-calendar, google, telegram-trigger\
**Created:** [February 12, 2025, 10:47am UTC](https://community.n8n.io/t/issues-with-self-hosted-n8n-on-google-cloud-docker-install/77142 "2025-02-12T10:47:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vincent\_Hoonings](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/vincent_hoonings/32/57462_2.png) [@Vincent\_Hoonings](https://community.n8n.io/u/Vincent_Hoonings)\
**Post date:** [February 12, 2025, 10:47am UTC](https://community.n8n.io/t/issues-with-self-hosted-n8n-on-google-cloud-docker-install/77142/1 "2025-02-12T10:47:01Z")

</div>

I’m running a **self-hosted n8n instance on Google Cloud (Docker install)** , and despite extensive troubleshooting, I **still can’t authenticate with Google services** or **register a Telegram webhook**.

**What is the error message (if any)?**

1️⃣ **Google OAuth Authentication Fails**

• **OAuth Redirect URI:**

```auto
https://n8n.wills.com/rest/oauth2-credential/callback

```

• Verified API credentials, **firewall rules** , and redirect settings, but login still fails.

• Running gcloud sql connect devdb [--user=vincent@wills.com](mailto:--user=vincent@wills.com) returns:

```auto
ERROR: (gcloud.sql.connect) Mysql client not found.

```

2️⃣ **Telegram Webhook Rejection**

• **Error Message:**

```auto
Telegram Trigger1: Bad Request: Webhook can be set up only on ports 80, 88, 443, or 8443.

```

• **n8n is running on port 5678** , proxied via **Nginx to 443** , yet Telegram **still rejects the webhook**.

• SSL (Let’s Encrypt) is configured, and **firewall rules allow necessary traffic**.

**Please share your workflow**

_(Workflow itself isn’t the issue, but logs available if needed.)_

**Share the output returned by the last node**

_(Errors are from API responses, no node-specific issues.)_

**Information on your n8n setup**

• **n8n version:** Latest (as of Feb 2025)

• **Database:** Google Cloud SQL (MySQL 8.0)

• **n8n EXECUTIONS\_PROCESS setting:** Default

• **Running n8n via:** Docker on a Google Cloud VM

• **Operating system:** Debian-based (Google Cloud VM default)

**What We’ve Tried**

✅ **Google OAuth Debugging:**

• Verified **OAuth credentials & redirect URIs** in Google Cloud Console.

• Allowed **Google SQL access & authorized networks** (34.123.216.159, 34.133.19.92).

✅ **Telegram Webhook Fixes:**

• Adjusted **Nginx proxy settings** to forward requests correctly.

• Opened **ports 443, 3306, etc.** for traffic.

• **Reset API tokens & credentials multiple times**.

**Questions:**

1. **Has anyone successfully configured Google OAuth & Telegram webhooks on a self-hosted n8n running in GCP?**

2. **Any workarounds for getting Telegram to recognize the webhook when proxied?**

3. **Is there a specific firewall rule I should add to allow ingress/egress for these services?**

Any insights would be **greatly appreciated!** 🚀

**Thanks in advance!**

**Vincent**

---

<div class="post-metadata">

**Author:** ![n8n](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/n8n/32/196425_2.png) [@n8n](https://community.n8n.io/u/n8n)\
**Post date:** [February 12, 2025, 10:47am UTC](https://community.n8n.io/t/issues-with-self-hosted-n8n-on-google-cloud-docker-install/77142/2 "2025-02-12T10:47:04Z")

</div>

It looks like your topic is missing some important information. Could you provide the following if applicable.

- **n8n version:**
- **Database (default: SQLite):**
- **n8n EXECUTIONS\_PROCESS setting (default: own, main):**
- **Running n8n via (Docker, npm, n8n cloud, desktop app):**
- **Operating system:**

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [May 13, 2025, 10:47am UTC](https://community.n8n.io/t/issues-with-self-hosted-n8n-on-google-cloud-docker-install/77142/3 "2025-05-13T10:47:55Z")

</div>

Closed on May 13, 2025, 10:47am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
