# Cloudflare Pages Frontend 1. Click `Compute (Workers)` -> `Workers & Pages` -> `Create` ![create pages](/ui_install/worker_home.png) 2. Select `Pages`, choose `Use direct upload` ![pages](/ui_install/pages.png) 3. Enter the deployed worker address. It must be the backend API root URL, start with `https://`, and must not include a trailing `/`. Click generate, and if successful, a download button will appear. You will get a zip package. - The worker domain here is the backend API domain. For example, if I deployed at `https://temp-email-api.awsl.uk`, then fill in `https://temp-email-api.awsl.uk` - If your domain is `https://temp-email-api.xxx.workers.dev`, then fill in `https://temp-email-api.xxx.workers.dev` - Do not enter your frontend `Pages` domain, and do not include paths like `/admin` or `/api`. Otherwise frontend requests will hit the wrong address and you may see `Cannot read properties of undefined (reading 'map')` or `405 Method Not Allowed` - Before filling it in, open `https://your-worker-domain/open_api/settings` in the browser and confirm it returns JSON. If it returns HTML, 404, 405, or a Cloudflare challenge page, fix the Worker binding, variables, or security policy first > [!warning] Note > The `worker.dev` domain is not accessible in China, please use a custom domain. > > Do not enable security policies such as Under Attack, Bot Fight, or Managed Challenge on the backend API domain. Frontend XHR requests cannot complete those browser challenges, and the common symptom is `Network Error`.
{{ tip }}

Example: `https://temp-email-api.example.com`. Do not enter the frontend Pages domain and do not add a trailing `/`.

{{ errorMessage }}

> [!NOTE] > You can also deploy manually. Download the zip from here: [frontend.zip](https://github.com/dreamhunter2333/cloudflare_temp_email/releases/latest/download/frontend.zip) > > Modify the index-xxx.js file in the archive, where xx is a random string > > Search for `https://temp-email-api.xxx.xxx` and replace it with your worker's backend API root URL, then deploy the new zip file. If you replace it with the frontend Pages domain, common symptoms are the `map` error or `405` responses from API requests > > If you entered the wrong address the first time and still see errors after redeploying, test in an incognito window or clear browser cache so the browser stops using the old frontend assets. 4. Select `Pages`, click `Create Pages`, modify the name, upload the downloaded zip package > [!warning] Important: SPA Mode > This project is a Single-Page Application (SPA). **You must expand the advanced options during deployment and set "Not Found handling" to `Single-page application (SPA)`**. > Otherwise, refreshing the page or directly accessing sub-paths like `/admin` will return a 404 error. > > ![pages spa setting](/ui_install/pages-spa-setting.jpg) Then click `Deploy` ![pages1](/ui_install/pages-1.png) 5. Open the `Pages` you just deployed, click `Custom Domain`. Here you can add your own domain, or you can use the automatically generated `*.pages.dev` domain. If you can open the domain, the deployment is successful. ![pages domain](/ui_install/pages-domain.png)