-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access the WebUI #26
Comments
Add --listen to start.sh
|
Thanks for the reply! If i add --listen, where do i find the full url for the webui to access it? Since the script only exports api routes on a serverless instance 🤔 |
Any ideas? @brgrp |
Hi @crax0 , I am stuck with the same issue, were you able to find a way to access the webui after adding the --listen parameter? Thanks! |
Unfortunately not 👎🏼 |
Ah, I see, why would you want to get web interface access for a serverless instance? You can also use the docker image on a pod instance and that should work as suggested. |
🎉 This issue has been resolved in version 2.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
@crax0 @brgrp @maxabrahamsson we added this directly into the worker: Access ComfyUI via WebUI. |
Is your feature request related to a problem? Please describe.
Im trying to access the WebUI somehow..
Describe the solution you'd like
Im already building my own image from the dev brach and can connect the network storage for my own models but is there any way to access the WebUi of the running serverless instance? Maybe someone could tell me what i have to do to access it. Expose the port 8188 in the Dockerfile and map it in runpod?
The text was updated successfully, but these errors were encountered: