Improved CLI Error Handling Update

Improved CLI Error Handling Update

Let’s walk you through the latest enhancements we’ve made, specifically in our error management, leveraging events to manage domain states, and our new private IPFS gateway.

These improvements are designed to make your SDK, CLI, and incoming UI experience even smoother and more secure. Let’s dive right in!


Enhanced Error Management

We’ve made some improvements to how we manage errors across our services. Previously, when users encountered an error (like linking an already utilized Domain), they would receive a traditional error stack trace. This wasn’t the most user-friendly approach and often required extra work for users to understand and address the issue.

Now, our error-handling system is much more efficient and digestible, propagating error messaging across the CLI, SDK, and soon-to-come UI:


Domain States and Events

We’re expanding domain statuses on our platform from our verified/not verified state to a more specific list, giving users a clearer look at a domain’s lifecycle as they link it to their sites on Fleek.

We’re leveraging our event-driven architecture to enhance how we update domains and the states they go through in their lifecycle! Previously, domains were only verified as true or false upon connection. Now, domains travel through a set of events with possible states upon creation. The updated domain events include:

These events are handled asynchronously for a more efficient and reliable process. For more information on events, check out the Fleek Leak blog post about our event-driven architecture!


New Private IPFS Gateway

We’ve also launched a new and improved IPFS gateway that brings better performance in obtaining data and increased security.

The reason?

Before, our IPFS gateways to preview raw IPFS sites and storage were publicly accessible to any (browsers, users, and crawlers alike) which meant any content, malicious or not, could be exposed. This affected Fleek’s gateway’s domain reputation and exposing users to potential phishing content.

Now, gateways are hidden from the general public and will only serve the purpose of allowing users to map a custom domain on top of them to access their site’s raw IPFS preview from a personalized private gateway endpoint. This separates the scope and responsibility for the content to each user and ensures proper usage. For specifics on the changes we’re making to improve security against phishing effects, check out our most recent blog!


Other Fixes and Improvements


For more resources and updates, visit our LinkTree.