Apache error vagrant “Could not reliably determine the server's fully qualified domain name, using...
up vote
0
down vote
favorite
I am running Apache server with vagrant and I am getting this error "Could not reliably determine the server's fully qualified domain name, using 10.0.2.15. Set the 'ServerName' directive globally to suppress this message". Keep in mind that everything works fine.
Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.network "private_network", ip: "192.168.33.10"
config.vm.synced_folder "www/", "/var/www/html", :nfs => { :mount_options => ["dmode=777", "fmode=666"] }
config.vm.provision "shell", path: "bootstrap.sh"
end
bootstrap.sh
#!/usr/bin/env bash
apt-get update
apt-get upgrade
apt-get install -y apache2
a2enmod rewrite
apt-add-repository ppa:ondrej/php
apt-get update
apt-get install -y php7.2
apt-get install -y libapache2-mod-php7.2
service apache2 restart
apt-get install -y php7.2-common
apt-get install -y php7.2-zip
debconf-set-selections <<< 'mysql-server mysql-server/root_password password root'
debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root'
apt-get install -y mysql-server
apt-get install -y php7.2-mysql
sudo service apache2 restart
I know there is already an answer to my problem on this site but the solution is to connect to the server and fix the problem manually. How can I do this in bootstrap.sh so I dont have to fix each new server.
server apache2 vagrant
asked Dec 3 at 13:43
Diar
11
add a comment |
up vote
0
down vote
favorite
I am running Apache server with vagrant and I am getting this error "Could not reliably determine the server's fully qualified domain name, using 10.0.2.15. Set the 'ServerName' directive globally to suppress this message". Keep in mind that everything works fine.
Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.network "private_network", ip: "192.168.33.10"
config.vm.synced_folder "www/", "/var/www/html", :nfs => { :mount_options => ["dmode=777", "fmode=666"] }
config.vm.provision "shell", path: "bootstrap.sh"
end
bootstrap.sh
#!/usr/bin/env bash
apt-get update
apt-get upgrade
apt-get install -y apache2
a2enmod rewrite
apt-add-repository ppa:ondrej/php
apt-get update
apt-get install -y php7.2
apt-get install -y libapache2-mod-php7.2
service apache2 restart
apt-get install -y php7.2-common
apt-get install -y php7.2-zip
debconf-set-selections <<< 'mysql-server mysql-server/root_password password root'
debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root'
apt-get install -y mysql-server
apt-get install -y php7.2-mysql
sudo service apache2 restart
I know there is already an answer to my problem on this site but the solution is to connect to the server and fix the problem manually. How can I do this in bootstrap.sh so I dont have to fix each new server.
server apache2 vagrant
asked Dec 3 at 13:43
Diar
11
2
Possible duplicate of Apache error "Could not reliably determine the server's fully qualified domain name"
– Marc Vanhoomissen
Dec 3 at 15:10
@MarcVanhoomissen I would rather fix it in the bootstrap.sh file rather than connecting to the server and fix it manually. So I dont have to fix this for each new server.
– Diar
Dec 3 at 16:13
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am running Apache server with vagrant and I am getting this error "Could not reliably determine the server's fully qualified domain name, using 10.0.2.15. Set the 'ServerName' directive globally to suppress this message". Keep in mind that everything works fine.
Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.network "private_network", ip: "192.168.33.10"
config.vm.synced_folder "www/", "/var/www/html", :nfs => { :mount_options => ["dmode=777", "fmode=666"] }
config.vm.provision "shell", path: "bootstrap.sh"
end
bootstrap.sh
#!/usr/bin/env bash
apt-get update
apt-get upgrade
apt-get install -y apache2
a2enmod rewrite
apt-add-repository ppa:ondrej/php
apt-get update
apt-get install -y php7.2
apt-get install -y libapache2-mod-php7.2
service apache2 restart
apt-get install -y php7.2-common
apt-get install -y php7.2-zip
debconf-set-selections <<< 'mysql-server mysql-server/root_password password root'
debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root'
apt-get install -y mysql-server
apt-get install -y php7.2-mysql
sudo service apache2 restart
I know there is already an answer to my problem on this site but the solution is to connect to the server and fix the problem manually. How can I do this in bootstrap.sh so I dont have to fix each new server.
server apache2 vagrant
asked Dec 3 at 13:43
Diar
11
I am running Apache server with vagrant and I am getting this error "Could not reliably determine the server's fully qualified domain name, using 10.0.2.15. Set the 'ServerName' directive globally to suppress this message". Keep in mind that everything works fine.
Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
config.vm.network "private_network", ip: "192.168.33.10"
config.vm.synced_folder "www/", "/var/www/html", :nfs => { :mount_options => ["dmode=777", "fmode=666"] }
config.vm.provision "shell", path: "bootstrap.sh"
end
bootstrap.sh
#!/usr/bin/env bash
apt-get update
apt-get upgrade
apt-get install -y apache2
a2enmod rewrite
apt-add-repository ppa:ondrej/php
apt-get update
apt-get install -y php7.2
apt-get install -y libapache2-mod-php7.2
service apache2 restart
apt-get install -y php7.2-common
apt-get install -y php7.2-zip
debconf-set-selections <<< 'mysql-server mysql-server/root_password password root'
debconf-set-selections <<< 'mysql-server mysql-server/root_password_again password root'
apt-get install -y mysql-server
apt-get install -y php7.2-mysql
sudo service apache2 restart
I know there is already an answer to my problem on this site but the solution is to connect to the server and fix the problem manually. How can I do this in bootstrap.sh so I dont have to fix each new server.
server apache2 vagrant
server apache2 vagrant
asked Dec 3 at 13:43
Diar
11
asked Dec 3 at 13:43
Diar
11
edited Dec 3 at 16:27
asked Dec 3 at 13:43
Diar
11
asked Dec 3 at 13:43
Diar
11
asked Dec 3 at 13:43
Diar
11
11
2
Possible duplicate of Apache error "Could not reliably determine the server's fully qualified domain name"
– Marc Vanhoomissen
Dec 3 at 15:10
@MarcVanhoomissen I would rather fix it in the bootstrap.sh file rather than connecting to the server and fix it manually. So I dont have to fix this for each new server.
– Diar
Dec 3 at 16:13
add a comment |
2
Possible duplicate of Apache error "Could not reliably determine the server's fully qualified domain name"
– Marc Vanhoomissen
Dec 3 at 15:10
@MarcVanhoomissen I would rather fix it in the bootstrap.sh file rather than connecting to the server and fix it manually. So I dont have to fix this for each new server.
– Diar
Dec 3 at 16:13
2
2
Possible duplicate of Apache error "Could not reliably determine the server's fully qualified domain name"
– Marc Vanhoomissen
Dec 3 at 15:10
Possible duplicate of Apache error "Could not reliably determine the server's fully qualified domain name"
– Marc Vanhoomissen
Dec 3 at 15:10
@MarcVanhoomissen I would rather fix it in the bootstrap.sh file rather than connecting to the server and fix it manually. So I dont have to fix this for each new server.
– Diar
Dec 3 at 16:13
@MarcVanhoomissen I would rather fix it in the bootstrap.sh file rather than connecting to the server and fix it manually. So I dont have to fix this for each new server.
– Diar
Dec 3 at 16:13
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098154%2fapache-error-vagrant-could-not-reliably-determine-the-servers-fully-qualified%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1098154%2fapache-error-vagrant-could-not-reliably-determine-the-servers-fully-qualified%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Possible duplicate of Apache error "Could not reliably determine the server's fully qualified domain name"
– Marc Vanhoomissen
Dec 3 at 15:10
@MarcVanhoomissen I would rather fix it in the bootstrap.sh file rather than connecting to the server and fix it manually. So I dont have to fix this for each new server.
– Diar
Dec 3 at 16:13