# DK0066 - \[error\] Error - DK0066: IMPORT\_DB\_DUMP: Error (1): YERROR 1130 (HY000): Host 'XXXXX' is not allowed to connect to this MariaDB server

**URL:** <https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830>\
**Category:** Community Guides\
**Created:** [December 14, 2025, 9:22am UTC](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830 "2025-12-14T09:22:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![itibook](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/itibook/32/5277_2.png) [@itibook](https://community.kinsta.com/u/itibook)\
**Post date:** [December 14, 2025, 9:22am UTC](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830/1 "2025-12-14T09:22:00Z")

</div>

Dear all,

this one drove me nuts for a bit so writing this here for everyone, but especially for me 🙂

I was getting the DK0066 error like many experienced.

**1-** First issue was a normal site creation in DevKinsta. I fixed this by following this thread: [Something bad happened: in create new site - #17 by StormChild](https://community.kinsta.com/t/something-bad-happened-in-create-new-site/2190/17)

**2-** I then faced a similar issue when importing a site from Kinsta. I was getting an error and when looking into the main.log file I saw the error

**[error]**  **Error** - DK0066: IMPORT\_DB\_DUMP: **Error** (1): YERROR 1130 (HY000): Host ‘172.172.0.5’ is not allowed to connect to this MariaDB server

I solved this one as follows:

The error “Host ‘172.172.0.5’ is not allowed to connect to this MariaDB server” indicates a MySQL/MariaDB privilege issue where the specified host (likely the web server or FPM container in DevKinsta’s Docker network) does not have the necessary permissions to connect to the database server

To fix this, you need to grant the correct privileges to the database user. The best approach involves accessing the database container via the command line and updating the user permissions.

**Solution Steps**

1. **Access the Database Container:**  
Open your terminal or command prompt and run the following command to get a bash shell inside your DevKinsta database container:

2. **Log in to MariaDB:**  
Once inside the container, log in to the MariaDB server using the root user. When prompted for a password, use the database password found in the DevKinsta UI for that site.

3. **Grant Remote Access Privileges:**  
Inside the MySQL shell, you need to grant privileges to your user, allowing connections from any host (represented by `%`). Replace `'your_database_password'` with the actual password from DevKinsta.

4. **Exit MySQL and Restart the Container:**  
Type `exit;` to leave the MySQL shell, and then type `exit` again to leave the Docker container’s bash session.Restart your `devkinsta_db` container using your Docker desktop application or the command line for the changes to take effect.

5. **Retry the Import:**  
Go back to DevKinsta and try the database import again. The error should now be resolved.

---

<div class="post-metadata">

**Author:** ![ShawnC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/shawnc/32/880_2.png) [@ShawnC](https://community.kinsta.com/u/ShawnC)\
**Post date:** [December 15, 2025, 3:18am UTC](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830/2 "2025-12-15T03:18:41Z")

</div>

Howdy @itibook 👋 ,

I see this is your first time posting, so welcome to the community.

You brought the 🔥 on your first post!

Thank you kindly not only for your generosity, but also for those immaculate instructions (with beautiful formatting).

Personally, I have not encountered this issue, but if/when I’ve ever do, I’ve bookmarked this thread and will follow our instructions.

Again, thank you for sharing and contributing to the community.

kindly,

Shawn C.

---

<div class="post-metadata">

**Author:** ![kitcsltg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kitcsltg/32/5437_2.png) [@kitcsltg](https://community.kinsta.com/u/kitcsltg)\
**Post date:** [February 26, 2026, 9:49am UTC](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830/3 "2026-02-26T09:49:54Z")

</div>

Thank you so much, that fixed it.

---

<div class="post-metadata">

**Author:** ![garyfutch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/garyfutch/32/5569_2.png) [@garyfutch](https://community.kinsta.com/u/garyfutch)\
**Post date:** [May 20, 2026, 2:00pm UTC](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830/4 "2026-05-20T14:00:03Z")

</div>

This is basically a MariaDB permissions issue inside DevKinsta’s Docker network. The database user exists, but MariaDB only allows connections from certain hosts, so when the import container tries connecting from something like `172.172.0.5`, it gets blocked with error 1130.

Your fix is correct. Granting privileges to `root@'%'` or specifically to the Docker container IP allows the import process to authenticate properly. In Docker setups this happens pretty often because containers communicate over internal bridge networks and MariaDB treats each container IP as a separate host.

One thing I’d recommend though is avoiding `root@'%'` long term if possible. Better to create a dedicated DevKinsta user with only the permissions needed for imports. Safer and avoids weird permission issues later.

Also, if imports keep failing even after fixing permissions, it’s worth checking whether the SQL dump itself is damaged or incomplete. Sometimes failed exports or interrupted imports can corrupt tables, and in those cases try third party tools like Stellar Repair for MySQL can help recover damaged MySQL/MariaDB databases before re-importing them.

---

<div class="post-metadata">

**Author:** ![merineth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/merineth/32/3022_2.png) [@merineth](https://community.kinsta.com/u/merineth)\
**Post date:** [May 21, 2026, 3:41am UTC](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830/5 "2026-05-21T03:41:05Z")

</div>

@garyfutch, welcome to the Kinsta community, and thank you so much for sharing your input and recommendations. They’re truly appreciated and will definitely be helpful.

Have a great day!
