# "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:** 2
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 3, 2024, 6:18am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/22 "2024-02-03T06:18:25Z")
@devstagr, please check if this warning appears when launching Docker Desktop. If it does, click “Re-apply configurations” to allow DevKinsta to initialize. See the screenshot below for reference:
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 3, 2024, 12:55pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/23 "2024-02-03T12:55:24Z")
That notification already appeared a couple of days ago - already clicked on it to reapply
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 3, 2024, 1:15pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/24 "2024-02-03T13:15:53Z")
@devstagr I’m not sure why but maybe try installing back the previous version, 4.26.1, and make sure you choose the correct Docker Desktop installer for your Mac based on its processor - [Docker Desktop release notes | Docker Docs](https://docs.docker.com/desktop/release-notes/)
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 3, 2024, 4:54pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/27 "2024-02-03T16:54:19Z")
I’m on 4.26.1 already… Maybe I’ll try upgrading to 4.27.1?
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 3, 2024, 4:58pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/28 "2024-02-03T16:58:26Z")
No dice with `4.27.1` either… Wonder whether to go way back to what I originally started on `4.9.1` and see how that goes
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 3, 2024, 5:07pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/29 "2024-02-03T17:07:47Z")
Alright, going back to docker `4.9.1` got devkinsta started again and detecting docker so I now have the port number.
However, now I’m getting `sudo: not found` (tried sudo, Sudo, SUDO…)
Any ideas?
---
### Author:  [@Andrew](https://community.kinsta.com/u/Andrew)
#### Post date: [February 3, 2024, 6:36pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/30 "2024-02-03T18:36:03Z")
Hi @devstagr!
Thank you for your reply, and thank you for providing those details. I do see from the main.log file you shared with me that DevKinsta was originally reporting “[2024-02-01 11:12:32.630] [error] Error - DK0003: DOCKER\_INSTALL\_COMMON\_ERROR: Docker isn’t installed”
It is interesting that downgrading back to Docker 4.9.1 allows DevKinsta to launch. At the moment I’m not able to replicate any issue with the latest Docker version 4.27.1. I will be looking into this further with our team to see what might be causing this issue on your end with newer versions of Docker.
Regarding the sudo issue, may I have details about how and where you are trying to run sudo and seeing this error?
We look forward to hearing back from you!
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 3, 2024, 10:57pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/31 "2024-02-03T22:57:59Z")
Navigating to docker, clicking on the terminal button
Terminal launches, I type in `sudo -su grace` and it errors, as below
---
### Author:  [@Andrew](https://community.kinsta.com/u/Andrew)
#### Post date: [February 4, 2024, 1:33am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/32 "2024-02-04T01:33:23Z")
Thank you for your reply, and sharing those screenshots! By default sudo is not installed in the image. If you’d like to install it manually you may do so by running “apk add sudo”. Please note however that if the image is updated, or redeployed then manually installed packages may need to be reinstalled.
We are continuing to look into the Docker issue to see why DevKinsta is having difficulty locating the Docker installation when you are running an up to date version of Docker. We will be following up as soon as possible once we have more details to share.
Please let us know if you do have any questions in the meantime!
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 4, 2024, 1:54am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/33 "2024-02-04T01:54:26Z")
@devstagr Can you try without sudo? Try doing ’ `su grace` ’ instead. Let me know how it goes.
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 4, 2024, 2:42am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/34 "2024-02-04T02:42:47Z")
`su grace` works, but then command `wp` is not found - presuming that wp cli doesn’t come as standard inside of these docker templates?
Tried to install it via this guide: [Installing – WP-CLI – WordPress.org](https://make.wordpress.org/cli/handbook/guides/installing/) (after firstly running `apk add php`, successfully installing php `8.1.22`)
But end up with this error
`PHP Fatal error: Uncaught Error: Class "Phar" not found in /wp-cli.phar:3`
---
### Author:  [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)
#### Post date: [February 4, 2024, 3:14am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/35 "2024-02-04T03:14:28Z")
Oh please access the terminal inside the devkinsta\_fpm container. As shown on my previous screenshot.
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 4, 2024, 3:49am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/36 "2024-02-04T03:49:35Z")
`Success: Made 0 replacements.`
On the command
`wp search-replace 'https://instancename.local:49729' 'https://instancename.local'`
(also tried with `http://`, and without `https://` all together)
From what I can see in the `wp_options` db table, the site url doesn’t include the port
* * *
On a side note, been trying to start a new instance from scratch, but keep running into this error 😕 - So looks like no working instance anywhere for me still.
---
### Author:  [@Andrew](https://community.kinsta.com/u/Andrew)
#### Post date: [February 4, 2024, 7:41pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/37 "2024-02-04T19:41:09Z")
Hi @devstagr!
I’m sorry to see that you are having difficulty with creating a new site as well using DevKinsta. We certainly want to get to the bottom of what’s causing these issues to occur.
I am going to be escalating this with our development team to help further investigate into what’s causing the Docker issue, and this current issue where you are unable to create a site.
Would it be possible for you to share an updated copy of the main.log file so we may review the error occurring during this site creation please? That will help in our investigation.
We look forward to hearing from you!
---
### Author:  [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [February 5, 2024, 11:30am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/39 "2024-02-05T11:30:14Z")
Our engineers have reviewed the issue and they are not able to say with any certainty what is causing it. However, one of the theories is that your system doesn’t have access to _docker_ commands.
To test this, please try running _which docker_ command. If the command doesn’t work, you should review this thread for a possible solution: [Docker not found when freshly installed on Mac · Issue #6793 · docker/for-mac · GitHub](https://github.com/docker/for-mac/issues/6793)
If the command **does** work, then you can try:
- running Docker as System user
- Enabling default docker socket
- Having a look at permissions
But before trying those, please check if the _which docker_ command works.
Let us know if the above helps.
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 6, 2024, 1:23am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/40 "2024-02-06T01:23:19Z")
> [@VladimirM](#):
>
> which docker
Presuming this means it works
> - running Docker as System user
> - Enabling default docker socket
> - Having a look at permissions
This is a little above my knowledge level as I’ve never really set up a docker container before - (hence using DevKinsta…) - could you walk me through this a little?
Appreciate all the help!
---
### Author:  [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [February 6, 2024, 11:13am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/42 "2024-02-06T11:13:13Z")
Our engineers are still suspecting some sort of permissions issue.
You could also try running e.g. `docker --version` just to see if the user you’re logged in with has the permission to execute `docker` from the CLI.
Also, can you please recheck and make sure that in Advanced Docker Desktop settings everything is set as per this screenshot:
Kind regards
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 8, 2024, 3:42pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/43 "2024-02-08T15:42:13Z")
```auto
grace@Graces-MacBook-Pro public % docker --version
Docker version 25.0.2, build 29cf629
```
Yep that command works.
Have re-updated to the latest version of docker and set the settings to mimic what you’ve got there, and something has happened…
Will report back
---
### Author:  [@Andrew](https://community.kinsta.com/u/Andrew)
#### Post date: [February 9, 2024, 12:20am UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/44 "2024-02-09T00:20:26Z")
Thank you for the update, @devstagr! We look forward to hearing back from you! 🙂
---
### Author:  [@devstagr](https://community.kinsta.com/u/devstagr)
#### Post date: [February 12, 2024, 1:16pm UTC](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015/45 "2024-02-12T13:16:21Z")
Going through those config updates in docker did /something/ as now my local site runs on `domain.local` without ports, so I presume that fixed the routing issue.
As this was taking too long to sort though, in the meantime I ended up taking the other users advice in this thread and user LocalWP to set up a dev environment ([https://localwp.com/](https://localwp.com/))
This not only works, but performs miles and miles faster than DevKinsta has been for the last while (0.5s page loads vs 20-30 seconds) - related to an issue I reported a long time ago but never actually got properly resolved.
> [@504 Gateway Time-out errors when loading any page in local environment](https://community.kinsta.com/t/504-gateway-time-out-errors-when-loading-any-page-in-local-environment/1570/25):
>
> Sorry for the delay - here’s the screenshot
Because of these changes though a lot of assets/elements in DevKinsta environment have been purged/migrated to the LocalWP env, so the Kinsta one is in a bit of a sorry state now (my own fault!) - but still loads slowly…
I’m probably going to switch to LocalWP at this point because it works, and it’s miles faster when it comes to performance.
I don’t imagine this is the end of my DevKinsta journey as we host everything with Kinsta, but I feel very unenthused to continue trying to use it for the time being, now knowing that the performance issues are related to the software and not the specs of my laptop, and equally how long this took to get things half resolved. Hopefully at some point in the future these issues can be fixed?
[Previous page](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015.md?page=1)
[Next page](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015.md?page=3)