> For the complete documentation index, see [llms.txt](https://quicly.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quicly.gitbook.io/help/faq/common-errors-and-fixes.md).

# Common Errors & Fixes

## **Navigating Common URL Conversion Errors**

During the URL shortening process, certain issues may arise, leading to error messages. Below, we've outlined common errors and provided explanations to help you troubleshoot and resolve these issues efficiently

<figure><img src="/files/iU2LbjdQnEgTU4CW0rVc" alt=""><figcaption><p>img 1 - Common errors in url conversion</p></figcaption></figure>

### <mark style="color:purple;">**1. Long URL Issues:**</mark>&#x20;

Errors associated with the long URL may occur due to various reasons:

* **Missing Protocol**: Ensure the URL begins with ‘http\://’ or ‘https\://’.
* **Prohibited Content**: The link must not include blacklisted domain keywords associated with explicit content, gambling, or substances (e.g., sex, gambling, porn, xxx, drugs, alcohol, cannabis).
* **Invalid Domain Ending**: The domain must conclude with a valid ending, such as '.com' or '.net'.
* **Invalid Characters**: Ensure the URL does not contain any invalid or unsupported characters.

### <mark style="color:purple;">**2. Alias Errors:**</mark>

The custom alias field also has specific requirements:

* **No Spaces Allowed**: Ensure there are no spaces within the alias.
* **Character Restrictions**: Use only alphanumeric characters (0-9, a-z, A-Z), hyphens (-), or underscores (\_).
* **Character Limit**: The alias must be between 7 and 20 characters in length.
* **Unique Alias**: The alias must not be already in use.

### <mark style="color:purple;">**3. UTM Builder Notes:**</mark>

While UTM parameters are optional, if you choose to provide one of the main parameters (utm\_campaign, utm\_source, or utm\_medium), all other main parameters are required for a comprehensive tracking setup. The ‘utm\_term’ and ‘utm\_content’ parameters remain optional.

<figure><img src="/files/GWvABLJmwHtJnj7jaV9j" alt=""><figcaption><p>img 2 - UTM Builder errors</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://quicly.gitbook.io/help/faq/common-errors-and-fixes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.