How to fix: WordPress not opening on localhost:8080 after port change from 80 to 8080 (HTTP 404 Not Found error)

WordPress not opening on localhost:8080 after port change from 80 to 8080
Opening a WordPress site after Apache port change returns HTTP 404 error (Not Found). This is a common issue with  WordPress users who have installed WordPress on local machine, then had to change the Apache HTTP port since other programs took over the HTTP port 80.

Here is a scenario for the issue:
Read more »

XAMPP Apache Service fails to start due to blocked port: Error: Apache Shutdown Unexpectedly -may be due to blocked port, missing dependencies, improper privileges, or shutdown by another method

XAMPP Apache Service not starting due to blocked port
Today, the Apache service installed with XAMPP shutdown on me. The following error was displayed on the XAMPP Control Panel -
Apache service not starting Shutdown Unexpectedly -may be due to blocked port
"Error: Apache Shutdown Unexpectedly -may be due to blocked port, missing dependencies, improper privileges, a crash, or shutdown by another method".
Check the Apache error logs which shows -
[Fri Oct 03 07:41:34.188511 2014] [ssl:warn] [pid 404:tid 400] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Oct 03 07:41:34.360389 2014] [ssl:warn] [pid 404:tid 400] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
Let's see how to resolve this issue.
Read more »
Back To Top