# Notice: "Machine doesn't allow incoming Tor connections?"

**URL:** <https://bisq.community/t/notice-machine-doesnt-allow-incoming-tor-connections/11537>\
**Category:** Support\
**Created:** [May 7, 2022, 1:45pm UTC](https://bisq.community/t/notice-machine-doesnt-allow-incoming-tor-connections/11537 "2022-05-07T13:45:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bisquicked](https://bisq.community/letter_avatar/bisquicked/32/5_5575768a8748004e209b776fc1b2916d.png) [@bisquicked](https://bisq.community/u/bisquicked)\
**Post date:** [May 7, 2022, 1:45pm UTC](https://bisq.community/t/notice-machine-doesnt-allow-incoming-tor-connections/11537/1 "2022-05-07T13:45:05Z")

</div>

I just updated Bisq to v1.9.1. Upon first login, I was given a warning that:

> "This machine is not set up to allow incoming Tor connections. This may prevent your offers from being taken. This is common on Whonix/Qubes VMs.

(paraphrasing as I didn’t copy the note and it doesn’t show up anymore)

Before this notice, I’ve completed orders both ways (maker and taker) and had no issues. This flag only came up after updating. To my knowledge, I have not changed anything to my machine, Tor, Bisq, or firewall settings that could have triggered this.

Could someone please help me check if I have Tor configured correctly? Or at least share what triggers this notice to pop up?

Thanks!

---

<div class="post-metadata">

**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\
**Post date:** [May 9, 2022, 7:12am UTC](https://bisq.community/t/notice-machine-doesnt-allow-incoming-tor-connections/11537/2 "2022-05-09T07:12:02Z")

</div>

This is a new check that has been put in place with 1.9.1 specifically, and it was meant as a heads up for those users who indeed had problems at taking and having their offers taken; since you report having successfully worked out trades with previous versions, if nothing else has changed other than you upgrading Bisq, it is possible that was a false positive and you should still be able to trade correctly, which you will be able to verify soon enough I think

---

<div class="post-metadata">

**Author:** ![bisquicked](https://bisq.community/letter_avatar/bisquicked/32/5_5575768a8748004e209b776fc1b2916d.png) [@bisquicked](https://bisq.community/u/bisquicked)\
**Post date:** [May 25, 2022, 4:49pm UTC](https://bisq.community/t/notice-machine-doesnt-allow-incoming-tor-connections/11537/3 "2022-05-25T16:49:27Z")

</div>

Update - I recently completed a trade, so looks like this is a false positive.

---

<div class="post-metadata">

**Author:** ![w000000t](https://bisq.community/user_avatar/bisq.community/w000000t/32/3124_2.png) [@w000000t](https://bisq.community/u/w000000t)\
**Post date:** [May 30, 2022, 9:45am UTC](https://bisq.community/t/notice-machine-doesnt-allow-incoming-tor-connections/11537/4 "2022-05-30T09:45:29Z")

</div>

Indeed, the first algo used to check this was open to false positives, new approach should overcome this.