# Delta Chat on TAILS

**URL:** <https://support.delta.chat/t/delta-chat-on-tails/3703>\
**Category:** Mutual Help\
**Created:** [April 8, 2025, 6:01pm UTC](https://support.delta.chat/t/delta-chat-on-tails/3703 "2025-04-08T18:01:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Avoca](https://support.delta.chat/user_avatar/support.delta.chat/avoca/32/2577_2.png) [@Avoca](https://support.delta.chat/u/Avoca)\
**Post date:** [April 8, 2025, 6:01pm UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/1 "2025-04-08T18:01:13Z")

</div>

Has anyone managed to run DC on a TAILS install in Persistent mode?

I have followed the 4 step guide from this forum, and the app runs OK, but returns a “connection refused: error OS 111” message when trying to establish a link.

Any ideas greatly appreciated.

---

<div class="post-metadata">

**Author:** ![link2xt](https://support.delta.chat/user_avatar/support.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://support.delta.chat/u/link2xt)\
**Post date:** [April 8, 2025, 6:30pm UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/2 "2025-04-08T18:30:27Z")

</div>

The guide is available on

> **[How to Setup Delta Chat on Tails in 4 Steps](https://lefherz.net/2022/08/28/how-to-setup-delta-chat-on-tails-in-4-steps/)**
>
> Delta Chat is a messenger which writes emails, so you can write to any email user. It also supports easy encryption via Autocrypt. But how to use it on an anonymous Tails stick?

Maybe try `socks5://127.0.0.1:9050` instead of `socks5://localhost:9050`.  
I have just tried, at least on non-tails Linux `socks5://localhost:9050` works with Tor for me.

---

<div class="post-metadata">

**Author:** ![Avoca](https://support.delta.chat/user_avatar/support.delta.chat/avoca/32/2577_2.png) [@Avoca](https://support.delta.chat/u/Avoca)\
**Post date:** [April 8, 2025, 10:40pm UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/3 "2025-04-08T22:40:20Z")

</div>

Awesome. Works fine, thanks.

The only issue is, if you are trying to create a new, stealth, Profile, you have to choose the “USE OTHER SERVER” option, then “CLASSIC E-MAIL LOGIN” then the “+ Advanced” option, toggle “Use Proxy”, and fill in the SOCKS5 proxy details there. It took a bit of fiddling but eventually worked. And, the settings are Persistent.

This is great because Session’s LOKINET doesn’t work with TOR, Signal is useless without a SIM and, the pre-loaded PIDGEN is horrible and vulnerable to attacks.

Well done Delta Chat team, a great addition to my tinfoil-hat existence.

And, thanks to link2xt. Cheers.

---

<div class="post-metadata">

**Author:** ![link2xt](https://support.delta.chat/user_avatar/support.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://support.delta.chat/u/link2xt)\
**Post date:** [April 9, 2025, 1:45am UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/4 "2025-04-09T01:45:48Z")

</div>

Proxy settings should be outside of the login settings. This is already done on Android, but not on Desktop:

> <https://github.com/deltachat/deltachat-desktop/issues/4124>
>
> With core release 1.143.0 old \`socks5\_\*\` settings are deprecated and \`proxy\_\*\` s…hould be used instead.
> 
> This should be done when done is updated from 1.142.x.
> 
> https://github.com/deltachat/deltachat-android/pull/3292 gives an idea how the screen looks like in Android
> 
> Step 1
> \- \[x\] Change Setting Types: socks5\_enabled, socks5\_host, socks5\_port, socks5\_user, socks5\_password =\> proxy\_enabled, proxy\_url
> \- \[x\] Adapt form: One text field for one proxy\_url (placeholder: "Enter proxy URL here"
> \- \[x\] UI: Show explaining text: "Supported proxy types: HTTP(S), SOCKS5 and Shadowsocks"
> 
> Step 2 (in separate PR)
> \- \[\] UI: add client side validation
> \- \[\] UI: Show connectivity status & proxy type
> \- \[\] UI: enable multiple proxy url entries
> \- \[\] if a proxy is clicked/selected/added, enable "use proxy" toggle
> 
> Step 3 (in separate PR)
> \- \[\] Proxy UI should also be moved out of configuration and into a separate screen like done on Android: https://github.com/deltachat/deltachat-android/pull/3277
> 
> !\[new-proxy-settings\](https://github.com/user-attachments/assets/b7585feb-5595-4930-ba8d-16b93c206ba9)
> 
> Sharing is probably not necessary on desktop

---

<div class="post-metadata">

**Author:** ![Avoca](https://support.delta.chat/user_avatar/support.delta.chat/avoca/32/2577_2.png) [@Avoca](https://support.delta.chat/u/Avoca)\
**Post date:** [April 9, 2025, 2:02am UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/5 "2025-04-09T02:02:13Z")

</div>

Yeah, I noticed the difference between my LineageOS Samsung s9 and the Linux version’s of DC. Cheers.

---

<div class="post-metadata">

**Author:** ![Avoca](https://support.delta.chat/user_avatar/support.delta.chat/avoca/32/2577_2.png) [@Avoca](https://support.delta.chat/u/Avoca)\
**Post date:** [May 30, 2025, 7:19am UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/6 "2025-05-30T07:19:01Z")

</div>

The above procedure has changed.

DC have relocated the proxy settings from the +Advance subsection to the top right option stack of the Main profile creation screen.

Much easier, cheers.

---

<div class="post-metadata">

**Author:** ![r10s](https://support.delta.chat/user_avatar/support.delta.chat/r10s/32/1513_2.png) [@r10s](https://support.delta.chat/u/r10s)\
**Post date:** [October 6, 2026, 3:19pm UTC](https://support.delta.chat/t/delta-chat-on-tails/3703/7 "2026-10-06T15:19:35Z")

</div>


