Question

Rebooted droplet, virtual host not being reconized

Posted July 30, 2014 4.2k views

Hi there, I had a ruby on rails application running just fine on my droplet, rebooted the server with a reboot now command (in console), and now that it’s back up. It’s going to This file is located in /home/rails/app/views/home/index.html.erb, and not the virtual host path. Any help would please be apprecitated… and fast. Thanks

Add a comment
bob182605
By:
bob182605
Add a comment
2 comments
  • bob182605 July 30, 2014
    Reply Report

    nothing has changed in my apache config that was working. My site is at /var/www/sites/yadayada

    Here’s what I get when I restart the service

    apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
    apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
    (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
    no listening sockets available, shutting down
    Unable to open logs
    Action ‘start’ failed.
    The Apache error log may have more information.

  • kamaln7 July 30, 2014
    Reply Report

    That means there is something listening on port 80. You can find out what program is using the port by running:

    sudo netstat -plutn | grep 80

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers
bob182605 July 30, 2014

Was just looking at there, here’s what’s running

tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 833/unicorn.conf -E
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 776/nginx: worker p

I stopped apache and tried to restart, now I get this

apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80

Reply Report
bob182605 July 31, 2014

Andrew’s response was right in my ordeal, but Kamal helped me see what was going on initially.

For those of you who get this in the future. What append was, after I rebooted the droplet, the service nginx (in my case) took over port 80, which is my default port for apache. I’ve seen posting about killing whatever service on that port to kick out whatever took your port # or to config a new port # for your vitual hosts. All it took in my case, was stopping the nginx service, and then starting up apache. BOOB… DONE. Thanks for your help everybody.

Reply Report
henry.wu February 24, 2015

This is awesome.

Basically digitalocean automigrated my droplet when they upgraded it. All my sites suddenly had the ‘Welcome to Nginx’ default message. Wtf....

Anyways, after an hour of googling and experimenting, I came upon this thread which solved everything.

My question is, why does auto-migrating a droplet make Nginx the default webserver listening on port 80???? Thats a serious fail on digitaloceans part, no?

Reply Report

Looking for something else?

Ask a new question Search for more help