# "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:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![Adrian\_L](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/adrian_l/32/2810_2.png) [@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")

</div>

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.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/f/f13d16730dff4d26c8cce8d38a22640ae5495539.png)

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.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/8/8d390bc37c955ba94f33ddd2fa31bf33abf9a131.png)

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!

---

_[View the full topic](https://community.kinsta.com/t/this-site-can-t-be-reached-but-adminer-is-still-accessible/3015)._