You can read shamael's post here regarding this subject: viewtopic.php?t=54995

I'm glad to hear that and you're very much welcome mate Thanks likewise for reporting back, and your post

I'm presuming you're running deluged/deluge-web from the default provided systemd-services of deluge arch repo package, so running under an unpriveleged 'deluge' user - check if a permission issue, which i'm guessing, by running e..g 'sudo -u deluge touch <dir>\foo', where '<dir>' is changed to the ...

To the two with synology errors, I think you're using deluge2 with py2, as seen such from other synology users here before, and maybe this is entirely unrelated but saw quickly an old report about python 2.6/7 not supporting something with abspath when non ascii chars in directory or down it's path,...

Sorry, that is frustrating :( I saw your thread on arch forum, and hope you get response there, but without any logging suggesting any error whatsoever, then am not to confident sadly, but could get lucky of-course if someone in the know. I'm too using arch with systemd-networkd/wpa_supplicant(thoug...

BTW, you could also run without systemd and without deluge-user, just to remove some variables in the trouble-shooting, so add deluged and deluge-web to e.g. .xinitrc(no -d switch or anything) if always using xorg, or .zshrc/.zprofile or whatever wanted startup sourced file, and then delete your ~/....

Cool, hope you find a solution. BTW, not an arch general issue atleast, since I'm on that also, sorry if not being too clear on that. Good luck.

I'm sorry i'm at complete loss towards why happens, hopefully others have some troubleshooting advice to you. I just checked again and cannot reproduce and started fresh and rebotted several times. My deluged log is much much longer than yours - yours is cutoff in a fraction of the real log, so seem...

If there's not more in that log, then the daemon isnt running imho - did you check as per my last reply? A running deluged daemon outputs alot more than those few lines, e.g which port bound to etc etc.

Listen_interfaces is most important yes, i.e it's this which is used for announcing that IP(or IP of device) to tracker/swarm, but might as well also bind the other libtorrent option outgoing_interfaces imho when available. Atleast on deluge2 it worked same, if using IP or device, and is libtorrent,...