# DevKinsta keep showing error cannot resolve host

**URL:** https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770
**Category:** Questions
**Created:** [November 22, 2023, 11:25am UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770 "2023-11-22T11:25:29Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![martinjankov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/martinjankov/32/2712_2.png) [@martinjankov](https://community.kinsta.com/u/martinjankov)
#### Post date: [November 22, 2023, 11:25am UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770/1 "2023-11-22T11:25:29Z")

</div>

Could not connect to activation server (cURL error 6: Could not resolve host: [connect.advancedcustomfields.com](http://connect.advancedcustomfields.com)).

I keep getting these kind of errors whenever I need to connect to some external host.  
This is just one of the hosts cannot resolve. Others are google apis, ontraport api.  
I have to manually map the IP to host in devkinsta\_fpm /etc/hosts file.

Anyway to resolve this so I don’t have to map it all the time because whenever the Docker is getting update that /etc/hosts file is overwritten to the default and I need to enter things again?

---

<div class="post-metadata">

### Author: ![Alessandro](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/alessandro/32/2310_2.png) [@Alessandro](https://community.kinsta.com/u/Alessandro)
#### Post date: [November 22, 2023, 1:16pm UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770/2 "2023-11-22T13:16:24Z")

</div>

Hey @martinjankov welcome to Kinsta Community!  
This has happened to me once, restarting the fpm container fixed the issue, in my case for some reason Docker wasn’t able to resolve any domain.  
Have you tried that already?

Regards,  
Alessandro

---

<div class="post-metadata">

### Author: ![martinjankov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/martinjankov/32/2712_2.png) [@martinjankov](https://community.kinsta.com/u/martinjankov)
#### Post date: [November 22, 2023, 2:05pm UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770/3 "2023-11-22T14:05:42Z")

</div>

@Alessandro I tried that, but no success.

---

<div class="post-metadata">

### Author: ![Alessandro](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/alessandro/32/2310_2.png) [@Alessandro](https://community.kinsta.com/u/Alessandro)
#### Post date: [November 22, 2023, 2:55pm UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770/4 "2023-11-22T14:55:28Z")

</div>

When running this command in the fpm container, what do you get as output?

```auto
cat /etc/resolv.conf

```

---

<div class="post-metadata">

### Author: ![Sam\_Benson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/sam_benson/32/2499_2.png) [@Sam\_Benson](https://community.kinsta.com/u/Sam_Benson)
#### Post date: [May 2, 2025, 9:33am UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770/5 "2025-05-02T09:33:24Z")

</div>

I’m having this same issue for all external curl requests.

Here’s the output for my resolv.conf file:

```auto
# Generated by Docker Engine.
# This file can be edited; Docker Engine will not make further changes once it
# has been modified.

nameserver 127.0.0.11
options ndots:0

# Based on host file: '/etc/resolv.conf' (internal resolver)
# ExtServers: [127.0.0.1]
# Overrides: [nameservers]
# Option ndots from: internal

```

---

<div class="post-metadata">

### Author: ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [May 2, 2025, 1:19pm UTC](https://community.kinsta.com/t/devkinsta-keep-showing-error-cannot-resolve-host/2770/6 "2025-05-02T13:19:45Z")

</div>

Hello @Sam_Benson 👋

That looks standard.

Can you please tell me what is the Docker, DevKinsta and operating system version you use?

Also, if possible, can you please provide us with DevKinsta’s main.log as explained here?

> **[Troubleshooting - Error Codes - Kinsta® Docs](https://kinsta.com/docs/devkinsta/devkinsta-troubleshooting/error-codes/#viewing-the-application-log-file)**
>
> Find out what error codes may be returned in DevKinsta, what each of them means, and how you can fix them.

Kind regards!
