Forum

There are two ways to do it:

1. generate a api key while deploy
2. setup environment variable ZEABUR_AI_HUB_API_KEY=sk----

more detail follow template docs

still：
LLM error: {

"error": {

"code": 400,

"message": "API Key not found. Please pass a valid API key.",

"status": "INVALID_ARGUMENT",

"details": [

{

"@type": "type.googleapis.com/google.rpc.ErrorInfo",

"reason": "API_KEY_INVALID",

"domain": "googleapis.com",

"metadata": {

"service": "generativelanguage.googleapis.com"

}

},

{

"@type": "type.googleapis.com/google.rpc.LocalizedMessage",

"locale": "en-US",

"message": "API Key not found. Please pass a valid API key."

}

]

}

}

Which model are you currently using? You can check it with /status.

Make sure you’ve configured the corresponding API_KEY for authentication.

Please refer to the official documentation to confirm the correct environment variable name:

https://docs.openclaw.ai/providers

Hi please follow instruction to fix telegram problem

The Telegram Bot API has two mutually exclusive methods for receiving updates:

1. Polling (getUpdates) — actively polls for new updates

2. Webhook (setWebhook) — Telegram pushes updates to a specified URL

This 409 error means a webhook was previously set for this bot, but the gateway is now

trying to use polling (getUpdates). Telegram does not allow both at the same time, so it

rejects the request.

Common causes:

• A previous environment or another instance called setWebhook on this bot

• The bot was later switched to polling mode without clearing the webhook first

Fix:

Delete the webhook first, then the gateway can poll normally:

use command to run curl "https://api.telegram.org/bot<YOUR_BOT_TOKEN>/deleteWebhook"

A successful response will return {"ok": true, "result": true}, and the getUpdates

conflict will be resolved.

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.