w-e-w
commented
3 weeks ago I don't know what you're doing and what's on your instance and I practically zero concept of how to use EC2
but if the issue is simply those parts are occupied by other instances other services then call obvious reasons it will not work
by default webui use the default pors range set by gradio whitch is 7860
it will try up to 100 subsequent ports if the port is not available
this behavior can be configured by using
the is control by environment GRADIO_SERVER_PORT=7860 and GRADIO_NUM_PORTS=100
GRADIO_SERVER_PORT the starting port, GRADIO_NUM_PORTS the number of subsequent ports to try if unavailable
which givs you a port range of 7860~7960
another way of specifying a different port is to use the--port launch command line arg
see wiki https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Command-Line-Arguments-and-Settings
note then --port will only use the specified port and will not try subsequent ports
if you wish it to use a range port then it must use the environment variables
Checklist
What happened?
When I deploy source on a normal ec2, when starting ec2, it does not have this error. But when I deploy source on an ec2 in auto scaling group, it will have this error.
Steps to reproduce the problem
What should have happened?
SD should start successfully instead of port error and SD will restart
What browsers do you use to access the UI ?
No response
Sysinfo
I use ec2 with instance type g6e.xlarge
Console logs
Additional information
No response