Add torrent dialog doesn't shows options

[metrolan]

Hi!.

I'm a bit confused 

My system: micro-PC Mirabox (headless server, Archlinux arm), qBittorrent version 3.2.0 compiled in the server (qbittorrent-nox)
Using web interface from remote computers.

The problem: it is supposed that clicking the "+" icon, it will drop a dialog where I should find options like path to download the torrent and so, but I get only the dialog you can see in the attached picture

What am I doing wrong?

[ciaobaby]

What am I doing wrong?

Expecting a GUI action to occur when using the web UI.

[metrolan]

What am I doing wrong?

Expecting a GUI action to occur when using the web UI.

Well, then I'm not wrong:
From the wiki:

qBittorrent-nox ships a feature-rich Web UI that is almost identical to qBittorrent graphical user interface.

At least, I'm almost right 
Where can I find the differences?. It seems that there are a few.

[ciaobaby]

Where can I find the differences?. It seems that there are a few.

Also on the Wiki;

https://github.com/qbittorrent/qBittorr ... umentation

[metrolan]

Where can I find the differences?. It seems that there are a few.

Also on the Wiki;

https://github.com/qbittorrent/qBittorr ... umentation

Fine!
Now seriously, it is not exactly what I'm looking for, 'cause I have no plans at the moment to build a WebUI extension or something like that. Anyway, it is a good point to start learning about, but I've installed qBittorrent on my desktop to see the GUI and the differences with WebUI.

So said, I have another question, maybe worth another thread: Is it possible to connect qBittorrent to a remote core?. I mean, not to do this with the current release, but if the code is such that it can be implemented in the future. Something like Deluge does, for example.

[ciaobaby]

Is it possible to connect qBittorrent to a remote core

Define; "Remote core" if you do not mean running the GUI as a 'Thin Client,' for a remote service.

[metrolan]

Is it possible to connect qBittorrent to a remote core

Define; "Remote core" if you do not mean running the GUI as a 'Thin Client,' for a remote service.

Well, something like that. But I think that is easiest to modify qBittorrent to give the possibility to connect GUI to a remote qBittorrent (a --nogui compilation, mainly) than to dettach a completely separate GUI program.