Ubuntu server experiencing significant issues
Ubuntu server experiencing significant issues
On a brand-new server setup, try executing: sudo apt update --allow-releaseinfo-change. If this doesn’t resolve the issue, consider updating your sources list to match the correct mirrors. For Ubuntu, open /etc/apt/sources.list using nano and swap outdated links for the latest archive URLs from http://archive.ubuntu.com/ubuntu/. Because it’s headless, all commands will run in the terminal; just wait until the update completes before installing any additional packages.
The file at /cdrom indicates an attempt to update from the installation image. Remove the file if you have physical media. Disable the virtual device using the installation media if it's a VM. Make sure the media isn't included in the sources list provided earlier.
How to move through the nano interface? You attempted to go into nano but couldn't exit or use keyboard shortcuts. Eventually, you had to restart the PC. (Note: I learned how to navigate nano and fixed the archive list correctly. The issue continues—nano is still finding files on removable drives and applying updates.) This is the current error after your attempts.
The default file in /etc/apt/sources.list is /etc/apt/sources.list. The source list for the Ubuntu sources file is located at /etc/apt/sources.list.d/ubuntu.sources. This is the standard configuration from a newly set up virtual machine.
There are questions about continuing with a headless installation, as the user may prefer a GUI or Ubuntu Desktop instead of the server setup. Alternatives include using Debian with Xfce or LXDE, or opting for Mint if you dislike newer features. If you decide to restart from scratch, reinstalling might be the best option.
Edited September 5, 2025 by DraconisMaximus
sudo nano /etc/apt/sources.list and update the entries accordingly. Replace the old references with the archive sources. After saving, execute sudo apt update to ensure proper fetching. It seems your repository links are still pointing to outdated versions. Adjusting to the archive repos should resolve the issue.
Are you sure your network is working? Try these commands to check basic connectivity:
#ping Google DNS (To Test Basic Connectivity) ping -c 5 8.8.8.8
#ping Cloudflare DNS (To Verify Basic Connectivity) ping -c 5 1.1.1.1
#ping Google (To Test DNS Function) ping -c 5 google.com
#ping DuckDuckGo (To Verify DNS Function) ping -c 5 duckduckgo.com