teal77 / trireme

A Deluge thin client for Android. Written in Flutter.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cannot add server

shomilsaini opened this issue · comments

Tried the app.. looks promising but cannot even add server either local or over internet.
Btw still using transdrone so i know server/network setups are ok.

It asks for mandatory username and password and I'm using binhex-delugevpn container which doesnot have that... We only have webui password. Is there a way around? Also my port 58846 is not exposed to internet... Transdrone uses default port 8112 or whatever i map to internet....

This app doesn't use web UI. You can either stick with transdrone or use the thin client setup.
Don't know the specifics of your setup but here's how you do it for regular clients.
https://dev.deluge-torrent.org/wiki/UserGuide/ThinClient

OK that was a little helpful as in I was able to configure on my local network by updating the auth and conf files but that still does not work over the internet.
I port forwarded 58846 on my router to my unraid server and then from server to binhex-delugevpn docker.
I am assuming that has some configuration challenge with letsencrypt docker.

I tried 2 configurations but to no avail.

This is conf-1:

 server {
     listen 58846;
 
     server_name deluge.*;
 
     include /config/nginx/ssl.conf;
 
     client_max_body_size 0;
 
     # enable for ldap auth, fill in ldap details in ldap.conf
     #include /config/nginx/ldap.conf;
 
     location / {
         # enable the next two lines for http auth
         #auth_basic "Restricted";
         #auth_basic_user_file /config/nginx/.htpasswd;
 
         # enable the next two lines for ldap auth
         #auth_request /auth;
         #error_page 401 =200 /login;
 
         include /config/nginx/proxy.conf;
         resolver 127.0.0.11 valid=30s;
         set $upstream_deluge binhex-delugevpn;
         proxy_pass http://$upstream_deluge:58846;
     }
 }

here is configuration 2:

server {
    listen 58846;
    server_name deluge.*;
    location / {
        return 301 https://$host$request_uri;
    }    
}
server {
    listen 58846 ssl;
    server_name deluge.*;
    
    location / {
	# enable the next two lines for http auth
	# auth_basic "Restricted";
	# auth_basic_user_file /config/nginx/.htpasswd;
	proxy_pass http://192.168.XXX.XXX:58846;
    }
}

I don't know about docker and stuff sorry. If the app is working in LAN, then you should consider using ssh tunnel instead of opening up the deluge port to the wider internet.
https://dev.deluge-torrent.org/wiki/UserGuide/ThinClient#CreateSSHTunnel
#7

Ok so the issue with that ssh tunneling is that I'm behind multiple layers from public ip. That sectio. In that document assumes that you are on a machine directly connected to internet via a static ip.
For me the public ip is dynamic and resides with the internet company modem. Behind that i have local network lets say 192.168.xx.xx then my server has that class of ip. Then behind that inside docker i have another layer of network lets say 172.168.xx.xx and delige docker gets one of those on eth0. Also sinve deluge is vpn docker I'm using vpn so actual communication happens over vpn tunnel which is tun0 and there is a loopback lo0.
Any thoughts?

Any thoughts?

Good luck I guess 😄

I personally only use the app in LAN so all this is beyond me.

I have to say I like the app on LAN. But I'm going to have to figure out the remote access part.
Thanks for your efforts. I hope you keep on doing the good work.
Cheers!

Thanks!
I will probably add some kind of warning when users enter the web UI address in a future version.
#29

I would suggest you to add the app in Google play store... also recommended you donot close issues without actually having a solution.

App was in play store at the beginning, but then google banned my account for no reason.
As for this issue there is nothing I can do here.