FireFtw

Members
 View Profile  See their activity

  • Posts

    20

  • Joined

  • Last visited

 Content Type 

Posts posted by FireFtw

    [Support] Linuxserver.io - Qbittorrent

    in Docker Containers

    Posted

    On 10/3/2017 at 9:49 PM, Quiks said:

    Are you changing it in the Qbt WEBUI settings or the container?

     

    Edit: I found I had the same issue as you, but was able to figure it out. With the base settings, any time you change the port in the QBT interface, it will reset to 8080 when rebooting the docker.

     

    To fix this, you need 2 changes from the default config.

     

    Remove the original 8080:8080 port map

     

    create a new one 6666:6666 (whatever your new port is)

    add a new variable

    Key: WEBUI_PORT

    Value: 6666 (again, whatever your new port is)

     

    apply this and your UI should now work on the new port.

     

    However, clicking WEBUI on your docker in the UnRaid UI will yield a webpage opening with :8080 which won't load. I'm still trying to figure out how to change the default webpage since it seems hardcoded to 8080.

     

    Hopefully this helps you or anyone else trying to change their port!

     

    edit: I figured out that I had the view on basic. Switched it to advanced, and I can change the default launch URL as well.

     

    That should fix all the issues for everyone.

     

    Woot!

    Bless, for anyone dealing with the "Unauthorized" issue this is the fix. Took way longer than it had any right to.

    [Support] Linuxserver.io - Bookstack

    in Docker Containers

    Posted

    Well after way too much time I realized I'm an idiot and this setup is pretty easy for the letsencrypt container.

     

    Here's your conf file: 

    server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name bookstack.*;

    include /config/nginx/ssl.conf;
	
    client_max_body_size 128M;
	
    location / {
		include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_bookstack bookstack;
        proxy_pass http://$upstream_bookstack:80;
		proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
    }
}

     

    Do NOT enter anything in the docker for "Reverse proxy URL".

     

    DO edit the .env file in /appdata/bookstack/www/.env and UNCOMMENT the "#APP_URL=" as well as put in your domain name including your subdomain prefix.

     

    That's it. However if you're an idiot like me and don't do one of those things it can send you on a long trail of trying to fix something that isn't broken.

    • Like 1

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    I'm having issues getting a few dockers set up.

     

    Booksonic is a strange one, here is my config 

    server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name booksonic.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_booksonic booksonic;
        proxy_pass http://$upstream_booksonic:4040;
    }
}

    Which gives me this when I actually try and navigate to it

    lsJZpck.png

     

    Clicking on the link actually brings me to where I want to be

    rhOpgak.png

     

    the webUI for the docker has it set to http://10.0.0.10:4040/booksonic which gets redirected like it should, but how to set up the equivalent with nginx or a DNS config I don't know.

     

    Then we have gotify, which doesn't work at all. I just get a bad gateway. 

    server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name gotify.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_gotify gotify;
        proxy_pass http://$upstream_gotify:1400;
    }
}

    6ETb5Dd.png

     

    This is regular docker container, not one that was setup for unraid. Not sure if that means there's something to set up that I don't know about.

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    Here's an interesting one.

     

    I would like to run MineOS through this too so I can close the ports I need open for it. I don't care about the web interface, just so ports 25565-25575 get passed on to the docker, no URL stuff. I don't know nearly enough about nginx to come up with the solution on my own and I can't find much for references to base it off of. Any ideas?

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    13 hours ago, saarg said:

    If you are using our calibre container, have the containers on their own custom bridge, you are using the wrong port. It's either 8080 or 8081.

    When using the name to resolve the container, you need to use the ports internally in the containers.

    Yep, forgot I didn't have the bridge swapped over. The internal and external ports are both 8083 on the newest docker.

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    Still looking for a working calibre subdomain config file. I have: 

    server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name calibre.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_calibre calibre;
        proxy_max_temp_file_size 2048m;
        proxy_pass http://$upstream_calibre:8083;
    }
}

    with my calibre docker named 'calibre', however accessing the site gives me a bad gateway error. Any ideas?

    [Support] cheesemarathons repo

    in Docker Containers

    Posted

    6 hours ago, cheesemarathon said:

    @FireFtw When signups are disabled, the Create Account button will still appear and you can click on it and fill out the form. However, when you click the submit button to create a new account, it should say "Registration not allowed"

     

    If your still having issues, make sure the container is up to date. Also, try recreating the container. I had an issue where I had changed SIGNUPS_ALLOWED to false but not saved it properly so it didn't recreate the container and a restart didn't apply the change. So you can just remove the "e" in false and retype it, thus making a change so the Apply button is enabled but keeping the settings the same. Then click Apply to recreate the container with the new settings. I hope that makes sense.

     

    Let me know if you're still having issues.

    Thanks for the reply, my bad I thought the button would have disappeared.

    [Support] binhex - rTorrentVPN

    in Docker Containers

    Posted · Edited by FireFtw
    update

    Trying to get rtorrent to execute a script sitting after it's done downloading, is there any reason 

    method.set_key=event.download.finished,filebot,"execute={/home/rtorrent-postprocess.sh,$d.base_path=,$d.name=,$d.custom1=}"

    doesn't seem to work? I gave the script all permissions and the first thing it does is echo into a file so I'm pretty sure it's not being called.

     

    On a separate note I found an interesting (although unfortunately really old) thread on some forums about having deluge handle downloading and then having it pass the download off to rtorrent after it's done. 

    In order to do something like that I would have to be able to, through the docker, point it at a torrent file to import and tell it where to find it. Is something like this currently possible? 

    [Support] Djoss - FileBot

    in Docker Containers

    Posted

    I am having a hard time finding a few things you referenced before with kizer, mainly how to run it from command line (/usr/bin/filebot.sh does not exist) and being able to have a folder run a script automatically after some time. Anywhere you can point me for those?

    [Support] Djoss - FileBot

    in Docker Containers

    Posted

    On 4/18/2018 at 7:35 PM, Djoss said:

    Yes it's definitely possible to have a "watch" folder and I'm planning to do it.  I'm just not sure yet what is the best way: simply call a user-defined script periodically (where the user will have the ability to call the AMC script) or have something more targeted toward the AMC script (where its behaviour is configurable via container settings (environment variables)).

     

    Did a "watch folder" ever get implemented?