Skip to main content
← All guides

Fix Angular ng serve “Blocked request. This host is not allowed”

Why qURL here

Keep the app private on your machine and invite the people you choose by email: each verifies their address and saves a passkey, with no account needed, and comes back until you revoke them. One .qurl.site entry in angular.json covers everyone you let in, with pages and hot reload coming through. For a quick look, send a one-time qURL™ link instead.

See how LayerV compares to ngrok →

Steps

Angular’s Vite-based ng serve blocks unknown hosts. Add the tunnel domain, such as .qurl.site, to allowedHosts in the serve target’s angular.json options, then restart. The boolean --allowed-hosts flag turns the check off; avoid it. With qURL, share the running ng serve app through single-use links that expire on their own, with no public URL.

  1. Read the host from the error

    The page answers 403 and says: “Blocked request. This host ("c-k3j2ab.qurl.site") is not allowed. To allow this host, add it to allowedHosts under the serve target in angular.json.” It suggests that exact host. Allow the tool’s domain instead, so the next link works too.

  2. Add the tool’s domain to allowedHosts in angular.json

    The option sits under projects.<your-app>.architect.serve.options. A leading dot allows the domain and every subdomain: .qurl.site for qURL, your exact dev domain for ngrok (your-domain.ngrok-free.app), .trycloudflare.com for a Cloudflare Quick Tunnel.

    "serve": {
      "builder": "@angular/build:dev-server",
      "options": {
        "allowedHosts": [".qurl.site"]
      }
    }
  3. Restart ng serve on 127.0.0.1, then share it

    ng serve reads angular.json only at start-up, so restart it after editing. With no --host it can listen only on the IPv6 address [::1], depending on localhost resolution, while qurl publish connects to 127.0.0.1, so start it with --host 127.0.0.1. Each qurl share link opens once and expires within 24 hours.

    ng serve --host 127.0.0.1
    qurl publish http://127.0.0.1:4200
    qurl share <CRID>

What the recipient sees

With the domain allowed, the page loads through the link and hot reload connects.

Troubleshooting

Troubleshooting
If you seeDo this
Still “Blocked request” after editing angular.jsonRestart ng serve: it reads angular.json only at start-up. Check you edited the serve target of the project you are running.
--allowed-hosts on the command line lets every host inIn Angular CLI 22 the flag is a yes-or-no switch that turns the host check off; it takes no list. Remove it and list the domains in angular.json.
Show 6 more fixes
More troubleshooting
If you seeDo this
qurl publish says the local app is not accepting TCP connectionsStart the app first and check that curl works on the same address. qurl publish connects to localhost as 127.0.0.1, so if your app listens only on IPv6 (on macOS or Linux, lsof -iTCP -sTCP:LISTEN -nP shows [::1]), publish 'http://[::1]:PORT' instead, or start the dev server with --host 127.0.0.1 and publish that address. Neither requires listening on your LAN. Keep the quotes: zsh treats the brackets as a pattern.
The recipient sees “Access link invalid”The link was already used or has expired. Run qurl share again and send the new link.
The recipient sees “Resource not found”The resource was deleted after the link was made. Publish the app again, then run qurl share and send the new link.
publish rejects http://127.0.0.1 with “only HTTPS URLs are allowed”, asks you to log in, or prints no Access: lineYour qURL CLI is out of date. On macOS run brew update, then brew upgrade qurl; elsewhere install the latest release. After updating, qurl --version prints 3.4.1 or later, and every publish is private by default.
publish says this Linux session “can’t reach a systemd user manager”You are in a container or sandbox without a user service manager. Run qurl publish with --foreground; sharing lasts as long as that process runs. Container and CI setup →
publish says “Quota Exceeded” with “protected resource limit reached”, or “Your qURL account has reached a plan limit”You can see this without an account: a device with no account can keep up to 3 active resources, with links that last up to 24 hours. Run qurl list --status active, then qurl delete <CRID> for any you no longer need (it asks you to confirm; --yes skips that). qurl stop keeps the resource, so it does not free a slot.

Frequently Asked Questions

Which Angular versions have allowedHosts?

The option first appears in the published @angular/build 19.1.5 and 18.2.14, released with the Vite versions that added the host check. Earlier releases have no allowedHosts option on the dev server.

Why not use --allowed-hosts?

Because it allows every host. Vite’s docs warn that allowing all hosts lets any website send requests to your dev server through DNS rebinding and download your source code. List the domains you need in angular.json.

Which domain do I add for qURL?

.qurl.site. A qURL link opens the app on a qurl.site subdomain, and the leading dot covers every one of them.

Who else can reach my app while the link is open?

Opening the link starts a session for that browser, which lasts 1 hour by default. After a browser opens it, another browser on the same public IP cannot use its access. A script or agent that opens the link without a browser is admitted by its network address instead, which other devices on that public IP share until the session ends. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues. Keep your app’s own sign-in for anything sensitive.

Publish your app now

Install the CLI, then run one command. No sign-up, no API key.

Install the CLI →

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.