I was able to install wordpress on Ubuntu 24 and access the admin panel in the browser.…
- User
I was able to install wordpress on Ubuntu 24 and access the admin panel in the browser. Soon after my browser crashed and I had to reboot my PC. Now when I go to https://wordpress.local/, I get: Unable to connect LibreWolf can’t establish a connection to the server at wordpress.local. The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection. If your computer or network is protected by a firewall or proxy, make sure that LibreWolf is permitted to access the web.
- Assistant
Based on your description, it sounds like your WordPress site was working, but after the browser crash and reboot, it's no longer accessible at
https://wordpress.local/. Since this is a local development environment on Ubuntu 24.04, here’s a guided checklist to help you troubleshoot and fix the issue.
✅ General Troubleshooting Steps
1. Check local server (Apache or Nginx) status
Ensure your web server is running after reboot:
Apache:
sudo systemctl status apache2Nginx:
sudo systemctl status nginx👉 If it's not running, start it:
sudo systemctl start apache2 # or nginxAnd optionally enable it to start with system boot:
sudo systemctl enable apache2 # or nginx
2. Check if MySQL/MariaDB is running
WordPress needs a database connection.
sudo systemctl status mysqlStart it if it's not running:
sudo systemctl start mysql
3. Check your
/etc/hostsfileSince
wordpress.localis not a real domain, it needs to be mapped locally.Open the file:
sudo nano /etc/hostsEnsure you have a line like:
127.0.0.1 wordpress.local⚠️ If this line is missing, your browser won't know where to find
wordpress.local.Save and exit (
Ctrl+O,Enter,Ctrl+X).
4. Make sure your site is configured for HTTPS if using
https://Unless you specifically set up SSL certificates (like using
mkcert, Let's Encrypt, etc.), a local site usinghttps://wordpress.localwill not work out of the box.Try this instead:
http://wordpress.localIf it works with HTTP, and not HTTPS, it means no SSL has been set up yet.
🔧 You can either:
- Set up HTTPS locally with tools like
mkcert, or - Stick to
http://for local development.
5. Check Virtual Host Configuration
Check that Apache or Nginx is configured to serve
wordpress.local.For Apache, check for a file in:
/etc/apache2/sites-available/wordpress.local.confMake sure it has something like:
<VirtualHost *:80> ServerName wordpress.local DocumentRoot /var/www/wordpress <Directory /var/www/wordpress> AllowOverride All Require all granted </Directory> </VirtualHost>Enable the site:
sudo a2ensite wordpress.local sudo systemctl reload apache2
6. Check if firewall is blocking traffic
If you have
ufw(Uncomplicated Firewall) enabled:sudo ufw statusIf it's active, allow HTTP/HTTPS:
sudo ufw allow 'Apache Full'
7. Clear DNS cache (rarely needed but can help)
sudo systemd-resolve --flush-cachesAlso try flushing your browser DNS cache or restarting the browser.
8. Browser cache or HTTPS redirection
Your browser may be cached to only try
https://after seeing it once. Try:- Opening in a private window.
- Using a different browser (Firefox, Chrome).
- Removing redirection to HTTPS (if it was enabled in
.htaccessor Apache config).
🔁 Recap Checklist
Check Description ✅ Apache/Nginx Started sudo systemctl status apache2✅ MySQL Started sudo systemctl status mysql✅ /etc/hostshas127.0.0.1 wordpress.local✅ Browser is using http://nothttps://Try http://wordpress.local✅ Virtual Host is configured and enabled Apache/Nginx config valid ✅ Firewall allows HTTP/HTTPS sudo ufw allow 'Apache Full'
Let me know what you find in these steps—we can go deeper as needed.
- Set up HTTPS locally with tools like
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.