ComfyUI idle to running red box issue
So I’ve installed a workflow in runpod and I install all the nodes and I have it working. However when I go to switch the runpod to idle and then switch it back to running it gives me red box errors and if I try to either fix them or uninstall and then reinstall they stay broken. Is there anyway to fix this?
Node packs that break are impact, WAS, sipherxyz comfyui-art-venture
15 Replies
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
In comfyui if you don’t have node packs installed then they are red boxes and you need to use the comfyui manager to install or use a git URL.
I can get the comfyUI workflow working in runpod. But when I stop the run runpod from running and then start it running again I get red boxes from some of the nodes and I can’t find a way to fix them and it reminds broken.
Use network storage on your endpoint and use a pod to fix the broken nodes
Otherwise your custom nodes will always have issues when your endpoint has a cold start.
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Ok I thought it might be a network storage thing. The documentation on network storage is confusing to me. So can I just choose a low gpu and high storage for the network volume and the pods can jsut pull from that right? There isn't any documentation that I can find on how a pod pulls from network storage. Any suggestions?
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Ok that makes sense I'll have to play with it thank you for the help and the quick reponse!
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
So while I would agree this would normally work I constantly get the error that if I try and load a new pod even with using a network volume there are nodes that are always broken whether I try I fix and or completely uninstall and reinstall. Those node packs are Impact, WAS, and comfyui-art-venture. And while I would try and fix them via a GIT url the securtiy level isn't configured correctly. I assume this is because of the network storage that I'm getting this issue. I don't with a normal pod not connect to network storage.
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
2024-06-27T15:17:24.742978048Z ERROR: To use this feature, you must set '--listen' to a local IP and set the security level to 'middle' or 'weak'. Please contact the administrator.
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
the logs from runpod
Did you manage to solve the problem? I am having the same problem.
Unknown User•16mo ago
Message Not Public
Sign In & Join Server To View