解决nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)

本文介绍了在Ubuntu 10.04上安装Nginx后遇到的端口冲突问题及解决方法。通过修改配置文件中的监听选项,避免IPv4和IPv6对同一端口的重复绑定。

首选是安装nginx,在./configure出错的情况下,查看错误的报告,如果是缺少一些必要的库,安装这些库,可能的有ssl pcre(这个库我是使用源码安装的,在线安装没有成功,提示看不到这个库)等 ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/ 这个是这个库的连接。下载源码然后安装即可!

然后make

make install

如果使用的是源码安装,安装后的目录在/usr/local/nginx.其中有所有的东西,源码安装的启动方式:sbin/nginx,这个程序在/usr/local/nginx

如果是在线安装,安装后的缺省目录在/etc/init.d/nginx start

如果在安装过程在浏览器中查找尝试!!

在ubuntu10.04上面安装nginx,安装完成之后尝试启动nginx,使用命令:

sudo /etc/init.d/nginx start

结果提示错误:

hankcs@ubuntu:~$ sudo /etc/init.d/nginx start
[sudo] password for hankcs:
 * Starting nginx nginx                                                         nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()

我看了一下端口占用情况,并且尝试杀了进程:

hankcs@ubuntu:~$ netstat -ntpl
(并非所有进程都能被检测到,所有非本用户的进程信息将不会显示,如果想看到所有信息,则必须切换到 root 用户)
激活Internet连接 (仅服务器)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      -              
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      -              
hankcs@ubuntu:~$ killall -9 nginx
nginx:没有发现操作

遇到这种问题我先用中文搜索了一下答案,发现大家都在装逼地说要杀nginx重复的进程。我试了下发现是扯淡,于是看了谷歌搜到的第一个英文页面,老外说是nginx先监听了ipv4的80端口之后又监听了ipv6的80端口,于是就重复占用了。更加坑人的是你去看了端口占用它又把80端口释放了,是不是很囧。

解决方案是编辑nginx的配置文件

hankcs@ubuntu:~$ sudo gedit /etc/nginx/sites-available/default

修改这一段:

listen 80;
listen [::]:80 default_server;

listen 80;
listen [::]:80 ipv6only=on default_server;

然后启动nginx,完美解决!

还有一种可能的情况就是,如果你是在虚拟机中安装了nginx,那么在虚拟机中的firefox可能就是不能连接,但是在宿主机中的浏览器可以连接(前提是宿主机和虚拟机是可以相通的!!!)

/usr/local/nginx/sbin# ./nginx nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 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 [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:8066 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 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 [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:8066 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 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 [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:8066 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 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 [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:8066 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 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 [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:8066 failed (98: Address already in use) nginx: [emerg] still could not bind() 重启nginx
08-01
该错误表明 Nginx 在尝试绑定到端口 80、443 或 8066 时失败,原因是这些端口已经被其他进程占用。通常,这种情况发生在系统中已有服务正在监听这些端口,导致 Nginx 无法绑定[^1]。 ### 常见原因及解决方法 1. **检查占用端口的进程** 可以使用 `netstat` 或 `lsof` 命令查找占用端口的进程。例如,检查 80 端口的占用情况: ```bash sudo netstat -tulnp | grep :80 ``` 或者: ```bash sudo lsof -i :80 ``` 如果发现其他服务(如 Apache、另一个 Nginx 实例或其他 Web 服务器)占用了这些端口,则可以停止这些服务或更改其配置以释放端口。 2. **停止占用端口的服务** 如果发现是其他服务占用了端口,可以使用以下命令停止服务。例如,停止 Apache: ```bash sudo systemctl stop apache2 ``` 或者,如果另一个 Nginx 实例正在运行: ```bash sudo nginx -s stop ``` 之后重新尝试启动 Nginx。 3. **更改 Nginx 监听端口** 如果无法释放端口,可以修改 Nginx 的配置文件(通常位于 `/etc/nginx/nginx.conf` 或 `/etc/nginx/sites-available/default`),将监听端口更改为未被占用的端口。例如: ```nginx server { listen 8080; server_name example.com; ... } ``` 保存更改后重新加载 Nginx 配置: ```bash sudo nginx -s reload ``` 4. **检查 Docker 容器端口冲突** 如果在 Docker 环境中运行 Nginx,确保宿主机端口未被占用。可以使用以下命令查看当前运行的容器及其端口映射: ```bash docker ps ``` 如果发现冲突,可以更改 Docker 容器的端口映射,例如: ```bash docker run -p 8080:80 nginx ``` 5. **检查 SELinux 或防火墙设置** 在某些情况下,SELinux 或防火墙规则可能会阻止 Nginx 绑定到特定端口。可以临时禁用 SELinux 或调整防火墙规则以排除此类问题。 6. **重启系统** 如果无法确定哪个进程占用了端口,可以尝试重启系统以释放所有端口并重新启动服务。 ### 总结 端口绑定失败通常是因为端口已被占用。通过检查占用端口的进程、停止冲突服务或更改配置,通常可以解决此问题。对于 Docker 环境,确保宿主机端口未被占用,并根据需要调整端口映射。 ---
评论 4
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值