citizen_y Posted April 1 Share Posted April 1 (edited) Hello, I am currently using Unraid Version 6.12.9. Whenever my Unraid server boots I'm getting repeated errors from nginx failing to bind to ports 80 and 443 due to error "98: Address already in use". I have pasted the logs below (though I have removed my internal network IPs and hostname). Is this expected behavior? if not, I'm fairly confident the fix is something straight forward and obvious that I am just missing - but would appreciate any help. Thanks Apr 1 16:53:29 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:80 failed (98: Address already in use) Apr 1 16:53:29 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:80 failed (98: Address already in use) Apr 1 16:53:29 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:80 failed (98: Address already in use) Apr 1 16:53:29 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:443 failed (98: Address already in use) Apr 1 16:53:29 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:443 failed (98: Address already in use) Apr 1 16:53:29 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:443 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:80 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:80 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:80 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:443 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:443 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:443 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:80 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:80 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:80 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:443 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:443 failed (98: Address already in use) Apr 1 16:53:30 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:443 failed (98: Address already in use) Apr 1 16:53:31 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:80 failed (98: Address already in use) Apr 1 16:53:31 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:80 failed (98: Address already in use) Apr 1 16:53:31 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:80 failed (98: Address already in use) Apr 1 16:53:31 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to 127.0.0.1:443 failed (98: Address already in use) Apr 1 16:53:31 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_1]:443 failed (98: Address already in use) Apr 1 16:53:31 [MY_HOSTNAME] nginx: 2024/04/01 16:53:24 [emerg] 7599#7599: bind() to [MY_INTERNAL_IP_ADDRESS_2]:443 failed (98: Address already in use) Edited May 10 by citizen_y Quote Link to comment
Solution bmartino1 Posted April 2 Solution Share Posted April 2 you most likely have a docker or other application set to auto start and that docker is replacing or claiming port 80 of the host. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.