# "Something Bad Happened" - unable to open exclude file

**URL:** https://community.kinsta.com/t/something-bad-happened-unable-to-open-exclude-file/2103
**Category:** Bug Reports
**Created:** [March 3, 2023, 4:39am UTC](https://community.kinsta.com/t/something-bad-happened-unable-to-open-exclude-file/2103 "2023-03-03T04:39:25Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![Agus](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/agus/32/1515_2.png) [@Agus](https://community.kinsta.com/u/Agus)
#### Post date: [March 7, 2023, 6:20am UTC](https://community.kinsta.com/t/something-bad-happened-unable-to-open-exclude-file/2103/11 "2023-03-07T06:20:18Z")

</div>

Thank you for your reply Darryl!

Looks like that symlink method didn’t help either 🤔 , though technically the path/file is accessible/actually there on your local machine.  
Really strange indeed as the error kept showing that error message:

> [terminalExec] Error: rsync: [client] failed to open exclude file /tmp/rsync/rsync\_exclude\_create\_import\_e60ee80476cd48b783ddd7411e47d513.tmp: No such file or directory (2)  
> rsync error: error in file IO (code 11) at exclude.c(1188) [client=3.2.3]

I’m out of idea at the moment, and have just updated asked our internal devs to double check and/or suggest any other idea. Will update you again once we have more information from them.

Cheers,  
Agus

---

_[View the full topic](https://community.kinsta.com/t/something-bad-happened-unable-to-open-exclude-file/2103)._