<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with gcp]]></title><description><![CDATA[A list of topics that have been tagged with gcp]]></description><link>https://fusionauth.io/community/forum/tags/gcp</link><generator>RSS for Node</generator><lastBuildDate>Tue, 29 Sep 2026 00:12:30 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/gcp.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Connection timeouts when using FusionAuth with GCP Cloud NAT]]></title><description><![CDATA[<p dir="auto">This issue is not actually related to FusionAuth itself, but rather to <strong>GCP Cloud NAT port allocation limits</strong>.</p>
<p dir="auto">By default, Cloud NAT only allocates <strong>64 TCP ports per VM</strong> for outbound connections. When your application makes many concurrent connections to FusionAuth (or any external service), you can quickly exhaust these ports, leading to connection timeouts.</p>
Solution
<p dir="auto">Enable dynamic port allocation and increase the port range with this gcloud command:</p>
gcloud compute routers nats update cloud-nat \
  --router=&lt;ROUTER&gt; \
  --region=&lt;REGION&gt; \
  --project=&lt;PROJECT&gt; \
  --enable-dynamic-port-allocation \
  --min-ports-per-vm=1024 \
  --max-ports-per-vm=32768

<p dir="auto">Replace &lt;ROUTER&gt;, &lt;REGION&gt;, and &lt;PROJECT&gt; with your actual GCP resource names.</p>
<p dir="auto">This increases the available ports from 64 to between 1024-32768 per VM, which should resolve the connection timeout issues.</p>
Additional Considerations
<p dir="auto">While this is primarily a GCP infrastructure issue, if you continue to experience connection problems after adjusting your NAT configuration, consider reviewing:</p>

<strong>Network latency between FusionAuth and your database</strong> - High latency or unstable network connectivity can cause database connection pool exhaustion, which may manifest as API timeouts
<strong>Connection pooling settings</strong> - Ensure your application is properly reusing HTTP connections to FusionAuth rather than creating new connections for each request
<strong>Load patterns</strong> - Monitor whether timeouts occur during specific load patterns that might indicate resource constraints

Related Documentation

<a href="https://fusionauth.io/docs/operate/secure/networking" rel="nofollow ugc">FusionAuth Networking Configuration</a> - Configure how FusionAuth determines client IP addresses and network settings
<a href="https://fusionauth.io/docs/operate/troubleshooting/#troubleshooting-api-calls" rel="nofollow ugc">Troubleshooting Connection Issues</a> - General guidance on troubleshooting API calls and connectivity
<a href="https://fusionauth.io/blog/fusionauth-google-kubernetes-engine-deployment" rel="nofollow ugc">Deploying FusionAuth on Google Kubernetes Engine</a> - Best practices for running FusionAuth on GCP
<a href="https://fusionauth.io/partners/google-cloud" rel="nofollow ugc">Google Cloud Platform with FusionAuth</a> - Overview of deploying FusionAuth in GCP environments

External Resources

<a href="https://cloud.google.com/nat/docs/ports-and-addresses" rel="nofollow ugc">GCP Cloud NAT port allocation documentation</a>
Consider monitoring your NAT port usage to right-size these settings for your workload

]]></description><link>https://fusionauth.io/community/forum/topic/3153/connection-timeouts-when-using-fusionauth-with-gcp-cloud-nat</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3153/connection-timeouts-when-using-fusionauth-with-gcp-cloud-nat</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>