I am unable to access my droplet via SSH and the site is not responding to a browser. When i log into the console in the droplet settings window i see logs running like this:
[27582.814924] device vetha011770 entered promiscuous mode [27582.824511] docker0: port 2(vetha011770) entered blocking state [27582.827089] docker0: port 2(vetha011770) entered forwarding state [27582.993308] IPv6: ADDRCONF(NETDEV_UP): vethc587cdb: link is not ready [27582.028330] IPv6 ADDRCONF(NETDEV_CHANGE): vethc587cdb: link becomes ready … (this pattern then repeats over and over - port numbers change and a few other things but the pattern is the same, promiscuous, blocking, forwarding etc)
Due to this the site has been offline for a week now, digitalocean support have been no help and i am at a loss on how to rectify this.
does anyone have any idea on what is causing this and a possible solution?
thanks in advance
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I have this same problem:
- Cannot SSH
- A lot of noise on the DigitalOcean console for every container I have
- Have to “feel” my way to get the IP address working.
My CoreOS droplet no longer picks up the IP address provided in the /etc/environment file which has the COREOS_PUBLIC_IPV4=128.xxx.xxx.xxx defined.
I have to login in the console and look around. The docker virtual interface noise on the console didn’t help.
ifconfig eth0 shows a 169.x.x.x IP address, which means that it did not get the IP at all.
I forced a ifconfig eth0 128.xxx.xxx.xxx netmask 255.255.192.0 and route add 128.xxx.xxx.1 + add a nameserver to /etc/resolv.conf (of course, netmask and default route is pure guesswork, and a lucky one at that), and the docker noise is no longer there. And some of containers started to work, but I have to restart the nginx one. I can SSH to my instance again.
I’ve looked high and low for configuration details pertaining to IP addressing, but since this is --oem=digitalocean stuff, I have no idea where to begin.
Anyone with any ideas how the droplet configures itself with a provided IP address?
I launched a new coreOS instance, to see the differences, but have no idea where to begin.
Any help?
Thanks Wari
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.