Comfy-Org/ComfyUI_frontend

[Bug]: user.css fetched from default user when Comfy started with --multi-user

Open

#4,978 opened on Aug 14, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)TypeScript (610 forks)github user discovery
area:customizationhelp wantedverified bug

Repository metrics

Stars
 (1,838 stars)
PR merge metrics
 (Avg merge 4d 21h) (881 merged PRs in 30d)

Description

Prerequisites

  • I am running the latest version of ComfyUI
  • I have searched existing issues to make sure this isn't a duplicate
  • I have tested with all custom nodes disabled (see how)

What happened?

When activating --multi-user in comfy, the front end still tries to fetch user.css from default user.

It should instead probably fetch the actual user one.

Steps to Reproduce

  1. start comfy with --mutli-user
  2. open comfy and setup your username
  3. check network logs and see the 404 on user.css
  4. add a default user with a 'user.css`
  5. reload
  6. notice the error is not there anymore

How is this affecting you?

Minor inconvenience

ComfyUI Frontend Version

1.24.4

Browser

Chrome/Chromium

Console Errors

GET http://localhost:8190/api/userdata/user.css net::ERR_ABORTED 404 (Not Found)

Logs

Additional Context

No response

┆Issue is synchronized with this Notion page by Unito

Contributor guide

Research direction
Investigate how the frontend fetches user.css. Look for the place where the URL is constructed (e.g., in a service or component that handles user data). Ensure that when multi user mode is active, the correct user's CSS is fetched instead of default.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75