Duboux
Verified User
- Joined
- Apr 20, 2007
- Messages
- 264
After we switched ip's apache didn't want to work anymore.
Generating this error:
The current machine had a working SSL-certificate installed.
Somehow the machines current ip is being stored in a conf file, and I guess during changing if ip's it doesn't change with.
After the conf file was updated, apache needed being rebuilded twice for it to work again.
At first, it looked like the same error in here: http://directadmin.com/forum/showthread.php?t=12232&highlight=443
But those netstat and other commands showed no information.
I'm not sure if it's the doing of custombuild, but before I'm going to use it again I would like to be sure, this won't happen in the future.
Since this only happened with the machine that was custombuilded towards apache2 and php5 before the change of ip.
Generating this error:
root@server customapache]# service httpd stop
Stopping httpd: [FAILED]
[root@server customapache]# service httpd start
Starting httpd: (98)Address already in use: make_sock: could not bind to address OLD-IP:443
no listening sockets available, shutting down
Unable to open logs
[FAILED]
The current machine had a working SSL-certificate installed.
Somehow the machines current ip is being stored in a conf file, and I guess during changing if ip's it doesn't change with.
After the conf file was updated, apache needed being rebuilded twice for it to work again.
At first, it looked like the same error in here: http://directadmin.com/forum/showthread.php?t=12232&highlight=443
But those netstat and other commands showed no information.
I'm not sure if it's the doing of custombuild, but before I'm going to use it again I would like to be sure, this won't happen in the future.
Since this only happened with the machine that was custombuilded towards apache2 and php5 before the change of ip.
Last edited: