walrus-sites-portal

Configure and troubleshoot the Walrus Sites testnet portal for local site visibility.

10|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MystenLabs/skills --skill walrus-sites-portal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walrus-sites-portal
Source: https://github.com/MystenLabs/skills/tree/main/walrus-sites/portal
Command: npx skills add https://github.com/MystenLabs/skills --skill walrus-sites-portal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running Walrus Sites locally for testnet requires a correctly configured portal, and common issues like 404s, port conflicts, and misunderstanding original_package_id can block you from viewing your sites.

Core Features & Use Cases

  • Testnet portal setup: Clone the Walrus Sites repo, install dependencies, copy the testnet config, and start the portal to view testnet sites locally.
  • 404 and misconfiguration troubleshooting: Diagnose Page not found errors by checking blob expiration, verifying original_package_id, and confirming the correct site object URL/subdomain.
  • Portal architecture and routing understanding: Explain how base36 subdomains map to Sui site objects and how dynamic fields lead to Walrus blob retrieval and serving content.
  • Operational guardrails: Provide specific rules like keeping original_package_id unchanged and running the start command from the correct directory.
  • Use case: You have a testnet site and visit a base36 subdomain expecting content, but you see 404; use this skill to verify config correctness, confirm the site object type, and fix the workflow.

Quick Start

Ask the AI: how do I run the local Walrus Sites portal for testnet and troubleshoot a Page not found error on my base36 site URL?

Frequently Asked Questions about walrus-sites-portal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the Walrus Sites portal locally for testnet and view my site?

To run the Walrus Sites portal for testnet, clone the repo, install dependencies, copy the testnet config, and start the portal from the correct directory to resolve and serve your local testnet sites.

Why does my Walrus testnet site return a 404 Page not found error on a base36 subdomain?

A Walrus testnet site 404 error usually means blob expiration, an incorrect original_package_id, or a mismatched site object URL and base36 subdomain configuration that requires validation and correction.

How does base36 subdomain routing resolve to a Sui site object on the Walrus portal?

Base36 subdomain routing on the Walrus portal maps the subdomain to a Sui site object, using dynamic fields to locate and retrieve the corresponding Walrus blob for serving site content.

Do I need to keep the original_package_id unchanged to self-host a Walrus testnet portal?

Yes, you must keep the original_package_id unchanged for the site::Site framework package to ensure the Walrus testnet portal correctly resolves and serves your configured site objects.

What should I do if the Walrus portal fails to start because port 3000 is already in use?

If the Walrus portal fails to start due to a port 3000 conflict, you must diagnose and resolve the port occupancy issue before successfully running the testnet portal to view local sites.

What is the correct workflow to validate a Walrus testnet site object configuration and verify its URL?

The correct workflow to validate a Walrus testnet site object involves checking blob expiration, confirming the site object type, verifying original_package_id, and using concrete URL formats to test site resolution.