Unable to use site domain - WP Admin Not Found

Support
1

What issue or error are you experiencing?

When I create a website using site domain I receive an error message saying -

“Heads-up! Local’s router is having trouble starting. (Retry)”

When i click open site it shows up with a logo Bitnami and says “Awesome! WordPress is now installed” Access WordPress.

If I click open WP Admin i am getting a page which says “Not found, The requested URL was not found on this server”.

If I change my preferences to > advanced > router mode > Localhost. Then I am able to open site and WP Admin perfectly fine. But this means its not secure HTTPS.

How can I get the domain site to work?

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

image
image2344×229 23 KB

image
image1708×826 82.6 KB

image
image1240×360 19.5 KB

System Details

  • Local Version: - local-9.0.4-windows

  • Operating System (OS) and OS version: - Windows 11, 64-bit operating system

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)

2024/06/26 09:44:37 [emerg] 4760#19868: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:44:37 [emerg] 4628#4868: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:44:38 [emerg] 17344#17352: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:45:03 [emerg] 19364#19264: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:45:04 [emerg] 11688#15940: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:45:05 [emerg] 1960#1880: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:45:13 [emerg] 9912#16376: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:45:13 [emerg] 15048#21112: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:45:14 [emerg] 18092#18104: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:55:47 [emerg] 17824#12052: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:55:47 [emerg] 4264#11528: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 09:55:48 [emerg] 10324#23076: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:27 [emerg] 12944#2460: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:28 [emerg] 17260#12740: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:28 [emerg] 23288#10084: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:35 [emerg] 7708#8436: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:36 [emerg] 1496#12472: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:36 [emerg] 14420#22892: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:42 [emerg] 14332#18124: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:42 [emerg] 3808#6060: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:43 [emerg] 17572#13952: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:49 [emerg] 12020#20044: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:50 [emerg] 16408#12088: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 10:51:50 [emerg] 23796#16908: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:28 [emerg] 12832#13224: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:29 [emerg] 1364#22948: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:29 [emerg] 14264#5392: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:35 [emerg] 20396#4984: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:36 [emerg] 14864#12496: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:36 [emerg] 22260#22672: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:41 [emerg] 2268#11732: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:42 [emerg] 11080#10268: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:42 [emerg] 13872#23436: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:48 [emerg] 20880#19152: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:49 [emerg] 19812#11204: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2024/06/26 11:06:49 [emerg] 22484#3164: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hi @kirstyhutson1

Do you have any antivirus, security, or firewall applications that could be blocking Local? It looks like from the log it might be having trouble connecting.

More details about troubleshooting this here: Router Mode

Are you running other developer applications simultaneously? That could also cause similar issues. Apps like MAMP, XAMPP, or Docker for example.

You could also check over the items here as well:

3

Hi, No other developer applications running or installed. Antivirus software not blocking application, I uninstalled my antivirus software to check and its still not able to use site domain. Same error "heads-up! locals router is having trouble starting.

4

Are you running this machine with an admin user?

Is this a work/company issued piece of hardware?

5

Personal laptop. I am the administrator on my laptop.

6

It’s tough to say as we’ve covered most of the common culprits here. The fact that you can still only use Localhost and the errors in your log indicate something is still blocking.

You could also try some steps like this for further investigation:

  • Stop all sites that are running in Local

  • Force quit Local

  • (If using Mac) Run the command lsof -nP -iTCP -sTCP:LISTEN

  • (If using Windows) Run the command netstat -ano

What you’ll be looking for here is to see when sites are stopped and Local is properly shut down if there are still programs running on ports 80 and 443. These may be conflicting with Local or the system may be reporting Local is still running.

Once you run that command you should see a list of listening ports. If you see a particular program making use of those ports, you can then kill that process by running sudo kill -9 XXX where XXX is the PID number of that process. (On Windows you will use taskkill /F /pid XXX where XXX is the PID number of that process)

After that, you should be able to retry. Keep us posted if you have any questions or continuing issues.

There are also some more details around this and other troubleshooting steps at this link if needed: Stopping Whatever Is Listening On Port 80.

7

Thank you. I ran the command in windows cmd netstat -ano and looked for what was listing to 80 & 443. It said PID 5500 then i checked the ran the task manager to see under details what the PID 5500 was. It said Apache.exe. So then I searched my PC for apache.exe and found it in a folder called Bitnami. Which is why i was getting that screenshot website called Bitnami. Then I youtubed how to remove it. Turns out it was another local hosting wordpress platform installed on my laptop.

Now uninstalled WP Local Site router is working! Thanks for your help. Got there in the end.

1 Like
8

Glad to hear it @kirstyhutson1! Thank you for sharing the details here for others to find who might run into the same :slight_smile:

9

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.