-
Notifications
You must be signed in to change notification settings - Fork 4
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
Running into issue port already in use #1
Comments
When does this happen ? from a fresh startup ? Can you find out what is running on that port ? |
I have the same issue from a fresh startup. Application deployment failed at 2017-10-26T05:58:56Z with exit status 1 and error: Hook /opt/elasticbeanstalk/hooks/appdeploy/post/99_restart_delayed_job.sh failed. Stopping nginx: [ OK ] Then I check the 80 port on that instance as follow. |
Seems like nginx was already running ? are you using the setup below ? |
Yes, nginx was already running. |
Hi @Gary-Pan @JungleCatSW @dzincone , |
For anyone reading this there is an issue with nginx-setup-config. It works when you first deploy, but if you modify setup or redeploy it gives errors. I think this is due to the folder move commands at the bottom of the file. |
Ah I see, thanks @JungleCatSW! Sorry... just one more question. I'm getting the following error: Error during WebSocket handshake: Unexpected response code: 400. This must be something to do with the nginx config? Why might this be? Thanks!! |
@willmoss1000 Hi if you are still getting this can you start another issue on here and paste in the full error and where the error log came from. Cheers! |
Thanks @JungleCatSW! So like the others I'm running into this error: /var/log/nginx/error.log Even if I fix it with sudo fuser -k 80/tcp I get an error saying that proxy isn't working. I'm pretty sure I've followed your steps exactly. What do can I do to prevent this error on startup? Cheers! |
@willmoss1000 ill take a look and get back to you |
@willmoss1000 the 400 error is different to the port in use error though right ? Do you know how to get the full logs from ELB ? |
@JungleCatSW Sorry for the delay in going back. I'm using a classic load balancer as this script doesn't work currently. Yep, tried on a fresh install and kept getting 2018/03/27 11:59:13 [emerg] 4828#0: bind() to 0.0.0.0:80 failed (98: Address already in use). Does it work for you?? Would be great if I could get it working as an application load balancer! Cheers |
INFO: Docker container 1f741df9d2b7 is running aws_beanstalk/current-app.
ERROR: [Instance: i-0cccb2bac7313d483] Command failed on instance. Return code: 1 Output: (TRUNCATED)...[emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
[FAILED].
This happens from editing the file and running the bash script for redirects. Any idea on how to fix that?
The text was updated successfully, but these errors were encountered: