Comfy-Org/desktop

Fork 0

mirror of https://github.com/Comfy-Org/desktop.git synced 2026-11-04 23:47:43 +00:00

[GH-ISSUE #1058] [Bug]: After updating a couple of days ago, remotely accessing via browser has a different ComfyUI version than the application #284

New issue

Closed

opened 2026-10-31 22:11:10 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-31 22:11:10 +00:00

Owner

Originally created by @ManOrMonster on GitHub (Mar 13, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1058

App Version

Application:

Remote:

Expected Behavior

When I connect to my ComfyUI instance remotely via URL:port, ComfyUI and Manager should be the same version. Frontend is the same version in both somehow (1.11.8)

Actual Behavior

Remote ComfyUI version is not getting updated? Are there two separate versions of ComfyUI in Desktop?
In the app, it's 0.3.26. Remotely, it's 0.3.23.
The Manager in the app is 3.30.4. Remotely it's 3.27.10.

Steps to Reproduce

Open up over the network, connect from a browser.

Debug Logs

Attached

Browser Logs

Available on request

Settings JSON

On request

main.log

Other

No response

┆Issue is synchronized with this Notion page by Unito

Originally created by @ManOrMonster on GitHub (Mar 13, 2025). Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1058 ### App Version Application: ![Image](https://github.com/user-attachments/assets/7855952e-1569-4a2a-86c9-73a224c460a0) Remote: ![Image](https://github.com/user-attachments/assets/e13fb3e8-bfa7-4562-a2ee-95e414c3eb87) ### Expected Behavior When I connect to my ComfyUI instance remotely via URL:port, ComfyUI and Manager should be the same version. Frontend is the same version in both somehow (1.11.8) ### Actual Behavior Remote ComfyUI version is not getting updated? Are there two separate versions of ComfyUI in Desktop? In the app, it's 0.3.26. Remotely, it's 0.3.23. The Manager in the app is 3.30.4. Remotely it's 3.27.10. ### Steps to Reproduce Open up over the network, connect from a browser. ### Debug Logs ```powershell Attached ``` ### Browser Logs Available on request ### Settings JSON On request [main.log](https://github.com/user-attachments/files/19232382/main.log) ### Other _No response_ ┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-1058-Bug-After-updating-a-couple-of-days-ago-remotely-accessing-via-browser-has-a-diffe-1b56d73d365081ecb721c1907c84451b) by [Unito](https://www.unito.io)

bsakaguchi

2026-10-31 22:11:10 +00:00

closed this issue
added the
expected
label

bsakaguchi commented

2026-10-31 22:11:10 +00:00

Author

Owner

@dosubot[bot] commented on GitHub (Mar 13, 2025):

@ManOrMonster Hello there! 👋 I'm here to help you with any bugs, questions, or contributions you have.

To address the issue of version discrepancies between the ComfyUI desktop application and the remote access via a browser, it's important to understand how updates are managed. The ComfyUI desktop app is designed to update automatically when new stable versions are released, and it does not support manual updates through the ComfyUI Manager ^[1].

The discrepancy you're experiencing might be due to the remote instance not being updated automatically. This could happen if the remote instance is not configured to sync updates in the same way as the desktop application. Ensure that the remote instance is set up to receive updates or manually update it to match the desktop version.

If the issue persists, you might want to check the configuration settings or scripts that handle the update process to ensure they are correctly set up for both local and remote instances.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

@dosubot[bot] commented on GitHub (Mar 13, 2025):  @ManOrMonster Hello there! 👋 I'm here to help you with any bugs, questions, or contributions you have.  To address the issue of version discrepancies between the ComfyUI desktop application and the remote access via a browser, it's important to understand how updates are managed. The ComfyUI desktop app is designed to update automatically when new stable versions are released, and it does not support manual updates through the ComfyUI Manager [[1]](https://github.com/Comfy-Org/desktop/issues/561). The discrepancy you're experiencing might be due to the remote instance not being updated automatically. This could happen if the remote instance is not configured to sync updates in the same way as the desktop application. Ensure that the remote instance is set up to receive updates or manually update it to match the desktop version. If the issue persists, you might want to check the configuration settings or scripts that handle the update process to ensure they are correctly set up for both local and remote instances.  *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/dffe389c-60ad-473a-9d56-9d47173f2251?feedback_type=other)

bsakaguchi commented

2026-10-31 22:11:10 +00:00

Author

Owner

@ManOrMonster commented on GitHub (Mar 13, 2025):

@dosu

This could happen if the remote instance is not configured to sync updates in the same way as the desktop application. Ensure that the remote instance is set up to receive updates or manually update it to match the desktop version.

Understood, but I didn't need to do this before until a recent Desktop update.

@ManOrMonster commented on GitHub (Mar 13, 2025): @dosu > This could happen if the remote instance is not configured to sync updates in the same way as the desktop application. Ensure that the remote instance is set up to receive updates or manually update it to match the desktop version. Understood, but I didn't need to do this before until a recent Desktop update.

bsakaguchi commented

2026-10-31 22:11:10 +00:00

Author

Owner

@dosubot[bot] commented on GitHub (Mar 13, 2025):

Could you provide more details about any changes or updates you made to the configuration or setup of your ComfyUI instance around the time of the recent Desktop update? Additionally, have you checked if there are any new settings or options in the latest version that might affect how updates are handled for remote instances?

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

@dosubot[bot] commented on GitHub (Mar 13, 2025):  Could you provide more details about any changes or updates you made to the configuration or setup of your ComfyUI instance around the time of the recent Desktop update? Additionally, have you checked if there are any new settings or options in the latest version that might affect how updates are handled for remote instances?  *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e417b24d-e937-4321-a204-d1b263e72b25?feedback_type=other)

bsakaguchi commented

2026-10-31 22:11:11 +00:00

Author

Owner

@ManOrMonster commented on GitHub (Mar 13, 2025):

So this is weird. I closed ComfyUI Desktop completely and the remote instance was still available. There was no indication of a second running instance (such as a terminal window). I had to go into Task Manager and force close Python. Bizarre.

Then after restarting Desktop, the remote insatnce was up-to-date. However, I was still having the same underlying issue as before, which I thought was caused by the version discrepancies. Rgthree's custom nodes were broken in my workflows remotely, but work in Desktop.

I closed the Desktop app again and the remote instance was still up and running. I had no idea that running remote meant having two instances running. So I force closed the remote instance again, force updated rgthree in the Manager in Desktop, then restarted Desktop. The nodes started working again. So this can only mean all custom nodes are duplicated across these two instances, and if the remote one is running, they don't get updated? And I see no way to close the remote instance without force closing Python from Task Manager.

Is this really how Desktop is designed to work? Or do I have some weird configuration doing this?

@ManOrMonster commented on GitHub (Mar 13, 2025): So this is weird. I closed ComfyUI Desktop completely and the remote instance was still available. There was no indication of a second running instance (such as a terminal window). I had to go into Task Manager and force close Python. Bizarre. Then after restarting Desktop, the remote insatnce was up-to-date. However, I was still having the same underlying issue as before, which I thought was caused by the version discrepancies. Rgthree's custom nodes were broken in my workflows remotely, but work in Desktop. I closed the Desktop app again and the remote instance was still up and running. **I had no idea that running remote meant having two instances running**. So I force closed the remote instance again, force updated rgthree in the Manager in Desktop, then restarted Desktop. The nodes started working again. So this can only mean all custom nodes are duplicated across these two instances, and if the remote one is running, they don't get updated? And I see no way to close the remote instance without force closing Python from Task Manager. Is this really how Desktop is designed to work? Or do I have some weird configuration doing this?

bsakaguchi commented

2026-10-31 22:11:11 +00:00

Author

Owner

@webfiltered commented on GitHub (Mar 13, 2025):

Using the desktop app as a server for remote connections is not actually the intended use of the desktop app. It's just not something we actively block.

It is possible that at some point in the future, we may look at implementing this properly.

The versions are different because the desktop app uses its own things. It isn't running two versions of server, but there are absolutely no guarantees about what will be different outside the app itself.

@webfiltered commented on GitHub (Mar 13, 2025): Using the desktop app as a server for remote connections is not actually the intended use of the desktop app. It's just not something we actively block. It is _possible_ that at some point in the future, we may look at implementing this properly. The versions are different because the desktop app uses its own things. It isn't running two versions of server, but there are absolutely no guarantees about what will be different outside the app itself.

bsakaguchi referenced this issue

2026-10-31 22:16:37 +00:00

[PR #284] [CLOSED] Sanity check if the double yarn install bug happens again #755

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Comfy-Org/desktop#284

No description provided.

Rows
Columns