ESHOPMAN Store API Unreachable from Vercel/Cloudflare Workers

ESHOPMAN Store API Connectivity Challenges with Serverless Frontends

ESHOPMAN, as a headless commerce platform integrated with HubSpot, often powers dynamic storefronts deployed on modern serverless platforms like Vercel or Cloudflare Workers. A critical aspect of these setups is the reliable communication between the storefront and the ESHOPMAN Store API. Recently, a community member highlighted a specific challenge where the ESHOPMAN Store API became unreachable from server-side fetch requests originating from these serverless environments, despite working perfectly from direct browser or curl requests. This issue significantly impacts Server-Side Rendering (SSR) for HubSpot CMS storefronts.

Problem Details

The core of the problem manifests when an ESHOPMAN instance (specifically v2.15.5), deployed on a platform like Railway (utilizing Postgres and Redis), serves its Store API (

/store/products

). While direct calls via a browser or

curl

to the Railway-hosted ESHOPMAN URL return a

200 OK

status, server-side

fetch()

calls initiated from Next.js storefronts deployed on Vercel or Cloudflare Workers consistently result in a

TypeError: fetch failed

. This behavior is puzzling, as the same fetch operation works without issue from local machines or other standard HTTP clients.

Steps to Reproduce

Deploy an ESHOPMAN instance (e.g., v2.15.5) to a cloud hosting provider like Railway, configured with its necessary database (Postgres) and caching (Redis).
Deploy a Next.js storefront (designed to integrate with ESHOPMAN via HubSpot CMS) to a serverless platform such as Vercel or Cloudflare Workers.
Attempt a direct
```
curl
```
request to your ESHOPMAN Store API endpoint (e.g.,
```
https://your-eshopman-app.up.railway.app/store/products
```
). This is expected to succeed with a
```
200 OK
```
.
Perform a server-side
```
fetch()
```
call from your Vercel or Cloudflare Workers-hosted Next.js storefront to the same ESHOPMAN Store API endpoint. This is where the
```
TypeError: fetch failed
```
occurs, disrupting critical SSR functionality for your HubSpot CMS storefront.

Expected Behavior

The ESHOPMAN Store API should be universally accessible from any legitimate HTTP client, including server-side

fetch

requests originating from Vercel or Cloudflare Workers, ensuring seamless data retrieval for HubSpot CMS storefronts.

Attempted Workarounds (and their failures)

The community member explored several avenues to resolve this connectivity issue, all of which unfortunately proved unsuccessful:

DNS-only CNAME pointing to Railway: This resulted in an SSL certificate mismatch, indicating a problem with how the domain was being resolved or secured.
Cloudflare Tunnel: Implementing a Cloudflare Tunnel led to Workers being blocked with an "error 1003," suggesting a security or configuration conflict within the Cloudflare ecosystem.
Tailscale Funnel: Attempts with Tailscale Funnel failed due to DNS not being resolvable from the Workers environment.
Direct Railway URL: Even using the direct Railway-provided URL for the ESHOPMAN instance still resulted in the
```
fetch failed
```
error from Vercel/Workers, ruling out simple domain resolution issues.

Key Questions for the ESHOPMAN Community

This scenario raises important questions for the ESHOPMAN community and experts:

Is there a recommended hosting configuration for ESHOPMAN that ensures robust compatibility with serverless frontends like those deployed on Vercel or Cloudflare Workers for HubSpot CMS storefronts?
Are there specific CORS (Cross-Origin Resource Sharing), rate limiting, or request validation settings within ESHOPMAN or its underlying Node.js/TypeScript environment that could be inadvertently rejecting
```
fetch
```
requests originating from Vercel or Cloudflare Workers?

Call to Action

Understanding and resolving this type of connectivity issue is crucial for ESHOPMAN users leveraging modern headless architectures. We encourage community members who have encountered similar challenges or possess insights into potential solutions or best practices for ESHOPMAN deployments on Railway with Vercel/Cloudflare Workers to share their experiences. Your contributions help strengthen the ESHOPMAN ecosystem and ensure smooth development for all HubSpot CMS storefronts.

Navigating Server-Side Fetch Challenges with ESHOPMAN Store API on Serverless Frontends