# Bastion socks working but getting :cognitect.anomalies/not-found

**URL:** <https://forum.datomic.com/t/bastion-socks-working-but-getting-cognitect-anomalies-not-found/443>\
**Category:** Datomic Cloud\
**Created:** [May 29, 2018, 2:47pm UTC](https://forum.datomic.com/t/bastion-socks-working-but-getting-cognitect-anomalies-not-found/443 "2018-05-29T14:47:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![emiller](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/emiller/32/167_2.png) [@emiller](https://forum.datomic.com/u/emiller)\
**Post date:** [May 29, 2018, 2:47pm UTC](https://forum.datomic.com/t/bastion-socks-working-but-getting-cognitect-anomalies-not-found/443/1 "2018-05-29T14:47:14Z")

</div>

Posting this here just in case others run into it. Perhaps this could also be added to the troubleshooting docs.

I had created an AWS instance of Datomic Cloud and run the socks connection to Bastion. I’d also verified that the socks connection worked by running the curl command specified in the documentation [on this page](https://docs.datomic.com/cloud/getting-started/connecting.html).

However, when I tried to connect I got an error `:cognitect.anomalies/not-found...`. The problem turned out to be that I had an error in my connection config. I’d omitted the `:proxy-port` setting. Took me a while to figure it out because the error didn’t give much detail.

Perhaps the troubleshooting docs could also give some advice – if any is to be had – for debugging AWS failures like this. Are there ways (logs, .e.g) of getting a bit more information about what may be wrong?

---

<div class="post-metadata">

**Author:** ![sparkofreason](https://avatars.discourse-cdn.com/v4/letter/s/8dc957/32.png) [@sparkofreason](https://forum.datomic.com/u/sparkofreason)\
**Post date:** [May 29, 2018, 5:10pm UTC](https://forum.datomic.com/t/bastion-socks-working-but-getting-cognitect-anomalies-not-found/443/2 "2018-05-29T17:10:24Z")

</div>

I had the same problem, but because I was guessing the proxy used port 22. Would be helpful it the docs just showed the default of 8182.

---

<div class="post-metadata">

**Author:** ![marshall](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.datomic.com/marshall/32/48_2.png) [@marshall](https://forum.datomic.com/u/marshall)\
**Post date:** [June 4, 2018, 12:58pm UTC](https://forum.datomic.com/t/bastion-socks-working-but-getting-cognitect-anomalies-not-found/443/3 "2018-06-04T12:58:28Z")

</div>

Thanks for the suggestion.  
I will look into adding this specific failure mode to the troubleshooting page of the docs.