Cannot load PageBuilder locally after fusion init → blank screen at /experiences/_default/pages/

[jquintana-lanacion]

Hi everyone,

I’m trying to run a local Fusion project for Micro Experience testing and following the official guide How To Run PageBuilder Engine Locally.

---

What I did

• Ran fusion init → structure created successfully.
• Created two sites under properties/sites/:
  • la-nacion-ar (default)
  • foodit
• Added two output-types (default.jsx and foodit.jsx).
• Verified folder structure, mocks and arc.config.json.
• Ran fusion start.

---

Environment

• OS: Ubuntu 22.04.4
• Node: v20.19.3
• NPM: 10.8.2
• Fusion CLI: 6.0.0
• Docker installed with enough resources (RAM/CPU).

---

Logs

• fusion start completes successfully.
• Engine and Webpack containers build correctly.
• Output shows: “Server ready: http://0.0.0.0:8080 🚀”.
• No errors in terminal logs.

---

Issue

When I open:
👉 http://localhost/pagebuilder/pages

It redirects to:
👉 http://localhost/pagebuilder/experiences/_default/pages/

But the UI remains completely blank (white screen).
Browser console shows errors such as TypeError: g is not a function in a minified file (main.415995a7.js).

---

Verifications

• CONTENT_BASE and ARC_ACCESS_TOKEN are configured correctly (already set when the ticket was opened).
• Ran npx fusion verify → passes successfully, only warnings (caniuse-lite outdated, Sass @import deprecation, Webpack performance recommendations). No blocking errors.

---

What I need

• Guidance on why PageBuilder is not loading locally after a clean fusion init setup.
• Clarification if there are additional flags or steps required for multi-site configuration.
• Any known issues in Fusion 6.0.0 with PageBuilder local engine that could explain the blank screen.

---

Attaching screenshots of the browser state and console errors if needed.

Thanks in advance for your help!

Best regards,
Julio

[emilynielson]

Hi @jquintana-lanacion, There was a fusion-cli release today. Which fusion-cli are you using? The release today was for 3.1.0.

I get the same behavior you are seeing when I set FUSION_RELEASE=latest or FUSION_RELEASE=6.0.0.

The page loads for me when I either don't set FUSION_RELEASE in the .env or set FUSION_RELEASE=6.1.0. To unblock you, can you try using FUSION_RELEASE=6.1.0 while the Arc team investigates.

[Ciip1996]

Hi @emilynielson I am having the same issue on outboundfeeds and I already applied the FUSION_RELEASE=6.1.0

I get the following errors:

UPDATE: It was the wrong credentials on the .env ARC_ACCESS_TOKEN and CONTENT_BASE :v