Digitalocean droplet can not access internet, nor can be accessed from outside
I was working with my droplet (via ssh) and suddenly it disconnected so I went to the digital ocean control panel and did a hard reset.
It restarted but it can't be reached from outside (ping, ssh) and it can not reach internet from inside.
I will really appreciate any help since is my production server and can not just destroy the droplet.
Screenshots of the terminal info
Network interfaces
ifconfig
networking ssh
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
add a comment |
I was working with my droplet (via ssh) and suddenly it disconnected so I went to the digital ocean control panel and did a hard reset.
It restarted but it can't be reached from outside (ping, ssh) and it can not reach internet from inside.
I will really appreciate any help since is my production server and can not just destroy the droplet.
Screenshots of the terminal info
Network interfaces
ifconfig
networking ssh
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
Since it's your production droplet then you have a backup right? Have you contacted Digital Ocean to verify the problem is the droplet not their hardware?
– Ramhound
Jul 29 '17 at 15:18
I was downloading my db and in that moment the connection broke up. I Will contact them
– Marco Santana
Jul 29 '17 at 16:34
when I restart the server it only has lo interface and only after service networking restart the other appear but it still doesn't work
– Marco Santana
Jul 29 '17 at 19:31
add a comment |
I was working with my droplet (via ssh) and suddenly it disconnected so I went to the digital ocean control panel and did a hard reset.
It restarted but it can't be reached from outside (ping, ssh) and it can not reach internet from inside.
I will really appreciate any help since is my production server and can not just destroy the droplet.
Screenshots of the terminal info
Network interfaces
ifconfig
networking ssh
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
I was working with my droplet (via ssh) and suddenly it disconnected so I went to the digital ocean control panel and did a hard reset.
It restarted but it can't be reached from outside (ping, ssh) and it can not reach internet from inside.
I will really appreciate any help since is my production server and can not just destroy the droplet.
Screenshots of the terminal info
Network interfaces
ifconfig
networking ssh
networking ssh
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
edited Jul 29 '17 at 16:52
Marco Santana
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
asked Jul 29 '17 at 15:13
Marco SantanaMarco Santana
166
166
Since it's your production droplet then you have a backup right? Have you contacted Digital Ocean to verify the problem is the droplet not their hardware?
– Ramhound
Jul 29 '17 at 15:18
I was downloading my db and in that moment the connection broke up. I Will contact them
– Marco Santana
Jul 29 '17 at 16:34
when I restart the server it only has lo interface and only after service networking restart the other appear but it still doesn't work
– Marco Santana
Jul 29 '17 at 19:31
add a comment |
Since it's your production droplet then you have a backup right? Have you contacted Digital Ocean to verify the problem is the droplet not their hardware?
– Ramhound
Jul 29 '17 at 15:18
I was downloading my db and in that moment the connection broke up. I Will contact them
– Marco Santana
Jul 29 '17 at 16:34
when I restart the server it only has lo interface and only after service networking restart the other appear but it still doesn't work
– Marco Santana
Jul 29 '17 at 19:31
Since it's your production droplet then you have a backup right? Have you contacted Digital Ocean to verify the problem is the droplet not their hardware?
– Ramhound
Jul 29 '17 at 15:18
Since it's your production droplet then you have a backup right? Have you contacted Digital Ocean to verify the problem is the droplet not their hardware?
– Ramhound
Jul 29 '17 at 15:18
I was downloading my db and in that moment the connection broke up. I Will contact them
– Marco Santana
Jul 29 '17 at 16:34
I was downloading my db and in that moment the connection broke up. I Will contact them
– Marco Santana
Jul 29 '17 at 16:34
when I restart the server it only has lo interface and only after service networking restart the other appear but it still doesn't work
– Marco Santana
Jul 29 '17 at 19:31
when I restart the server it only has lo interface and only after service networking restart the other appear but it still doesn't work
– Marco Santana
Jul 29 '17 at 19:31
add a comment |
1 Answer
1
active
oldest
votes
It is possible there's a problem with the /etc/resolv.conf file (Probably empty or wrongly configured) since ping does not work, run dig google.com A +trace to trace the DNS paths.
Typically you should have output like
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com A +trace
;; global options: +cmd
. 42083 IN NS a.root-servers.net.
. 42083 IN NS b.root-servers.net.
. 42083 IN NS c.root-servers.net.
. 42083 IN NS d.root-servers.net.
. 42083 IN NS e.root-servers.net.
. 42083 IN NS f.root-servers.net.
. 42083 IN NS g.root-servers.net.
. 42083 IN NS h.root-servers.net.
. 42083 IN NS i.root-servers.net.
. 42083 IN NS j.root-servers.net.
. 42083 IN NS k.root-servers.net.
. 42083 IN NS l.root-servers.net.
. 42083 IN NS m.root-servers.net.
. 42083 IN RRSIG NS 8 0 518400 20190212170000 20190130160000 16749 . eMPtAtRg5I5Rs5FG0dWDRxn/8/wDMavt/zz1YiIkLBeq6RaY1bfuWsmT Bo0zNzx1/hW4nh/aJpmgBOlTlOs9ZU0lAOJa2rHBnKJjNiu0dMJCkWDR uTxyDjG5Xi9orXw2yy0sa38gZkkZoZo/GGtZZRSXFXFFVg+S8iOjm6ZV AoYOLsiP3VranLSONnIadzdMVAw4WdeVYWvUdsXxOLtWzETR4bmOzdYK u9IXjBrwYEe7HQCyb0rRITkcpfULaFjD+u+4IG7Q2v5GnucKWbXeykLS PEOSUhuWL9D4pPpAR3KhC7qOqLQeGRkzaFPQgST2icfepNtpC863QJR8 Kl+FqA==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms
The last line (in my paste, as it is longer) ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms shows a DNS server from which 525 bytes was received in 1ms if you do see an out similar to this then you would need to edit your /etc/resolv.conf... sudo nano /etc/resolv.conf add
nameserver 8.8.8.8
nameserver 8.8.4.4
Try to ping google again
REF : Digital Ocean unable to ping external websites
Hopefully that helps.
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
1
and it can not reach internet from insideyou should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internetfrom inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.
– F.E Noel Nfebe
Feb 4 at 7:46
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
|
show 1 more comment
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
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%2fsuperuser.com%2fquestions%2f1235707%2fdigitalocean-droplet-can-not-access-internet-nor-can-be-accessed-from-outside%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is possible there's a problem with the /etc/resolv.conf file (Probably empty or wrongly configured) since ping does not work, run dig google.com A +trace to trace the DNS paths.
Typically you should have output like
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com A +trace
;; global options: +cmd
. 42083 IN NS a.root-servers.net.
. 42083 IN NS b.root-servers.net.
. 42083 IN NS c.root-servers.net.
. 42083 IN NS d.root-servers.net.
. 42083 IN NS e.root-servers.net.
. 42083 IN NS f.root-servers.net.
. 42083 IN NS g.root-servers.net.
. 42083 IN NS h.root-servers.net.
. 42083 IN NS i.root-servers.net.
. 42083 IN NS j.root-servers.net.
. 42083 IN NS k.root-servers.net.
. 42083 IN NS l.root-servers.net.
. 42083 IN NS m.root-servers.net.
. 42083 IN RRSIG NS 8 0 518400 20190212170000 20190130160000 16749 . eMPtAtRg5I5Rs5FG0dWDRxn/8/wDMavt/zz1YiIkLBeq6RaY1bfuWsmT Bo0zNzx1/hW4nh/aJpmgBOlTlOs9ZU0lAOJa2rHBnKJjNiu0dMJCkWDR uTxyDjG5Xi9orXw2yy0sa38gZkkZoZo/GGtZZRSXFXFFVg+S8iOjm6ZV AoYOLsiP3VranLSONnIadzdMVAw4WdeVYWvUdsXxOLtWzETR4bmOzdYK u9IXjBrwYEe7HQCyb0rRITkcpfULaFjD+u+4IG7Q2v5GnucKWbXeykLS PEOSUhuWL9D4pPpAR3KhC7qOqLQeGRkzaFPQgST2icfepNtpC863QJR8 Kl+FqA==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms
The last line (in my paste, as it is longer) ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms shows a DNS server from which 525 bytes was received in 1ms if you do see an out similar to this then you would need to edit your /etc/resolv.conf... sudo nano /etc/resolv.conf add
nameserver 8.8.8.8
nameserver 8.8.4.4
Try to ping google again
REF : Digital Ocean unable to ping external websites
Hopefully that helps.
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
1
and it can not reach internet from insideyou should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internetfrom inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.
– F.E Noel Nfebe
Feb 4 at 7:46
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
|
show 1 more comment
It is possible there's a problem with the /etc/resolv.conf file (Probably empty or wrongly configured) since ping does not work, run dig google.com A +trace to trace the DNS paths.
Typically you should have output like
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com A +trace
;; global options: +cmd
. 42083 IN NS a.root-servers.net.
. 42083 IN NS b.root-servers.net.
. 42083 IN NS c.root-servers.net.
. 42083 IN NS d.root-servers.net.
. 42083 IN NS e.root-servers.net.
. 42083 IN NS f.root-servers.net.
. 42083 IN NS g.root-servers.net.
. 42083 IN NS h.root-servers.net.
. 42083 IN NS i.root-servers.net.
. 42083 IN NS j.root-servers.net.
. 42083 IN NS k.root-servers.net.
. 42083 IN NS l.root-servers.net.
. 42083 IN NS m.root-servers.net.
. 42083 IN RRSIG NS 8 0 518400 20190212170000 20190130160000 16749 . eMPtAtRg5I5Rs5FG0dWDRxn/8/wDMavt/zz1YiIkLBeq6RaY1bfuWsmT Bo0zNzx1/hW4nh/aJpmgBOlTlOs9ZU0lAOJa2rHBnKJjNiu0dMJCkWDR uTxyDjG5Xi9orXw2yy0sa38gZkkZoZo/GGtZZRSXFXFFVg+S8iOjm6ZV AoYOLsiP3VranLSONnIadzdMVAw4WdeVYWvUdsXxOLtWzETR4bmOzdYK u9IXjBrwYEe7HQCyb0rRITkcpfULaFjD+u+4IG7Q2v5GnucKWbXeykLS PEOSUhuWL9D4pPpAR3KhC7qOqLQeGRkzaFPQgST2icfepNtpC863QJR8 Kl+FqA==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms
The last line (in my paste, as it is longer) ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms shows a DNS server from which 525 bytes was received in 1ms if you do see an out similar to this then you would need to edit your /etc/resolv.conf... sudo nano /etc/resolv.conf add
nameserver 8.8.8.8
nameserver 8.8.4.4
Try to ping google again
REF : Digital Ocean unable to ping external websites
Hopefully that helps.
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
1
and it can not reach internet from insideyou should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internetfrom inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.
– F.E Noel Nfebe
Feb 4 at 7:46
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
|
show 1 more comment
It is possible there's a problem with the /etc/resolv.conf file (Probably empty or wrongly configured) since ping does not work, run dig google.com A +trace to trace the DNS paths.
Typically you should have output like
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com A +trace
;; global options: +cmd
. 42083 IN NS a.root-servers.net.
. 42083 IN NS b.root-servers.net.
. 42083 IN NS c.root-servers.net.
. 42083 IN NS d.root-servers.net.
. 42083 IN NS e.root-servers.net.
. 42083 IN NS f.root-servers.net.
. 42083 IN NS g.root-servers.net.
. 42083 IN NS h.root-servers.net.
. 42083 IN NS i.root-servers.net.
. 42083 IN NS j.root-servers.net.
. 42083 IN NS k.root-servers.net.
. 42083 IN NS l.root-servers.net.
. 42083 IN NS m.root-servers.net.
. 42083 IN RRSIG NS 8 0 518400 20190212170000 20190130160000 16749 . eMPtAtRg5I5Rs5FG0dWDRxn/8/wDMavt/zz1YiIkLBeq6RaY1bfuWsmT Bo0zNzx1/hW4nh/aJpmgBOlTlOs9ZU0lAOJa2rHBnKJjNiu0dMJCkWDR uTxyDjG5Xi9orXw2yy0sa38gZkkZoZo/GGtZZRSXFXFFVg+S8iOjm6ZV AoYOLsiP3VranLSONnIadzdMVAw4WdeVYWvUdsXxOLtWzETR4bmOzdYK u9IXjBrwYEe7HQCyb0rRITkcpfULaFjD+u+4IG7Q2v5GnucKWbXeykLS PEOSUhuWL9D4pPpAR3KhC7qOqLQeGRkzaFPQgST2icfepNtpC863QJR8 Kl+FqA==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms
The last line (in my paste, as it is longer) ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms shows a DNS server from which 525 bytes was received in 1ms if you do see an out similar to this then you would need to edit your /etc/resolv.conf... sudo nano /etc/resolv.conf add
nameserver 8.8.8.8
nameserver 8.8.4.4
Try to ping google again
REF : Digital Ocean unable to ping external websites
Hopefully that helps.
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
It is possible there's a problem with the /etc/resolv.conf file (Probably empty or wrongly configured) since ping does not work, run dig google.com A +trace to trace the DNS paths.
Typically you should have output like
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com A +trace
;; global options: +cmd
. 42083 IN NS a.root-servers.net.
. 42083 IN NS b.root-servers.net.
. 42083 IN NS c.root-servers.net.
. 42083 IN NS d.root-servers.net.
. 42083 IN NS e.root-servers.net.
. 42083 IN NS f.root-servers.net.
. 42083 IN NS g.root-servers.net.
. 42083 IN NS h.root-servers.net.
. 42083 IN NS i.root-servers.net.
. 42083 IN NS j.root-servers.net.
. 42083 IN NS k.root-servers.net.
. 42083 IN NS l.root-servers.net.
. 42083 IN NS m.root-servers.net.
. 42083 IN RRSIG NS 8 0 518400 20190212170000 20190130160000 16749 . eMPtAtRg5I5Rs5FG0dWDRxn/8/wDMavt/zz1YiIkLBeq6RaY1bfuWsmT Bo0zNzx1/hW4nh/aJpmgBOlTlOs9ZU0lAOJa2rHBnKJjNiu0dMJCkWDR uTxyDjG5Xi9orXw2yy0sa38gZkkZoZo/GGtZZRSXFXFFVg+S8iOjm6ZV AoYOLsiP3VranLSONnIadzdMVAw4WdeVYWvUdsXxOLtWzETR4bmOzdYK u9IXjBrwYEe7HQCyb0rRITkcpfULaFjD+u+4IG7Q2v5GnucKWbXeykLS PEOSUhuWL9D4pPpAR3KhC7qOqLQeGRkzaFPQgST2icfepNtpC863QJR8 Kl+FqA==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms
The last line (in my paste, as it is longer) ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 1 ms shows a DNS server from which 525 bytes was received in 1ms if you do see an out similar to this then you would need to edit your /etc/resolv.conf... sudo nano /etc/resolv.conf add
nameserver 8.8.8.8
nameserver 8.8.4.4
Try to ping google again
REF : Digital Ocean unable to ping external websites
Hopefully that helps.
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
answered Feb 2 at 17:05
F.E Noel NfebeF.E Noel Nfebe
101
101
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
1
and it can not reach internet from insideyou should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internetfrom inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.
– F.E Noel Nfebe
Feb 4 at 7:46
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
|
show 1 more comment
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
1
and it can not reach internet from insideyou should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internetfrom inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.
– F.E Noel Nfebe
Feb 4 at 7:46
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
How does this relate to the question?
– RalfFriedl
Feb 2 at 17:15
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
@RalFriedl I don't understand your question. As you can clearly my answer is suggesting a possible cause and solution for why a droplet may not connect to the internet.
– F.E Noel Nfebe
Feb 4 at 6:18
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
The question says "can't be reached from outside". That is not a resolver problem.
– RalfFriedl
Feb 4 at 6:54
1
1
and it can not reach internet from inside you should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internet from inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.– F.E Noel Nfebe
Feb 4 at 7:46
and it can not reach internet from inside you should read details carefully! The server cannot be connected to from outside but addittionally, it can't access the internet from inside. That's even a possible cause of it's not being accesible from outside, hence the answer is in context.– F.E Noel Nfebe
Feb 4 at 7:46
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
Thanks a little time has passed scince I posted the question. And had to destroy the droplet and recreate it from a backup. I cannot replicate the porble so I can not test your solution but thanks and I hop eit helps someone else.
– Marco Santana
Feb 6 at 23:00
|
show 1 more comment
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1235707%2fdigitalocean-droplet-can-not-access-internet-nor-can-be-accessed-from-outside%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
Since it's your production droplet then you have a backup right? Have you contacted Digital Ocean to verify the problem is the droplet not their hardware?
– Ramhound
Jul 29 '17 at 15:18
I was downloading my db and in that moment the connection broke up. I Will contact them
– Marco Santana
Jul 29 '17 at 16:34
when I restart the server it only has lo interface and only after service networking restart the other appear but it still doesn't work
– Marco Santana
Jul 29 '17 at 19:31