Port 3000 not working
I've tried at least half a dozen pods today, but none of them ever get port 3000 active on the container. Container is "ready" and no error showing in the log. This is for the FaceFusion community template, which was working fine yesterday.
17 Replies
Which region is it?
Central United States; same location I've been using with no problems for months.
8888, 7777, and 2999 all open as expected
If you try with a new setup will it work? With no network storage maybe?
No logs? Try checking the files, maybe the log for port 3000 is written into a file.log OR. TXT file
Use jupyter or the web terminal to find it
Log says "All services have been started" and "Container is READY!"
I've tied multiple different instances with different processors.
Template worked fine for months. Has anything changed on RunPod since 1/1/25?
Tried template for RunPod Stable Diffusion and port 8888 and 3001 work as expected.
I'm not sure if anything has changed since then but try running it manually first
Get into the worker, use a web terminal and run the app
Is there documentation or a how-to that would explain how to get into the worker, use a web terminal and run the app? I have not done that before.
Then press connect button then click on the web terminal button
Then run the app using the command for your app specifically, I'm not sure which
I can try running the template later, if you want send me a link
I appreciate the help. When you have time to test it the template ID is https://www.runpod.io/console/explore/igmp89t53m
Hmm yeah it says port isnt ready yet, since when is this
i think this might not be maintained anymore
i'd suggest using other alternatives first like on a1111 extensions or comfyui maybe
ok, thx, i was able to get a hugging space template set up.
Hi,
What does that mean please?
I have been facing the same issue with only Facefusion. I tried other templates - Forge, oobaboga et al. They worked fine. I noticed that it's only Facefusion that has the problem no matter which machine you use.
Hi @nerdylive - is there a chance you could take another look at the issues with https://www.runpod.io/console/explore/igmp89t53m not opening the interface on port 3000? The other templates I've tried are not as fast or easy, so I'd like to use this if possible. Or, since the other ports open as expected, is there a way to access the UI on another port? Thanks
Not now, probably remind me in like one more week
If the face fusion is maintained, then I might be able to make a new template for it
Or perhaps find some alternative for it
Hi There, checking back in to see if you have time to check on this issue to fix the template for port 3000 with version 2.6 of the app. Or if you know of a way to get the UI working using another port. Thanks
The problem there i think is its because the appisnt running
havent checked deep yet, do you know any other repo that works? or any other sources that works
When you open the template in a container everything looks like it is running, it's just that port 3000 never opens. After it installs the app all the ports say "ready" and web terminal says "running", and the workspace is available in 7777 and 8888. Just seems like a problem accessing port 3000. I'm not experienced enough to know how, but it seems like there might be a way connect via web terminal or get the gradio UI to run thought the workspace.
the port 3000 never opens because the app isn't running inside the container
the other apps on port 7777, 8888 works fine