Closed dbermond closed 4 years ago
This means the dns rebinding protection works. see https://en.wikipedia.org/wiki/DNS_rebinding
solution with ssh tunnel would be to bind XD's rpc to loopback address whenever used over a ssh.
Using 127.0.0.1
makes the console interface to work on a remote machine but blocks the webui to be accessed remotely. In this way, it looks like that only one type of user interface have to be chosen when doing remote access.
Is there a way to use both the web and console interfaces on a remote machine at the same time like it's possible on a local machine?
you could put XD's webui behind nginx or apache.
It works nice by placing XD behind nginx with the host setted to 127.0.0.1
, making it also to work at the console. Thanks for the tip.
Since this is by design I will close this issue.
Maybe adding an option for listening on all interfaces like setting to it 0.0.0.0
would be a good idea. Please consider.
Thanks for making this torrent client.
info
git revision / version: git master (currently at XD-0.3.3-d79ff87)
OS: Arch Linux
Architecture: x86_64
problem
The console interface does not work when XD is running at a remote machine (for example, at remote IP
192.168.1.74
). Settingbind
to192.168.1.74:1488
andhost
to192.168.1.74
at the config file makes the webui to work, but breaks the console interface, which makes it unsuitable for scripting and secure access over ssh.Can the console interface be used alongside the webui when running at a remote machine? This works nice on a local machine.
backtrace / error messages
Error messages: yes
When experimenting with different values in the
bind
andhost
options it also does not work. Here are the outputs, adding alsocurl
to test the webui:Backtrace: no