# "This site can’t be reached", but adminer is still accessible
**URL:** https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015
**Category:** Application Support
**Created:** [January 31, 2024, 6:09am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015 "2024-01-31T06:09:31Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [January 31, 2024, 6:09am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/1 "2024-01-31T06:09:31Z")
Been trying to fathom this one, but it has been an issue since I updated from Monterey to Sonoma just over a week ago.
Environment seems to start, and this is shown by some happy containers inside of docker
But, for whatever reason, the local routing seems to be invalid as my usual site.local domain is returning a ‘This site can’t be reached’ error. I’m wondering if the local ports/certs got reset somehow in the upgrade?
I have tried changing the TLD inside of devkinsta in an effort to refresh those but to no avail.
Have already done the obvious, restart devkinsta, restart docker, restart laptop.
---
### Author:  [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [January 31, 2024, 7:47am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/2 "2024-01-31T07:47:22Z")
Hello **devstagr** 👋
I’m sorry to hear you’re having troubles using DevKinsta.
If you’re certain that the issue happened after the OS update, it’s possible that some aspect of has changed with the update.
The first thing I would advise checking is the **hosts** file. Check if there are entries for your local sites that are pointing to ::1 or 127.0.0.1. For example:
::1 mysite.local
::1 www.mysite.local
127.0.0.1 mysite.local
127.0.0.1 www.mysite.local
If you check the hosts file and it looks good, but you still have the issue, please provide:
- the exact OS version
- Docker version
- DevKinsta version
Kind regards!
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [January 31, 2024, 10:26am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/3 "2024-01-31T10:26:55Z")
Seems to be in there…
OS: 14.2.1
Docker: 4.9.1
DevKinsta: 2.12.1
```auto
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
# Added by Docker Desktop
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section
#### START DEVKINSTA entries
127.0.0.1 site.local
127.0.0.1 www.site.local
::1 site.local
::1 www.site.local
#### END DEVKINSTA entries
```
---
### Author:  [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [January 31, 2024, 11:56am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/4 "2024-01-31T11:56:03Z")
The docker version is a bit out of date. I use 4.26.1 and I haven’t been able to replicate this issue.
If applicable, could you try updating Docker to 4.26.1 or 4;27 to test?
Kind regards
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [January 31, 2024, 3:02pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/5 "2024-01-31T15:02:30Z")
Hmmm - it says I’m up to date, and the ‘check for updates’ button is disabled. Will try downloading a new version manually
---
### Author:  [@dw4y](https://community.kinsta.com/u/dw4y)
#### Post date: [January 31, 2024, 4:52pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/6 "2024-01-31T16:52:23Z")
Same problem here. All websites are unreachable since the 2.13 update.
Docker is up to date (4.27). DevKinsta containers are all 1.3.5.
Nothing wrong in /etc/hosts. I’m on MacOS 14.3.
Now devkinsta tries to load websites via a port, ie : [https://mywebsite.local:51209](https://mywebsite.local:51209)
This is very problematic for lots of us, I litterally can’t work ☹
The error displayed is : PR\_CONNECT\_RESET\_ERROR and then after a reload PR\_END\_OF\_FILE\_ERROR
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [January 31, 2024, 5:12pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/7 "2024-01-31T17:12:15Z")
Yea, same with the port issue. Reinstalled docker and no dice. And yes, equally cannot work right now
---
### Author:  [@dw4y](https://community.kinsta.com/u/dw4y)
#### Post date: [January 31, 2024, 5:19pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/8 "2024-01-31T17:19:52Z")
I’ve also tried to create a new personnalized website, but it never ends installation.
No “Wordpress” part in the site détails (to activate WP\_DEBUG for example).
Everything is broken…
I think I’ll use LocalWP, I’m tired of devKinsta chaotic development.
---
### Author:  [@dw4y](https://community.kinsta.com/u/dw4y)
#### Post date: [January 31, 2024, 11:26pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/9 "2024-01-31T23:26:10Z")
I’ve removed entirely DevKinsta and Docker using CleanMyMac to ease the process.
Then reinstalled Docker (v4.26.1, not 4.27), reinstalled DevKinsta (it tooks ages to prepare containers, maybe 20mn).
Creating a new personnalized website works again, but just close DevKinsta and Docker, then restart Docker : it says the config has been changed by a software, and want to apply default config :
If you don’t apply, DevKinsta don’t boot and get stuck at “Updating dockers containers”.
If you apply, DevKinsta starts, but websites are again not reachable…
Still stuck.
Please provide previous working version of DevKinsta 2.12.1 !
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 1, 2024, 1:40am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/10 "2024-02-01T01:40:19Z")
Mmmm not tried any of this specifically, but have done a range of installs/uninstalls/downloading new environments, all to no avail and failure to load any sites. Would really appreciate some guidance here as I can’t do my job properly without a local environment… And I’d really rather not have to reset my entire teams workflow because of this
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 1, 2024, 3:43am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/11 "2024-02-01T03:43:34Z")
Hey!
We understand that some of you may be facing a frustrating issue, and we want to assure you that we’re here to help. We’re currently investigating the problem, but unfortunately, we haven’t been able to replicate it on Mac OS Sonoma with the latest version of DesKinsta 2.13.0.
We know how frustrating this can be, but we believe that the issue may be related to the local DNS resolver of the machine rather that the app. If you have added your site’s local domains to the local host file, we kindly request that you try clearing the DNS cache by referring to this link: [How to Flush DNS Cache (Windows, Mac, Chrome, Linux)](https://kinsta.com/knowledgebase/flush-dns/#macos).
We also suggest adding a new WP site to refresh the machine’s host file and validating the local DNS by pinging the domain.
Please let us know if the issue persists after trying the above suggested troubleshooting.
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 1, 2024, 4:13am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/12 "2024-02-01T04:13:58Z")
Also, to prevent the DevKinsta app from using random open ports to the site, you can uncheck the “Auto Detect” box located in the Port selector section within the DevKinsta settings. Instead, you can set port 80 for HTTP and port 443 for HTTPS. This ensures that the assigned ports remain constant.
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 1, 2024, 11:04am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/13 "2024-02-01T11:04:40Z")
Done this, but now running into a different issue…
You can see Docker is installed (and running) in the background. Starting up DevKinsta with Docker closed returns the same result
---
### Author:  [@dw4y](https://community.kinsta.com/u/dw4y)
#### Post date: [February 1, 2024, 6:09pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/14 "2024-02-01T18:09:13Z")
Thx @Adrian_L for your answer.
I’ve already done what you suggest, but with no success.
Still, removing Docker + DevKinsta, reinstall them, start them, Add 1 site properly with https, but if I close DevKinsta and Docker and restart them, nothing works, like described in first posts…
Anyway, I’ve moved to LocalWP, it’s more complete, stable, powerful and uses 500Mo of RAM where Docker + Devkinsta uses 3Go+…
---
### Author:  [@Andrew](https://community.kinsta.com/u/Andrew)
#### Post date: [February 2, 2024, 1:28am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/15 "2024-02-02T01:28:01Z")
@devstagr I’m sorry to see that you are now having difficulty with launching DevKinsta. I can imagine this is frustrating, and I understand how important DevKinsta is to your workflow.
I would like to see what is happening during the launch process that is causing DevKinsta not to be able to detect Docker. To do this, I’d like to take a look at the main.log file. Could you please send me a direct message with the main.log file attached? You can locate this file under /Users/username/Library/Logs/DevKinsta
@dw4y I’m sorry to hear that you have moved on to another application. If you would like to give us another chance we are standing by and happy to help. You may also send a copy of the main.log file to me as a direct message and I would be happy to take a look into it to see what errors are occurring if you are interested.
Best regards
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 2, 2024, 11:17am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/17 "2024-02-02T11:17:35Z")
Hi Andrew - sent across my log file
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 2, 2024, 12:08pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/18 "2024-02-02T12:08:16Z")
Hi @devstagr @dw4y
After trying different versions of DevKinta and Docker Desktop, I believe I think I managed to replicate the issue. It appears that the problem is related to the URL containing a custom port. Even if the “Auto Detect” box in the Port selector section in DevKinsta Settings is unchecked and port 80 and 443 are set for HTTP and HTTPS respectively, the site URL can still have the custom port included when loaded. In this case, it is needed to perform a search and replace in the site’s database to update the URL.
In my case, I was getting the following error message, so I needed to do a search and replace in the database.
I used the Docker Desktop terminal to run Search and Replace in the site’s database using WP CLI. Alternatively, you could also do the search and replace through the Database Manager UI directly in DevKinsta.
Search: [https://migrationproject.local:49467](https://migrationproject.local:49467)
Replace with: [https://migrationproject.local](https://migrationproject.local)
To use WP CLI in the terminal, I had to create an ssh user as WP CLI doesnt work with root.
1. Add ssh user:
`adduser adrian`
2. Switch user to adrian
`sudo -su adrian`
3. Go to the the directory where the site’s wp files are ipwnstalled
`cd /www/kinsta/public/migrationproject`
4. Then finally, run search and replace:
`wp search-replace 'https://migrationproject.local:49467' 'https://migrationproject.local'`
After that, my site already became accessible.
I hope it helps!
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 2, 2024, 6:54pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/19 "2024-02-02T18:54:23Z")
Hmm, the command ‘Adduser’ isn’t found when running it through the docker terminal. Is there something I’ve got to do before that point?
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 2, 2024, 10:40pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/20 "2024-02-02T22:40:05Z")
@devstagr Oh sorry, please try all lower case `adduser` .
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 3, 2024, 2:28am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/21 "2024-02-03T02:28:10Z")
omg I can’t believe I was that foolish! haha, got the user added now…
Although I have no idea what the port is as now DevKinsta refuses to start since you said to upgrade docker…
[Next page](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015.md?page=2)