Ubuntu server 16.04 can't ping outside IP's or domains or do updates
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I moved my server to my work and setup everything.
Changed the Internal IP to a new on and also changed the static IP to a new one.
When I do a ifconfig the new IP address/default-gateway/subnet all show as correctly.
The problem is I can't access the server through any pc on the network, can't ping any domain or external IP, can't do a apt-get anything, I added new rules to the firewall I am using now(mikrotike router/firwall) allowed port 80 and also pointed the new static IP to my domain company used(onlydomains.com). I also restarted apache2, the actual server and even router.
I can only ping internal IP's only.
I checked out many posts and google and was told to check:
/etc/resolve.conf
/etc/network/interfaces
/etc/gai.conf
(uncomment. precedence::ffff:0:0/96 100) to get apt-get working
also flush ip setting
When the server was by my home everything worked perfectly. I could access the website, ssh into the server from anywhere and so on.
I am so confused and don't know what needs to be done in order to fix it.
*If this has been solved somewhere please direct me there.
Thanks
Update:
ip route output:
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
changes made in /etc/network/interfaces
= I changed the network/broadcast/gateway as these were outside the range of the IP Address.
Can reach the server via SSH and can ping the default gateway however I can't ping any domain only IP's on the network. Also can't do any apt-get's.
dig google.com
; <<>> Dig 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
/etc/resolv.conf
nameserver 41.xxx.0.36
nameserver 41.xxx.0.37
search website.com
dig google.com @8.8.8.8
;<<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17942
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com IN A
;; ANSWER SECTION:
google.com. 192 IN A 216.58.223.46
;; QUERY time: 104 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 13 10:22:42 SAST 2018
;; MSG SIZE rcvd: 55
networking server ssh dns webserver
asked Apr 12 at 9:07
Deez Nutz
206
add a comment |Â
up vote
1
down vote
favorite
I moved my server to my work and setup everything.
Changed the Internal IP to a new on and also changed the static IP to a new one.
When I do a ifconfig the new IP address/default-gateway/subnet all show as correctly.
The problem is I can't access the server through any pc on the network, can't ping any domain or external IP, can't do a apt-get anything, I added new rules to the firewall I am using now(mikrotike router/firwall) allowed port 80 and also pointed the new static IP to my domain company used(onlydomains.com). I also restarted apache2, the actual server and even router.
I can only ping internal IP's only.
I checked out many posts and google and was told to check:
/etc/resolve.conf
/etc/network/interfaces
/etc/gai.conf
(uncomment. precedence::ffff:0:0/96 100) to get apt-get working
also flush ip setting
When the server was by my home everything worked perfectly. I could access the website, ssh into the server from anywhere and so on.
I am so confused and don't know what needs to be done in order to fix it.
*If this has been solved somewhere please direct me there.
Thanks
Update:
ip route output:
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
changes made in /etc/network/interfaces
= I changed the network/broadcast/gateway as these were outside the range of the IP Address.
Can reach the server via SSH and can ping the default gateway however I can't ping any domain only IP's on the network. Also can't do any apt-get's.
dig google.com
; <<>> Dig 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
/etc/resolv.conf
nameserver 41.xxx.0.36
nameserver 41.xxx.0.37
search website.com
dig google.com @8.8.8.8
;<<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17942
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com IN A
;; ANSWER SECTION:
google.com. 192 IN A 216.58.223.46
;; QUERY time: 104 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 13 10:22:42 SAST 2018
;; MSG SIZE rcvd: 55
networking server ssh dns webserver
asked Apr 12 at 9:07
Deez Nutz
206
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I moved my server to my work and setup everything.
Changed the Internal IP to a new on and also changed the static IP to a new one.
When I do a ifconfig the new IP address/default-gateway/subnet all show as correctly.
The problem is I can't access the server through any pc on the network, can't ping any domain or external IP, can't do a apt-get anything, I added new rules to the firewall I am using now(mikrotike router/firwall) allowed port 80 and also pointed the new static IP to my domain company used(onlydomains.com). I also restarted apache2, the actual server and even router.
I can only ping internal IP's only.
I checked out many posts and google and was told to check:
/etc/resolve.conf
/etc/network/interfaces
/etc/gai.conf
(uncomment. precedence::ffff:0:0/96 100) to get apt-get working
also flush ip setting
When the server was by my home everything worked perfectly. I could access the website, ssh into the server from anywhere and so on.
I am so confused and don't know what needs to be done in order to fix it.
*If this has been solved somewhere please direct me there.
Thanks
Update:
ip route output:
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
changes made in /etc/network/interfaces
= I changed the network/broadcast/gateway as these were outside the range of the IP Address.
Can reach the server via SSH and can ping the default gateway however I can't ping any domain only IP's on the network. Also can't do any apt-get's.
dig google.com
; <<>> Dig 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
/etc/resolv.conf
nameserver 41.xxx.0.36
nameserver 41.xxx.0.37
search website.com
dig google.com @8.8.8.8
;<<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17942
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com IN A
;; ANSWER SECTION:
google.com. 192 IN A 216.58.223.46
;; QUERY time: 104 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 13 10:22:42 SAST 2018
;; MSG SIZE rcvd: 55
networking server ssh dns webserver
asked Apr 12 at 9:07
Deez Nutz
206
I moved my server to my work and setup everything.
Changed the Internal IP to a new on and also changed the static IP to a new one.
When I do a ifconfig the new IP address/default-gateway/subnet all show as correctly.
The problem is I can't access the server through any pc on the network, can't ping any domain or external IP, can't do a apt-get anything, I added new rules to the firewall I am using now(mikrotike router/firwall) allowed port 80 and also pointed the new static IP to my domain company used(onlydomains.com). I also restarted apache2, the actual server and even router.
I can only ping internal IP's only.
I checked out many posts and google and was told to check:
/etc/resolve.conf
/etc/network/interfaces
/etc/gai.conf
(uncomment. precedence::ffff:0:0/96 100) to get apt-get working
also flush ip setting
When the server was by my home everything worked perfectly. I could access the website, ssh into the server from anywhere and so on.
I am so confused and don't know what needs to be done in order to fix it.
*If this has been solved somewhere please direct me there.
Thanks
Update:
ip route output:
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
changes made in /etc/network/interfaces
= I changed the network/broadcast/gateway as these were outside the range of the IP Address.
Can reach the server via SSH and can ping the default gateway however I can't ping any domain only IP's on the network. Also can't do any apt-get's.
dig google.com
; <<>> Dig 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
/etc/resolv.conf
nameserver 41.xxx.0.36
nameserver 41.xxx.0.37
search website.com
dig google.com @8.8.8.8
;<<>> DiG 9.10.3-P4-Ubuntu <<>> google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17942
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com IN A
;; ANSWER SECTION:
google.com. 192 IN A 216.58.223.46
;; QUERY time: 104 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 13 10:22:42 SAST 2018
;; MSG SIZE rcvd: 55
networking server ssh dns webserver
networking server ssh dns webserver
asked Apr 12 at 9:07
Deez Nutz
206
asked Apr 12 at 9:07
Deez Nutz
206
edited Apr 13 at 8:30
asked Apr 12 at 9:07
Deez Nutz
206
asked Apr 12 at 9:07
Deez Nutz
206
asked Apr 12 at 9:07
Deez Nutz
206
206
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
So your local network is 192.168.11.0/24 by the looks of it, and your IP address on eno1 is 192.168.11.199.
But your default gateway is 192.168.1.254.
This will not work. Your local gateway is outside your local network, so you have no means of contacting it.
You have to check your network settings in /etc/network/interfaces, so that the configuration is consistent. When that's done verify that you're able to ping your default gateway.
In addition, it seems that your defined DNS servers do not work. Some suggested servers would be Cloudflare's, at 1.1.1.1 or Google's at 8.8.8.8.
In /etc/network/interfaces you will have a line like
dns-nameservers 41...
Change this to dns-nameservers 1.1.1.1 for instance, and either reboot, or edit /etc/resolv.conf and replace the current nameserver 41... lines with nameserver 1.1.1.1.
Verify that you're able to ping google.com
answered Apr 12 at 11:47
vidarlo
7,14342140
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
What is the content of/etc/resolv.conf? What happens if you trydig google.com @8.8.8.8? What happens if you trydig google.com? Edit your question with the outputs, and ping me in a message :)
– vidarlo
Apr 12 at 14:59
 |Â
show 5 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
So your local network is 192.168.11.0/24 by the looks of it, and your IP address on eno1 is 192.168.11.199.
But your default gateway is 192.168.1.254.
This will not work. Your local gateway is outside your local network, so you have no means of contacting it.
You have to check your network settings in /etc/network/interfaces, so that the configuration is consistent. When that's done verify that you're able to ping your default gateway.
In addition, it seems that your defined DNS servers do not work. Some suggested servers would be Cloudflare's, at 1.1.1.1 or Google's at 8.8.8.8.
In /etc/network/interfaces you will have a line like
dns-nameservers 41...
Change this to dns-nameservers 1.1.1.1 for instance, and either reboot, or edit /etc/resolv.conf and replace the current nameserver 41... lines with nameserver 1.1.1.1.
Verify that you're able to ping google.com
answered Apr 12 at 11:47
vidarlo
7,14342140
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
What is the content of/etc/resolv.conf? What happens if you trydig google.com @8.8.8.8? What happens if you trydig google.com? Edit your question with the outputs, and ping me in a message :)
– vidarlo
Apr 12 at 14:59
 |Â
show 5 more comments
up vote
1
down vote
accepted
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
So your local network is 192.168.11.0/24 by the looks of it, and your IP address on eno1 is 192.168.11.199.
But your default gateway is 192.168.1.254.
This will not work. Your local gateway is outside your local network, so you have no means of contacting it.
You have to check your network settings in /etc/network/interfaces, so that the configuration is consistent. When that's done verify that you're able to ping your default gateway.
In addition, it seems that your defined DNS servers do not work. Some suggested servers would be Cloudflare's, at 1.1.1.1 or Google's at 8.8.8.8.
In /etc/network/interfaces you will have a line like
dns-nameservers 41...
Change this to dns-nameservers 1.1.1.1 for instance, and either reboot, or edit /etc/resolv.conf and replace the current nameserver 41... lines with nameserver 1.1.1.1.
Verify that you're able to ping google.com
answered Apr 12 at 11:47
vidarlo
7,14342140
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
What is the content of/etc/resolv.conf? What happens if you trydig google.com @8.8.8.8? What happens if you trydig google.com? Edit your question with the outputs, and ping me in a message :)
– vidarlo
Apr 12 at 14:59
 |Â
show 5 more comments
up vote
1
down vote
accepted
up vote
1
down vote
accepted
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
So your local network is 192.168.11.0/24 by the looks of it, and your IP address on eno1 is 192.168.11.199.
But your default gateway is 192.168.1.254.
This will not work. Your local gateway is outside your local network, so you have no means of contacting it.
You have to check your network settings in /etc/network/interfaces, so that the configuration is consistent. When that's done verify that you're able to ping your default gateway.
In addition, it seems that your defined DNS servers do not work. Some suggested servers would be Cloudflare's, at 1.1.1.1 or Google's at 8.8.8.8.
In /etc/network/interfaces you will have a line like
dns-nameservers 41...
Change this to dns-nameservers 1.1.1.1 for instance, and either reboot, or edit /etc/resolv.conf and replace the current nameserver 41... lines with nameserver 1.1.1.1.
Verify that you're able to ping google.com
answered Apr 12 at 11:47
vidarlo
7,14342140
default via 192.168.1.254 dev eno1 onlink
192.168.11.0/24 dev eno1 proto kernel scope link src 192.168.11.199
So your local network is 192.168.11.0/24 by the looks of it, and your IP address on eno1 is 192.168.11.199.
But your default gateway is 192.168.1.254.
This will not work. Your local gateway is outside your local network, so you have no means of contacting it.
You have to check your network settings in /etc/network/interfaces, so that the configuration is consistent. When that's done verify that you're able to ping your default gateway.
In addition, it seems that your defined DNS servers do not work. Some suggested servers would be Cloudflare's, at 1.1.1.1 or Google's at 8.8.8.8.
In /etc/network/interfaces you will have a line like
dns-nameservers 41...
Change this to dns-nameservers 1.1.1.1 for instance, and either reboot, or edit /etc/resolv.conf and replace the current nameserver 41... lines with nameserver 1.1.1.1.
Verify that you're able to ping google.com
answered Apr 12 at 11:47
vidarlo
7,14342140
edited Apr 13 at 8:41
answered Apr 12 at 11:47
vidarlo
7,14342140
answered Apr 12 at 11:47
vidarlo
7,14342140
answered Apr 12 at 11:47
vidarlo
7,14342140
7,14342140
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
What is the content of/etc/resolv.conf? What happens if you trydig google.com @8.8.8.8? What happens if you trydig google.com? Edit your question with the outputs, and ping me in a message :)
– vidarlo
Apr 12 at 14:59
 |Â
show 5 more comments
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
What is the content of/etc/resolv.conf? What happens if you trydig google.com @8.8.8.8? What happens if you trydig google.com? Edit your question with the outputs, and ping me in a message :)
– vidarlo
Apr 12 at 14:59
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
I can now ping the default gateway and can reach the server via SSH, however I cannot do any apt-get's
– Deez Nutz
Apr 12 at 12:33
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
You probably have to set DNS server as well.
– vidarlo
Apr 12 at 12:57
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
How would I do that? I am still a noob when it comes to this. I have set the dns-nameserver in the /etc/network/interfaces. And set it in the /etc/resolv.conf
– Deez Nutz
Apr 12 at 14:00
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
I have tried a solution from another post where it was said to try ifdown eno1 && sudo ifup eno1 but that made no difference. Does it take time for things to sink in before that command would work maybe?
– Deez Nutz
Apr 12 at 14:08
What is the content of
/etc/resolv.conf? What happens if you try dig google.com @8.8.8.8? What happens if you try dig google.com? Edit your question with the outputs, and ping me in a message :)– vidarlo
Apr 12 at 14:59
What is the content of
/etc/resolv.conf? What happens if you try dig google.com @8.8.8.8? What happens if you try dig google.com? Edit your question with the outputs, and ping me in a message :)– vidarlo
Apr 12 at 14:59
 |Â
show 5 more comments
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1024304%2fubuntu-server-16-04-cant-ping-outside-ips-or-domains-or-do-updates%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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