xlm.sh

Appearance

Troubleshooting ​

Error pages on xlm.sh link to the matching section below. The grey box on an error page gives the exact reason.

404: There is no site here ​

  • The name is not a Soroban Domain in registry v1, or it has expired. Check it with the lookup on the home page. Domains that exist only in Registry V2 are not served yet.
  • The address has a sub domain, such as blog-example.xlm.sh or blog.example.xlm.sh. Only top-level names are served.
  • The account has no xlm.sh record. Set one up with How to set up a site.
  • The page does not exist in the site's content. The domain works, but the path is not in the site's files. Sites that route in the browser (single-page apps) show this on deep links or refresh; use hash routing (/#/about) or generate one HTML file per page.

451: This site has been blocked ​

The site or its content was blocked following a report of abuse or illegal content, under the Terms. It is still on IPFS and Stellar; only xlm.sh no longer serves it.

If you own the site and believe this is a mistake, write to [email protected] with the site name.

501: This kind of site is not supported ​

The domain points to a contract address (C...). xlm.sh only serves domains that point to a Stellar account (G...), because the record is stored in the account's data entries. Point the domain to an account in Soroban Domains and set the record there.

502 or 503: The site could not be loaded ​

  • 503, a Stellar lookup failed. The Stellar RPC servers did not answer. This is usually brief; try again in a minute.
  • 503, a DNSLink problem. The record points to a domain whose _dnslink TXT record is missing, or has more than one record of the same kind (/ipfs/ or /ipns/). Fix the TXT record.
  • 502, the content could not be fetched. No IPFS node that xlm.sh can reach has the content, or it took too long. Make sure the CID is pinned on a node that is online, for example with your pinning service.

The site is slow the first time ​

The first visit after you publish a new CID has to find and fetch the content across the IPFS network. Once it has been visited, xlm.sh keeps a copy on its own nodes, so later visits are fast. Large sites take longer.

My change does not show up ​

  • xlm.sh caches the domain and the record for 30 seconds, and pages may be cached for another 60 seconds by your browser and Cloudflare. Allow about two minutes.

  • IPNS and DNSLink updates can take longer: an IPNS record is cached by IPFS nodes for its TTL, and a TXT record by DNS resolvers for its TTL.

  • Check which CID is being served:

    shell
    curl -sI https://example.xlm.sh/ | grep -i x-ipfs-roots

Something else ​

Write to [email protected] with the address you opened and what you saw.