Skip to main content
← All guides

Access ComfyUI remotely with a private link

Why qURL here

Let someone use your ComfyUI workflows on your own GPU while the server stays on localhost. The recipient can run workflows and custom nodes, so share only with people you trust and keep Manager restrictions enabled.

Steps

To access ComfyUI remotely with qURL™ by LayerV, keep it on 127.0.0.1:8188 with no --listen or --enable-cors-header. Set ComfyUI-Manager to security_level = strong, publish with qurl publish, and send a qurl share link. ComfyUI has no login; whoever opens the link gets a browser session. Keep the link private and end access when the work is done.

  1. Install the qURL CLI

    Install the qURL CLI. On macOS, install it with Homebrew. On Linux and Windows, download the package for your platform from the latest release; the CLI page lists each one. Nothing asks you to sign up.

    brew install layervai/tap/qurl
    qurl --version
  2. Start ComfyUI on localhost, with no extra flags

    ComfyUI listens on 127.0.0.1 port 8188 unless you pass --listen. Leave --listen off: with no value it binds 0.0.0.0 and ::, every IPv4 and IPv6 interface on the machine. Leave --enable-cors-header off too. qURL does not need it, and it replaces the check that refuses requests coming from other websites. If your launcher prints a different port, use that port in the publish step. Keep ComfyUI running, and use a second terminal for the qurl commands.

    python main.py   # listens on 127.0.0.1:8188
  3. Lock down ComfyUI-Manager for the session

    If ComfyUI-Manager is installed, it decides whether a caller is local from ComfyUI’s listen address, not from who is asking. ComfyUI listens on 127.0.0.1 here, so whoever uses the link gets the Manager features you get. Set security_level to strong in the [default] section of ComfyUI-Manager’s config.ini (the startup log prints its path), then restart ComfyUI. strong blocks installing, updating and uninstalling custom nodes, fixing nodes, snapshots and restarts. Keep allow_git_url_install and allow_pip_install at false, their default. Set the level back after the session.

    # ComfyUI-Manager config.ini
    [default]
    security_level = strong
  4. Publish ComfyUI

    Publish the app through qURL. The first publish creates this device’s identity, starts a background service that keeps serving after you close the terminal (while you stay logged in), and prints the app’s CRID, its stable ID. The Access row says who can open the app: a plain publish makes it private from qurl 3.4.1 on. qurl share turns the CRID into an access link, and the link is what you send.

    qurl publish http://127.0.0.1:8188
  5. Reload if ComfyUI rejects the first cross-site navigation

    ComfyUI versions affected by issue #16203 can reject the first navigation from another site. If the first page returns 403 and the server logs identify Sec-Fetch-Site: cross-site, try reloading the same page after the qURL session opens. If 403 persists, check the server logs or update ComfyUI; do not disable its origin checks.

  6. End the session

    Stop serving ComfyUI with qurl stop, and set ComfyUI-Manager’s security_level back to what it was. qurl delete removes the resource for good after asking you to confirm.

    qurl stop <CRID>
    qurl delete <CRID>

What the recipient sees

The recipient lands on the ComfyUI canvas at an address like https://r_….qurl.site/, with no sign-in, because ComfyUI has none.

More

They load or build a workflow and queue it. Progress and previews arrive over ComfyUI’s WebSocket, which a qURL link carries. Images are saved on your machine, in ComfyUI’s output folder, and shown to them in the page.

Troubleshooting

Troubleshooting
If you seeDo this
The recipient’s first page is blank and says 403 ForbiddenComfyUI refuses any request the browser marks Sec-Fetch-Site: cross-site, and a page reached from another site, including the qurl.link page, can arrive that way. Ask the recipient to try reloading the same page after the session opens. If ComfyUI still rejects it, check the request headers in its logs rather than disabling the origin check. ComfyUI issue #16203 tracks this, and pull request #16584 would let such navigations through.
You added --enable-cors-header to fix a 403Remove it. It accepts an exact origin, but only as the Access-Control-Allow-Origin value it sends, and it replaces ComfyUI’s origin check instead of adding to it, so the server stops refusing requests from other sites.
Show 7 more fixes
More troubleshooting
If you seeDo this
ComfyUI-Manager refuses to install or update nodesThat is security_level = strong doing its job while the link is live. Install what the workflow needs before you share, or set the level back after the session.
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

Can I use ComfyUI from my phone?

Yes. For ComfyUI remote access without --listen, open the qURL link in your phone’s browser. Keep ComfyUI running on your computer: the phone controls that instance and its GPU, while images remain in the computer’s output folder.

How long does a remote ComfyUI session last?

A qURL browser session lasts 1 hour by default. The command in this ComfyUI guide requests --session-duration 2h and --ttl 1h: the unused link expires within 1 hour, while an opened session can run for 2 hours. Check the actual expiry printed by the CLI. Keep the session short enough for the work.

Does ComfyUI have a login?

No. ComfyUI’s self-hosting docs say “The ComfyUI server has no authentication by default” and advise binding to a non-loopback address only on a network you trust, or behind a reverse proxy with authentication. With qURL, ComfyUI stays on loopback, and the link and its session decide who reaches it.

Is ComfyUI --listen 0.0.0.0 safe?

Starting ComfyUI with --listen puts it on every network the machine is on, with no login. In April 2026 Censys counted over 1,000 internet-exposed ComfyUI instances and described a campaign whose scanner, when ComfyUI-Manager is present, installs a vulnerable node package and then exploits it to mine cryptocurrency.

Do I need --enable-cors-header for qURL?

No. Requests from the ComfyUI page through a qURL link are same-origin in the browser, so the default check lets them through. The flag replaces that check rather than narrowing it.

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

Opening a qURL 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.

Does my computer have to stay on?

Yes. Your ComfyUI app runs on your machine. The machine and app must stay running and connected; the app is unavailable while the machine is asleep.

How do I stop sharing?

Run qurl stop <CRID> to pause serving the app, and qurl start <CRID> to resume it; a stopped app still counts toward your resource limit. qurl delete <CRID> removes the resource for good after asking you to confirm; its CRID can never be shared again.

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.