openclaw - 💡(How to fix) Fix [Bug]: Google Models Connection Failure After Upgrading to OpenClaw 4.21 [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70159Fetched 2026-04-23 07:28:34
View on GitHub
Comments
3
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
commented ×3labeled ×1

After upgrading OpenClaw to version 2026.4.21, Google models (eg. gemma-4-31b-it) fail to connect with network connection errors, while other providers (DeepSeek) work correctly.

Error Message

Google models fail with network connection errors:[agent/embedded] embedded run agent end: runId=7b4aadd0-a9f5-4f04-9cb5-ecef54121594 isError=true model=gemma-4-31b-it provider=google error=LLM request failed: network connection error. rawError=fetch failed [agent/embedded] embedded run agent end: runId=7b4aadd0-a9f5-4f04-9cb5-ecef54121594 isError=true model=gemma-4-31b-it provider=google error=LLM request failed: network connection error. rawError=fetch failed

  • The error occurs specifically with Google models

Root Cause

After upgrading OpenClaw to version 2026.4.21, Google models (eg. gemma-4-31b-it) fail to connect with network connection errors, while other providers (DeepSeek) work correctly.

Code Example

[agent/embedded] embedded run agent end: runId=7b4aadd0-a9f5-4f04-9cb5-ecef54121594 isError=true model=gemma-4-31b-it provider=google error=LLM request failed: network connection error. rawError=fetch failed
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading OpenClaw to version 2026.4.21, Google models (eg. gemma-4-31b-it) fail to connect with network connection errors, while other providers (DeepSeek) work correctly.

Steps to reproduce

  1. Upgraded OpenClaw from previous version to 2026.4.21
  2. Configured Google API key in environment variables
  3. Set Google models in openclaw.json configuration
  4. Enabled Google plugin in configuration
  5. Attempted to use Google models (gemma-4-31b-it)

Expected behavior

Google models should connect successfully using the configured API key and work normally.

Actual behavior

Google models fail with network connection errors:[agent/embedded] embedded run agent end: runId=7b4aadd0-a9f5-4f04-9cb5-ecef54121594 isError=true model=gemma-4-31b-it provider=google error=LLM request failed: network connection error. rawError=fetch failed

OpenClaw version

2026.4.21

Operating system

Win11

Install method

iwr

Model

deepseek

Provider / routing chain

openclaw gateway restart

Additional provider/model setup details

  1. ✅ Verified Google API key is set in environment variables
  2. ✅ Verified Google plugin is enabled in configuration
  3. ✅ Verified Google models are properly configured in openclaw.json
  4. ✅ Verified other providers (DeepSeek) work correctly
  5. ✅ Checked network connectivity (other internet access works)
  6. ✅ No proxy configuration interfering (direct connection)

Logs, screenshots, and evidence

[agent/embedded] embedded run agent end: runId=7b4aadd0-a9f5-4f04-9cb5-ecef54121594 isError=true model=gemma-4-31b-it provider=google error=LLM request failed: network connection error. rawError=fetch failed

Impact and severity

No response

Additional information

  • DeepSeek models work without issues using the same configuration structure
  • The error occurs specifically with Google models
  • No changes were made to network configuration or firewall settings
  • The issue started immediately after upgrading to OpenClaw 4.21

extent analysis

TL;DR

The most likely fix is to check the compatibility of the Google API with OpenClaw version 2026.4.21 and potentially revert to a previous version of OpenClaw or wait for a patch.

Guidance

  • Verify that the Google API key is correctly formatted and valid for the upgraded OpenClaw version.
  • Check the OpenClaw documentation for any changes in Google API integration or requirements in version 2026.4.21.
  • Test other Google models to see if the issue is specific to the gemma-4-31b-it model or a broader Google API compatibility problem.
  • Consider reverting to the previous OpenClaw version to confirm if the issue is indeed caused by the upgrade.

Example

No code snippet is provided as the issue seems related to configuration and compatibility rather than code.

Notes

The issue might be due to changes in the Google API or OpenClaw's integration with it, introduced in version 2026.4.21. Without more specific details on the changes made in this version, it's challenging to provide a definitive fix.

Recommendation

Apply workaround: Revert to the previous version of OpenClaw until a compatible version with the Google API is released, as this is the most straightforward way to restore functionality without waiting for a potential patch.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Google models should connect successfully using the configured API key and work normally.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Google Models Connection Failure After Upgrading to OpenClaw 4.21 [3 comments, 2 participants]