Question
Perforce Droplet cannot be connected to after resize
- Posted on May 31, 2025
- DigitalOcean DropletsDroplets
Asked by brain56
I have a 25 GB, 2 GB RAM Perforce droplet that I resized to 80 GB, 4 GB RAM. The resize seemed to have gone smoothly without error or warning. However, after turning the droplet back on, I am unable to access it with P4V, P4Admin, nor the web console.
I can see that there’s CPU usage up to 4%, and Disk I/O up to 750 kB/s, but network Bandwidth remains at 0.
SSH and connection attempts via Command Prompt just time out, and the web console just stays on the waiting stage.
I’ve tried power cycling and turning it off and on again several times. Any suggestions? Thanks!
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!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
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 SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Get our newsletter
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
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.
Hey!
It sounds like your Droplet might’ve had a network misconfig after the resize. Sometimes the network interface doesn’t come up cleanly, especially if cloud-init or network configs get messed up.
If you can, try checking the network settings via the Recovery Console or boot into Recovery Mode to inspect the logs.
Try the answer from the following thread: Networking not working after Droplet resize
And if you’re still stuck, definitely reach out to DigitalOcean support so they can advise you further.
- Bobby
Heya, @brain56
Try booting your Droplet into recovery mode and check the network settings. Look at the netplan or interfaces file, depending on your OS. It’s possible the network config didn’t update properly after the resize.
Also, check the logs in /var/log/syslog or run dmesg to see if the system is stuck on something like a file system check. Make sure SSH is enabled and listening on the right interface.
If you’re still stuck, you can reach out to our support team and they will help you!