Jump to content

saitoh183

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by saitoh183

  1. I was trying to setup this drive with the SAS card and it seem to not be detected by it. Then i decided to plug it straight to the motherboard and plugged a 20tb x20 to the SAS card and that was seen no problem and the x22 was seen by the motherboard as well. Does this mean the x22 is not compatible with the LSI card or there is some other configuration i need to do on the card in order to get it to be seen? 

  2. On 9/4/2023 at 11:21 AM, ianstagib said:

    I just came across an issue after restarting my server where mergefs wasn't installing. After some investigation it seems the latest build from mergerfs does not work properly and I solved the problem by adding the previous (and currently listed as latest) version to the tag (line 184). I'm not sure why the latest build is looking for 2.37 but 2.36 is listed by trapexit as latest on his github.

     

    I hope this helps someone escape some frustration and that the problem resolves itself soon..

     

    image.thumb.png.ca93af52139dc51d964d2ac9a6addd98.png

     

    Thanks for this...

  3. 7 hours ago, jonathanm said:

    Working fine here on 3 different boxes. Try setting your VPN_ENABLED to no and see if it allows you to connect. If so, you need to investigate your VPN files and credentials.

    I just tried it and yes it works with vpn off. I just switched to NordVPN and set it to custom. Im on a hetzner box. So i figure it might have something to do with the LAN Network or Firewall setting i need to add maybe? Im not sure what to put in Lan Network and if it is a Firewall, i dont know what rule i would need to add. I know the VPN works as i can get to the webui the docker ip.

     

    Also on a side note, is it normal that the logs show this in repetition?

    2020-02-03 06:27:41,234 DEBG 'watchdog-script' stdout output:
    [debug] iptables chain policies are in place
    2020-02-03 06:27:41,247 DEBG 'watchdog-script' stdout output:
    [debug] VPN IP is 10.7.0.2
    [debug] Deluge IP is 10.7.0.2

     

  4. just pulled latest build

     

    ___.   .__       .__                   
    \_ |__ |__| ____ |  |__   ____ ___  ___
     | __ \|  |/    \|  |  \_/ __ \\  \/  /
     | \_\ \  |   |  \   Y  \  ___/ >    < 
     |___  /__|___|  /___|  /\___  >__/\_ \
         \/        \/     \/     \/      \/
       https://hub.docker.com/u/binhex/
    
    2018-03-16 23:44:38.486664 [info] System information Linux ec1dc240d262 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.30-2~bpo8+1 (2017-06-14) x86_64 GNU/Linux
    2018-03-16 23:44:38.574209 [info] PUID defined as '1000'
    2018-03-16 23:44:38.667035 [warn] PGID not defined (via -e PGID), defaulting to '100'
    2018-03-16 23:44:38.857990 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
    2018-03-16 23:44:38.947159 [info] Permissions already set for volume mappings
    2018-03-16 23:44:39.030368 [info] Setting permissions on files/folders inside container...
    chown: cannot access '/var/lib/nzbhydra2': No such file or directory

    binhex/arch-nzbhydra2: 1.4.7-1-01 works

    • Like 1
    • Upvote 1
  5. 8 hours ago, strike said:

    No, I mean on the remote router, port 58846 needs to be forwarded to your server. I assume you (or someone where your server is located) has forwarded ports on the remote router before. Because in order to get the jwilder nginx container to work port 443 needs to be forwarded to your server, and your container is obviously working so someone must have done it.

    @Spike

    via iptables? I tried a few things in there but to no avail 

     

    iptables -t nat -A PREROUTING -p tcp --dport 58846 -j REDIRECT --to-port 58846
    iptables -A OUTPUT -p tcp --dport 58846 -j ACCEPT
    iptables -A INPUT -p tcp --dport 58846 -j ACCEPT
    iptables --append FORWARD --match tcp --protocol tcp --sport 58846 --dport 58846 --jump ACCEPT

     

  6. 6 hours ago, strike said:

    Also I hope you have set up authentication for your services behind the reverse proxy, or else anybody can mess with them. Specially now when you have published your domain name and all. You might want to get on that asap if you don't have authentication set up.

     

    its not the real domain name :)

  7. If i do a curl localhost:8112 or sub.domain.com:8112 on the server via ssh, I get a response from deluge:

     

    <head>
    <title>Deluge: Web UI 1.3.15</title>
    
    <link rel="shortcut icon" href="/icons/deluge.png" type="image/png" />
    <link rel="icon" href="/icons/deluge.png" type="image/png" />
    <link rel="apple-touch-icon-precomposed" media="screen and (resolution: 163dpi)" href="/icons/apple-pre-57.png" />
    <link rel="apple-touch-icon-precomposed" media="screen and (resolution: 132dpi)" href="/icons/apple-pre-72.png" />
    <link rel="apple-touch-icon-precomposed" media="screen and (resolution: 326dpi)" href="/icons/apple-pre-114.png" />
    
    <!-- Stylesheets -->
    <link rel="stylesheet" type="text/css" href="/css/ext-all-notheme.css" />
    <link rel="stylesheet" type="text/css" href="/themes/css/xtheme-gray.css" />
    <link rel="stylesheet" type="text/css" href="/css/ext-extensions.css" />
    <link rel="stylesheet" type="text/css" href="/css/deluge.css" />
    
    <script type="text/javascript">
    deluge = {
    author: 'Damien Churchill <damoxc@gmail.com>',
    version: '1.3.15',
      .....

     

    but if i do it from my PC i get a timeout. And i cant for the life of me get the 58846 to connect with my Deluge thin client app. but im guessing the 2 problems are related :(

     

    if i run with VPN off everything works ...

  8. 2 minutes ago, strike said:

    I messed with this once a long time ago when I used CP and I remember I had to add a new line on top with my user:pass:10 in order to get it to work, so try that if you don't have any success

     

    Yeah i configure that and restarted the container.

     

    So the RP works but http://wanIP:Port for the webui doesnt work so im guessing WanIP:58846 wont either

  9. @strike

     

     

     

    so i see this in log but i now get the webUI :)

    2018-02-23 14:57:18,146 DEBG 'start-script' stderr output:
    modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-112-generic
    
    2018-02-23 14:57:18,146 DEBG 'start-script' stdout output:
    [warn] Unable to load tun kernel module using modprobe, trying insmod...
    
    2018-02-23 14:57:18,148 DEBG 'start-script' stderr output:
    insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory
    
    2018-02-23 14:57:18,148 DEBG 'start-script' stdout output:
    [warn] Unable to load tun kernel module, assuming its dynamically loaded

    but i still cant get the deluge thin client to connect

  10. 6 minutes ago, strike said:

     

    1 hour ago, saitoh183 said:

    [debug] Deluge IP is 10.x.10.x

     

    is this the same ip listed under IPAddress (look at the bottom) if you run  

    
    docker inspect <ContainerNameOrId>

     see attachement

     

    9 minutes ago, strike said:

    I don't know what distro you're on so maybe the command could be different, google will probably help you then

     

    Ubuntu 16.04

    delugevpn

  11. @strike

     

    2 hours ago, strike said:

    Then I believe you have to forward port 58846 I think you also need the iptable-mangle-something module loaded on the host  (see the delugevpn faq, there will be a message in the log if this is not loaded) Without that you can't connect remotely.

     

    it needs to be installed on host? The FAQ is for unraid but how would i apply this on a normal server machine?

     

    Edit: does this mean it is there?

     

    root@ubuntu:/home/saitoh183# lsmod
    Module                  Size  Used by
    iptable_mangle         16384  1

     

     

    2 hours ago, strike said:

    You also mention the IP 10.x.x.x  is this your machine's IP or are you referring to the docker network? I have never tried docker outside unraid but I believe you don't access the docker with the dockerIP:8112 but the "local machine IP":8112 locally that is.

     

    no this is the delugevpn from the supervisord.log

     

    2018-02-23 12:25:49,246 DEBG 'deluge-script' stdout output:
    [debug] VPN incoming port is 
    [debug] VPN IP is 10.x.10.x
    [debug] Deluge incoming port is 
    [debug] Deluge IP is 10.x.10.x

    the docker network is on 172.17.0.0/16

     

    2 hours ago, strike said:

    You mention radarr (radarr.saitoh183.com), are you running that as a docker too? If so just do what you did with radarr, looks like you did exactly what I mean. It's the same thing

     

    I dont know if you looked at how we enable RP+LE with the jwilder container but basically all i have to do is add env to the container i want to deploy and the nginx-proxy container does the rest. but the rp is for my server ip which is 63.x.x.x (wan) and not for 10.x.x.x which the deluge is running on

     

    so for radarr

     

    docker create \
      --name=radarr \
        -v <path to data>:/config \
        -v <path to data>:/downloads \
        -v <path to data>:/movies \
        -v /etc/localtime:/etc/localtime:ro \
        -e TZ=<timezone> \
        -e VIRTUAL_HOST=radarr.saitoh183.com  \ <--env for jwilder/nginx -->
        -e VIRTUAL_PORT= 7878  \ <--env for jwilder/nginx -->
        -e LETSENCRYPT_HOST=radarr.saitoh183.com  \ <--env for jwilder/nginx -->
        -e LETSENCRYPT_EMAIL=<email>  \  <--env for jwilder/nginx -->
        -p 7878:7878 \
      linuxserver/radarr

    and the jwilder nginx generates:

     

    # radarr.saitoh183.com
    upstream radarr.saitoh183.com {
    				## Can be connect with "bridge" network
    			# radarr
    			server 172.17.0.7:7878;
    }
    server {
    	server_name radarr.saitoh183.com;
    	listen 80 ;
    	access_log /var/log/nginx/access.log vhost;
    	return 301 https://$host$request_uri;
    }
    server {
    	server_name radarr.saitoh183.com;
    	listen 443 ssl http2 ;
    	access_log /var/log/nginx/access.log vhost;
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:!DSS';
    	ssl_prefer_server_ciphers on;
    	ssl_session_timeout 5m;
    	ssl_session_cache shared:SSL:50m;
    	ssl_session_tickets off;
    	ssl_certificate /etc/nginx/certs/radarr.saitoh183.com.crt;
    	ssl_certificate_key /etc/nginx/certs/radarr.saitoh183.com.key;
    	ssl_dhparam /etc/nginx/certs/radarr.saitoh183.com.dhparam.pem;
    	add_header Strict-Transport-Security "max-age=31536000";
    	include /etc/nginx/vhost.d/default;
    	location / {
    		proxy_pass http://radarr.saitoh183.com;
    	}
    }

     

    2 hours ago, wgstarks said:

    There is also a YouTube video that I think is up to date.

     

    @wgstarks

    Thanks i will have a look

     

    @binhex

     

    Maybe you have a solution ?

     

    also here is my supervisord log again

    supervisord.log

  12. @strike

     

    I think there is some confusion with the term thin client. I should have specified Deluge Thin client that is on my local machine at home. :)

     

    3 minutes ago, strike said:

    Should work (if you use this already on the remote server then you must have ports forwarded or else it wouldn't work. You at least need port 443 forwarded to get this to work) 

     

    For sure if i could setup a Reverse proxy using jwilder/nginx-proxy + the LE companion, this would be my preferred solution but i dont know what i need to configure to get it to work with this nginx container. since deluge is on 10.x.x.x, i dont know how it would work since this works with vhost and i just create an A record pointing the server ip to a new url (ie: radarr.saitoh183.com).

     

    I have root access on the machine.

     

    I was able to install openvpn-as and get to the configuration page but i dont know what i need to do next. But if i understand correctly, this will allow me to create a secure connection between me and my home pc which at that point i could get to deluge from my home pc. this could work also but if i could avoid having to do that, i would use this as last resort.

     

    Let me break down my setup, maybe that will help get a clearer picture.

     

    - Machine is hosted at wholesaleinternet

    - Its a Dedicated server so i have full root  with a wan IP so i can SSH to machine.

    - i setup a subdomain pointing to that ip (wsi.saitoh183.com)

    - I installed on that machine Docker and i run delugeVPN + other apps

    - for Reverse proxy im using jwilder/nginx-proxy

    - Ideally i would like to access deluge webui via https://deluge.saitoh183.com or https://wsi.saitoh183.com/deluge but most important is to be able to connect to it via the deluge thin client over port 58846

     

    Im sure im not the first person to have this type of setup. Im sure people that dont have unraid still use this deluge container

     

  13. 59 minutes ago, strike said:

    You'll either have to

    1: Forward 8112 on the remote router, then you can connect to sub.domain.com:8112 but so will everybody else so that's not really secure

    2: Install a docker like openvpn , setup that so you can connect to the whole remote network securely (best option) You will then access deluge via the 10.x.x.x IP

    3. setup a reverse proxy with maybe the let's encrypt docker so you get a ssl certificate on your domain, and setup password authentication with htpasswd. You then access deluge via sub.domain.com/deluge or just sub.domain.com your choice. This can be setup for most dockers (second best option) 

     

    All of them require forwarding ports on the remote router.  

    @strike

    1 isnt possible

    Well i use jwilder/nginx-proxy + the LE companion. I dont know if it is possible with this to achieve point 3. I would like to be able to use my subdomain and i figure it would be the only way to get my thin client to work?

    Doing point 2 seems like the best solution but i do install OpenVPN-AS on the remote machine instead of delugeVPN or im installing so i can access delugevpn from my browser?

    50 minutes ago, wgstarks said:

    Depending on what type remote router you are using you may also be able to install OpenVPN directly on to it to access the remote network securely.

     

    I agree with @strike though. The OpenVPN-AS docker might be the best and easiest solution.

    @wgstarks
    Remote router?  This box is hosted at wholesaleinternet so i dont know

  14. 4 hours ago, wgstarks said:

    How do you access the remote server now to install dockers?

     

    Via WAN IP (which is point to a subdomain). So either open a ssh to the machine and run

     

    docker run -d \
        --cap-add=NET_ADMIN \
        -p 8112:8112 \
        -p 8118:8118 \
        -p 58846:58846 \
        -p 58946:58946 \
        --name=deluge \
        -v deluge_config:/config \
        -v /etc/localtime:/etc/localtime:ro \
        -e VPN_ENABLED=yes \
        -e VPN_USER=<user> \
        -e VPN_PASS=<pass> \
        -e VPN_PROV=custom \
        -e STRICT_PORT_FORWARD=no \
        -e ENABLE_PRIVOXY=no \
        -e LAN_NETWORK=<lan ipv4 network>/<cidr notation> \
        -e NAME_SERVERS=<name server ip(s)> \
        -e DEBUG=<true|false> \
        -e UMASK=<umask for created files> \
        -e PUID=1001 \
        -e PGID=1001 \
        binhex/arch-delugevpn

    or via portainer.

     

    As i said i have it up and running now but i just dont know how i am suppose to connect to it since its on 10.x.x.x and i tried sub.domain.com:8112.

     



     

     

    supervisord.log

  15. Ok so i have it up and running

     

    2018-02-23 00:36:59,526 DEBG 'deluge-script' stdout output:
    [debug] VPN incoming port is 
    [debug] VPN IP is 10.X.10.X
    [debug] Deluge incoming port is 
    [debug] Deluge IP is 10.X.10.X

    So how do i connect to webui and use my thin client from my home pc  (this is a remote dedicated server)

  16. 3 minutes ago, jonathanm said:

    Even if you manage to get it connected, it's not going to work for seeding. That vpn service doesn't support port forwarding.

     

    Oh really?...good to know. I see most say PIA is the way to go...i was just looking to save some money if i could :)

  17. Hi,

     

    I dont use unraid  but i wanted to try this container out on my dedicated server. since i connect to this machine via the external ip, for LAN_NETWORK and NAME_SERVERS what do i put? This is my first time trying to set this up. Also i have a vpn that comes with my usenetserver account so i would be using custom i guess as config.

    Is there some sort of guide or example i can base myself on? i tried to search the topic but 118 pages and random keyword search isnt working out as i would hope.

     

    Thanks :)

     

    Edit: i think my issues is the same as

     

    Edit 2 so i tried it out ...not sure it worked since i cant get to webui (log says that as well) https://paste.ee/p/hwAgE

×
×
  • Create New...