screen "It worked!"
screen "It worked!"
I've created recently a new droplet on my account in Digital Ocean, based on my previous droplet
and since then, I'm not be able to enter to most of my domains or sub domains that reside on it.
Instead of getting the normal home page, I'm getting a strange page that include at the top the text:
" It worked!"
and at the bottom is written:
"Powered by VESTA"
When asking the Digital Ocean support team what could be the reason for that, they said it is something
associated with the VESTA interface.
Could you please help me with that?
and since then, I'm not be able to enter to most of my domains or sub domains that reside on it.
Instead of getting the normal home page, I'm getting a strange page that include at the top the text:
" It worked!"
and at the bottom is written:
"Powered by VESTA"
When asking the Digital Ocean support team what could be the reason for that, they said it is something
associated with the VESTA interface.
Could you please help me with that?
Re: screen "It worked!"
Yes, but I'm not sure if I've updated all necessary files:
I went through all VESTA folders that reside on my new droplet in Digital Ocean and changed the old IP to the new one.
Do you know, just in case, what are the associated files that have to be updated?
And one more question:
Do I need to stop the apache server and start it again, in order for the changes to take place?
Thanks,
Ami
I went through all VESTA folders that reside on my new droplet in Digital Ocean and changed the old IP to the new one.
Do you know, just in case, what are the associated files that have to be updated?
And one more question:
Do I need to stop the apache server and start it again, in order for the changes to take place?
Thanks,
Ami
-
SCelik
Re: screen "It worked!"
Yes you have to restart Apache afer configuration changes.
Configuration files for Centos:
http://www.vestacp.com/docs/#config-log ... hel-centos
Configuration files for Debian/Ubuntu:
http://www.vestacp.com/docs/#config-log ... ian-ubuntu
Firs add your new IP to vesta from panel. Then delete old one. Rebuild dns for websites. After all check manually... (From config file locations.)
Configuration files for Centos:
http://www.vestacp.com/docs/#config-log ... hel-centos
Configuration files for Debian/Ubuntu:
http://www.vestacp.com/docs/#config-log ... ian-ubuntu
Firs add your new IP to vesta from panel. Then delete old one. Rebuild dns for websites. After all check manually... (From config file locations.)
Re: screen "It worked!"
Thank you very much for your detailed reply; I'm really appreciating your help.
Now, I'll go through all your guidelines and hope it will work.
As soon as I finish all tasks, or having any problem during the process, I'll let
you know.
Best regards,
Ami
Now, I'll go through all your guidelines and hope it will work.
As soon as I finish all tasks, or having any problem during the process, I'll let
you know.
Best regards,
Ami
Re: screen "It worked!"
Hi SCelic,
How are you today?
I've done what you suggested and change the IP through all files.
Now, when trying to bring up the apache server, I'm getting the
following error (see text between the dashed lines):
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
root@new-faze:~# sudo service apache2 start
[....] Starting web server: apache2apache2: Could not reliably determine the server's fully qualified domai n name, using 127.0.1.1 for ServerName
[Sun Oct 18 10:36:52 2015] [warn] NameVirtualHost 5.101.103.210:8080 has no VirtualHosts
[Sun Oct 18 10:36:52 2015] [warn] NameVirtualHost 5.101.103.210:80 has no VirtualHosts
(98)Address already in use: make_sock: could not bind to address 5.101.103.210:8080
no listening sockets available, shutting down
Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
failed!
root@new-faze:~#
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What should I do to resolve the problem?
Best regards,
Ami
P.S. The string 5.101.103.210, is the new IP that was allocated after creating the new droplet
How are you today?
I've done what you suggested and change the IP through all files.
Now, when trying to bring up the apache server, I'm getting the
following error (see text between the dashed lines):
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
root@new-faze:~# sudo service apache2 start
[....] Starting web server: apache2apache2: Could not reliably determine the server's fully qualified domai n name, using 127.0.1.1 for ServerName
[Sun Oct 18 10:36:52 2015] [warn] NameVirtualHost 5.101.103.210:8080 has no VirtualHosts
[Sun Oct 18 10:36:52 2015] [warn] NameVirtualHost 5.101.103.210:80 has no VirtualHosts
(98)Address already in use: make_sock: could not bind to address 5.101.103.210:8080
no listening sockets available, shutting down
Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
failed!
root@new-faze:~#
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What should I do to resolve the problem?
Best regards,
Ami
P.S. The string 5.101.103.210, is the new IP that was allocated after creating the new droplet
-
SCelik
Re: screen "It worked!"
You have to correct server hostname:
And this line is strange:
Code: Select all
# v-change-sys-hostname mail.yourdomain.comOne of your configuration files points a domain to 127.0.1.1 can you find which one?Starting web server: apache2apache2: Could not reliably determine the server's fully qualified domai n name, using 127.0.1.1 for ServerName
Re: screen "It worked!"
Thank you for your reply; I'm really appreciate your significant help.
Just to be on the safe side, could you please clear the following:
1. You said: "You have to correct server hostname":
1.1. How would I do it ? Is it by simply issuing the command "# v-change-sys-hostname mail.yourdomain.com" on the command line of ssh? or do it from VESTA control panel and if so, how should I do it?
1.2. Is "yourdomain" in the above command should be replace by my new droplet IP, or by the main domain associated with it,
or something else, or stay the same?
2. You said: "One of your configuration files points a domain to 127.0.1.1 can you find which one?" - How can I find it? Shall I use the "netstat -plant" command, or something else?
Best regards,
Ami
Just to be on the safe side, could you please clear the following:
1. You said: "You have to correct server hostname":
1.1. How would I do it ? Is it by simply issuing the command "# v-change-sys-hostname mail.yourdomain.com" on the command line of ssh? or do it from VESTA control panel and if so, how should I do it?
1.2. Is "yourdomain" in the above command should be replace by my new droplet IP, or by the main domain associated with it,
or something else, or stay the same?
2. You said: "One of your configuration files points a domain to 127.0.1.1 can you find which one?" - How can I find it? Shall I use the "netstat -plant" command, or something else?
Best regards,
Ami