[BUG]: …Error with Jupiter in the official ComfortUI template

[evaluxara-lang]

Describe the bug
JupyterLab port 8888 disappears from RunPod UI after pod Stop/Start cycle, making it inaccessible through the web interface.

Repro MVP (Minimal Viable Procedure)

1. Create a new pod using the official ComfyUI template (latest version)
2. Verify that all 3 ports are working: 8080 (FileBrowser), 8188 (ComfyUI), 8888 (JupyterLab)
3. Stop the pod (either manually with "Stop" button or automatically when GPU becomes unavailable)
4. Start the pod again (either manually or automatically when GPU becomes available)
5. Port 8888 (JupyterLab) is no longer visible in the RunPod UI "HTTP Services" section
6. Ports 8080 and 8188 continue working normally

Expected behavior
After stopping and restarting the pod, all three HTTP ports (8080, 8188, 8888) should remain visible and accessible in the RunPod UI.

Actual behavior

• Port 8888 disappears from the HTTP Services panel
• JupyterLab is still running internally (verified with netstat -tuln | grep 8888 and jupyter lab list)
• Attempting to access the URL manually results in connection errors
• The only workaround is manually restarting jupyter from the web terminal

Workaround

pkill -f jupyter
jupyter lab --allow-root --no-browser --port=8888 --ip=0.0.0.0 --ServerApp.allow_origin='*' > /tmp/jupyter.log 2>&1 &

Screenshots

Versions (please complete the following information):

• Template: Official RunPod ComfyUI template (latest)
• Pod ID: wgenifr3985iv5
• Region: EU-RO-1
• GPU: NVIDIA RTX 4000 Ada Generation

Additional context
This issue particularly affects users without persistent storage volumes, as they lose easy access to JupyterLab after every pod restart. The bug has been persistent for some time and occurs reliably with every Stop/Start cycle.

The issue seems to occur specifically when:

• Pod stops due to GPU unavailability (switching to CPU-only mode)
• Pod is manually stopped and restarted
• In both cases, the HTTP proxy/port mapping for 8888 fails to re-register with RunPod's interface

Thank you for looking into this issue.