Ubuntu 23.10 on DigitalOcean VPS: Unable to use curl

Curl fails on Ubuntu 23.10 DigitalOcean VPS due to network configuration errors, missing dependencies, or firewall restrictions. Verify internet connectivity with ping, ensure curl is installed via apt, and check UFW rules. If issues persist, inspect proxy settings and DNS resolution to restore functionality.

Verifying Network Connectivity

Before troubleshooting curl specifically, you must confirm that the Virtual Private Server (VPS) has active internet access. DigitalOcean droplets can sometimes lose connectivity due to IP conflicts, routing table errors, or upstream provider issues. The first diagnostic step is to ping a reliable external host. Open your terminal and execute the following command:

ping -c 4 google.com

If this command returns replies, your network interface is functioning correctly at the ICMP level. However, if it fails, the issue lies deeper than curl. Check your network configuration by running ip addr show to ensure your primary interface (usually eth0) has a valid public IP address assigned. Additionally, verify your default gateway using ip route show. If the gateway is missing, you may need to restart the networking service with sudo systemctl restart networking or reboot the droplet from the DigitalOcean control panel. In cases where connectivity is intermittent, refer to Ubuntu 22.04 VM on KVM/virt-manager Not Connecting to Internet for broader network troubleshooting strategies applicable to Linux VPS environments.

Checking Curl Installation and Dependencies

If network connectivity is confirmed, the next logical step is to verify that curl is actually installed and not corrupted. On minimal Ubuntu installations, curl might not be present by default. Check its presence by running:

which curl

If this returns no output, install curl using the package manager:

sudo apt update
sudo apt install curl

After installation, test the binary directly. Sometimes, permissions or broken symlinks can prevent execution. Ensure the binary is executable by checking file permissions with ls -l /usr/bin/curl. If curl is installed but still fails to run, there may be missing shared libraries. You can diagnose this by running ldd $(which curl). This command lists all shared libraries required by curl. If any library shows as "not found," you likely have a broken dependency chain. Reinstalling the package with sudo apt --reinstall install curl often resolves these library mismatches. For users migrating from other distributions, note that while RHEL-based systems use yum or dnf, Ubuntu relies exclusively on apt. See Troubleshooting curl not working on an RHEL8 Server for comparative insights on package management differences.

Inspecting Firewall and Security Groups

DigitalOcean implements firewall rules at both the host level (UFW) and the cloud level (Cloud Firewall). Even if curl is installed and connected, outbound traffic might be blocked by misconfigured rules. Although curl typically uses HTTP (port 80) and HTTPS (port 443), which are usually open by default, custom security groups can restrict these ports. Check the status of the Uncomplicated Firewall (UFW) on your VPS:

sudo ufw status

If UFW is active, ensure that outgoing traffic is allowed. By default, UFW allows all outgoing connections, but if you have customized the policy, you might need to explicitly allow them. More importantly, check the DigitalOcean Cloud Firewall settings in the web console. Navigate to Networking > Firewalls and verify that your droplet is attached to a firewall rule that permits outbound traffic on ports 80 and 443. If you recently applied a new security rule, it might have inadvertently blocked outbound requests. Disabling the cloud firewall temporarily can help isolate whether the blockage is internal or external. For additional hardening considerations, review Understanding Ubuntu 22.04 VPS Security to understand how kernel modules and firewall policies interact.

DNS Resolution and Proxy Settings

Curl failures often stem from Domain Name System (DNS) resolution errors rather than network connectivity issues. If you can ping an IP address but not a domain name, your DNS configuration is flawed. Test this by pinging 8.8.8.8 versus google.com. If the IP works but the domain does not, edit your /etc/resolv.conf file or configure systemd-resolved to use reliable DNS servers like Google's 8.8.8.8 or Cloudflare's 1.1.1.1. Additionally, corporate or proxied environments may require curl to route through a proxy server. If your VPS is behind a proxy, curl will fail unless you specify the proxy details. You can set environment variables for the current session:

export http_proxy=http://proxy.example.com:8080
export https_proxy=http://proxy.example.com:8080

Alternatively, configure curl globally by editing ~/.curlrc or /etc/curl.conf and adding the proxy line. If you encounter SSL certificate errors when using curl, ensure that the ca-certificates package is up to date by running sudo apt install --reinstall ca-certificates. This ensures that curl trusts the root certificates required for HTTPS connections.

Testing with Verbose Output

When standard troubleshooting steps do not resolve the issue, enable verbose mode in curl to get detailed diagnostics. Run your curl command with the -v flag:

curl -v https://example.com

This output provides a step-by-step breakdown of the connection process, including DNS resolution, TCP handshake, TLS negotiation, and HTTP request/response headers. Look for specific error codes such as Could not resolve host (DNS issue), Connection refused (firewall/proxy issue), or SSL certificate problem (certificate trust issue). The verbose output is invaluable for pinpointing exactly where the communication chain breaks.

Frequently Asked Questions

Why does curl work with an IP but not a domain name?

This indicates a DNS resolution failure rather than a network connectivity problem. Your VPS cannot translate domain names into IP addresses, so you should check your /etc/resolv.conf settings or switch to public DNS servers like Google or Cloudflare.

How do I check if DigitalOcean Cloud Firewall is blocking curl?

Navigate to the DigitalOcean Control Panel, go to Networking, and select Firewalls. Ensure your droplet is associated with a firewall rule that allows outbound traffic on ports 80 (HTTP) and 443 (HTTPS). Temporarily removing the firewall association can help verify if it is the source of the block.

What should I do if curl reports SSL certificate errors?

Update your system's CA certificates by running sudo apt install --reinstall ca-certificates. This refreshes the trusted root certificate store, allowing curl to validate HTTPS connections properly. You can also bypass verification for testing purposes using the -k flag, but this is not recommended for production.

Can a missing default gateway cause curl to fail?

Yes, without a default gateway, your VPS cannot route traffic to external networks. Verify your routing table with ip route show and ensure a default route exists. If it is missing, you may need to reconfigure your network interfaces or reboot the droplet to restore proper routing.

How do I configure curl to use a proxy server?

You can set the http_proxy and https_proxy environment variables in your shell session or add them to ~/.bashrc for persistence. Alternatively, create a .curlrc file in your home directory and add the line proxy = http://proxy.example.com:8080 to apply the setting globally for all curl commands.