aptalca

Community Developer
 View Profile  See their activity

  • Posts

    3064

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by aptalca

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

    in Docker Containers

    Posted

    39 minutes ago, Spoonsy1480 said:

    Just trying to configure my server again after a mishap earlier, I had letsencrypt and changed to swag now I’m trying to start a fresh and I get this
    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Plugins selected: Authenticator standalone, Installer None
    Obtaining a new certificate
    An unexpected error occurred:

    The server will not issue certificates for the identifier :: Error creating new order :: Cannot issue for "lidarr": Domain name needs at least one dot (and 4 more problems. Refer to sub-problems for more information.)

    Please see the logfiles in /var/log/letsencrypt for more details.
    IMPORTANT NOTES:
    - Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.
    ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
    My template is

    Any help would be grateful


    Sent from my iPhone using Tapatalk

    IMG_2165.jpg

    The container thinks your url is set to "lidarr"

     

    Post a full log

    [Support] Linuxserver.io - OpenVPN AS

    in Docker Containers

    Posted

    3 hours ago, Andreas76 said:

    Hello

    I just got openvpnas setup and I am able to connect.  But I am having issues connecting to servers/devices on the internal network when i'm connected to vpn.
    I tried with hostname and IP's.

    Did you add your network subnet to the routing section in the gui settings?

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

    in Docker Containers

    Posted

    9 hours ago, DockX said:

    Beside the HTTP header bug that noone else has (but thanks alot for the effort saarg 🙂 ), I have another question.

     

    Whats the best way to backup Nextcloud? I have read about tar and sql dump but shouldn't it be enough to just copy the config volumes somewhere else?

    Or is the dump and the tar process only to save disk space but both options would work?

    Both would work, but simply copying the mapped folders is sufficient (don't forget mariadb data if you're using that)

    [Support] Linuxserver.io - Heimdall

    in Docker Containers

    Posted

    1 hour ago, SPOautos said:

     

     

    I installed it and its running, however when I go to the Webgui it just opens up another instance of Unraid instead of going to the Heimdall gui

     

    Is it doing that because I need to go in to the config folder and remove "sample" and the rest of these instructions from the blog?.....

    Once the containers are set up, we'll find the file named heimdall.subfolder.conf.sample under letsencrypt's /config/nginx/proxy-confs folder and rename it to heimdall.subfolder.conf. If we look inside that conf file, we'll see that it is set to use location / {, which will cause an issue because there is already a location defined for / inside the default site config for letsencrypt. So we need to edit the default site config at /config/nginx/site-confs/default and comment out the location block for / inside our main server block so it reads:

    #location / { # try_files $uri $uri/ /index.html /index.php?$args =404; #}

    That way, nginx will use the / location block from our heimdall proxy conf instead.

    After that, when we navigate to https://linuxserver-test.com, we'll see the Heimdall interface.

     

    In that section above, the instructions talk about removing "sample" from the "subfolder.conf"......however what about the subdomain.conf file? Does sample need to come off of it as well like I had to do for Sonarr and other? Also, so I need to do anything in the subdomain file so that the custom domain is tied to Heimdall?

     

    Thanks!

    No, only subfolder.

    The subdomain one is for serving it at https://heimdall.mydomain.com

     

    Try connecting to your domain on a cell phone with wifi turned off

    [Support] Linuxserver.io - Heimdall

    in Docker Containers

    Posted

    51 minutes ago, SPOautos said:

    Hey guys, let me start off saying I'm VERY new to Unraid and computers in general. I've got this far with the use of videos and such.

     

    Anyway, I have the reverse proxy setup and everything works great where I can type in my own domain and access Sonarr, Radarr, Nextcloud. I'd like to set up the Heimdall app but I dont know much about it, I have read through the blog that was posted on page 6 of this thread but still have questions.

     

    First, when I install the docker and the ports for http and https are blank, do I just make them up myself and use something that is available....or do I need to use specific ports that relate to SWAG (LetsEncrypt) or something else? 

    If swag and heimdall are on the same custom bridge network, you don't even need to map ports for heimdall as swag will connect directly to the heimdall container over the custom docker bridge network.

    • Like 1

    [Plugin] Linuxserver.io - Unraid Nvidia

    in Plugin Support

    Posted

    4 hours ago, cryzis said:

    This is brand new tone mapping during transcode feature that will be released in the upcoming 10.7.0 release of jellyfin. See PR#3442 . I have been running Jellyfin:unstable and have been waiting to test this out but I guess the image doesn't support OpenCL :(

    Can you exec into the container and install the package "ocl-icd-opencl-dev", restart and see if it works?

    [Plugin] Linuxserver.io - Unraid Nvidia

    in Plugin Support

    Posted

    4 hours ago, cryzis said:

    This is brand new tone mapping during transcode feature that will be released in the upcoming 10.7.0 release of jellyfin. See PR#3442 . I have been running Jellyfin:unstable and have been waiting to test this out but I guess the image doesn't support OpenCL :(

    We'll look into it. It probably just needs some opencl packages added. We have other images that do that.

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

    in Docker Containers

    Posted

    2 hours ago, vurt said:

     

    That fixed it!! Thank you. I still don't understand why it worked previously though.

     

    By "custom docker bridge", do you mean the custom network?

     

    I just looked this up: https://docs.docker.com/network/bridge/

     

    After running the command 

    
$ docker network create my-net

    Do I then use the unRAID GUI to edit all my dockers' config to point Network Type to "my–net" instead of "bridge"? Would that be it or are there other stuff I need to do?

     

    My Emby is currently set to "Host", will that stay that way?

    Yes on my-net

     

    Emby can stay on host, in which case you have to put the ip in the upstream app variable. Or you can switch to my-net and keep the proxy conf as is.

    [Plugin] Linuxserver.io - Unraid Nvidia

    in Plugin Support

    Posted

    2 hours ago, cryzis said:

    Looking for a little help, I am seeing this within my Jellyfin container. I am passing through the gpu properly, but I enabled a new tone mapping feature that requires OpenCL. This should work right?

      

    
[AVHWDeviceContext @ 0x561dcd631340] Failed to get number of OpenCL platforms: -1001. 
Device creation failed: -19. Failed to set value 'opencl=ocl:0.0' for option 'init_hw_device': No such device 
Error parsing global options: No such device

     

    Screen Shot 2020-09-27 at 3.17.10 PM.png

    I don't think the image supports opencl. What feature is that?

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

    in Docker Containers

    Posted

    20 hours ago, vurt said:

    Thanks for suggesting that, I never knew there's a sample in there.

     

    But I'm still getting the same 502 Bad Gateway error. I'm beginning to suspect it might be Calibre-Web. Someone on Reddit is also getting the same error when his/her reverse proxy worked fine before.

     

    This is what I just tried based on the conf included in swag:

      

    
location /calibre {
    return 301 $scheme://$host/calibre/;
}

location ^~ /calibre/ {
    # 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, also customize and enable ldap.conf in the default conf
    #auth_request /auth;
    #error_page 401 =200 /ldaplogin;

    # enable for Authelia, also enable authelia-server.conf in the default site config
    #include /config/nginx/authelia-location.conf;

    resolver 192.168.1.252 valid=30s;
    set $upstream_app calibre;
    set $upstream_port 8083;
    set $upstream_proto http;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    proxy_set_header Host $http_host;
    proxy_set_header X-Scheme $scheme;
    proxy_set_header X-Script-Name /calibre;
}

     

    That's for calibre, not calibre-web

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

    in Docker Containers

    Posted

    40 minutes ago, Odessa said:

    Tried moving from Letsencrypt to Swag and everything broke. I stopped Letsencrypt, backed up the appdata folder, grabbed Swag from Apps, pointing to same appdata folder. Installation failed and docker won't start:

     

    root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='swag' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'EMAIL'='' -e 'URL'='[subdomain].duckdns.org' -e 'SUBDOMAINS'='www,[subdomain],' -e 'ONLY_SUBDOMAINS'='true' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'EXTRA_DOMAINS'='' -e 'STAGING'='false' -e 'DUCKDNSTOKEN'='b9911192-b13a-47ab-af33-d7bdd992eeb4' -e 'PROPAGATION'='' -e 'PUID'='99' -e 'PGID'='100' -p '80:80/tcp' -p '443:443/tcp' -v '/mnt/user/appdata/swag':'/config':'rw' --cap-add=NET_ADMIN 'linuxserver/swag' 

    da4142bafd8f2a88b1126a24f5c3eadfec3f49c1d4722a816e6e2d5efb6b567a
    /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint swag (8e3934ee2265f3ef9ebccbc5025f08609d479db4f7f030de27d366bb9f904aeb): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use.

    Port 80 in use, likely by unraid

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

    in Docker Containers

    Posted

    14 hours ago, joghurt said:

    Thx, I followed the instructions and deleted the conf files. The most of the log entry disappeared. 👍

    Last message left is the system warning:

     

    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

     

    Is there anything I could do on this? Many thx in advance,

    That's just an alert and is harmless

    • Like 1

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

    in Docker Containers

    Posted

    4 minutes ago, joghurt said:

    Hi, this is my first post, I am still new in unraid, sorry for mybe non-professionel question.

    I tried to migrate my running let'sencrypt docker to swag like described, so far so good. all is running.

     

    but in the logs i can see the following and I hope you can advice me what has to be done.

     

    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

     


    nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

     

    no field package.preload['resty.core']
    no file './resty/core.lua'
    no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
    no file '/usr/local/share/lua/5.1/resty/core.lua'
    no file '/usr/local/share/lua/5.1/resty/core/init.lua'
    no file '/usr/share/lua/5.1/resty/core.lua'
    no file '/usr/share/lua/5.1/resty/core/init.lua'
    no file '/usr/share/lua/common/resty/core.lua'
    no file '/usr/share/lua/common/resty/core/init.lua'
    no file './resty/core.so'
    no file '/usr/local/lib/lua/5.1/resty/core.so'
    no file '/usr/lib/lua/5.1/resty/core.so'
    no file '/usr/local/lib/lua/5.1/loadall.so'
    no file './resty.so'
    no file '/usr/local/lib/lua/5.1/resty.so'
    no file '/usr/lib/lua/5.1/resty.so'
    no file '/usr/local/lib/lua/5.1/loadall.so')
    Server ready

     

    Thx in advance.

     

    Some of your conf files are really old. Delete them and restart the container. Those are including nginx.conf, proxy.conf, ssl.conf, etc.

    • Like 1

    [Support] Linuxserver.io - Code-server

    in Docker Containers

    Posted

    5 hours ago, dharrah said:

    Both - same results either way
    As I look at the browser console logs, I see a few errors:

    WebSocket handshake - error 200
    WebSocket closed with status code 1006

    I still have the stock proxy-confs file in place - no changes were made. But the fact that I get the login page at my domain address seems to indicate that the SWAG portion of things is "fine". 

     

     

    codeserverError.png

    Make sure your nginx confs (ssl, proxy, nginx, etc.) are up to date. If you didn't customize them, you can delete them and restart the container. There was recently a change regarding websockets.

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

    in Docker Containers

    Posted

    1 hour ago, SPOautos said:

     

    Does that mean something is wrong with the CNAME?  I made the Host Name sonarr.s2white.com and the points to value is a duckdns.org address that points to my server IP

     

    In the linuxserver link you shared (thank you for that).....I see where it says this....

     

    "Nextcloud is a bit trickier because the app has various security measures built-in, forcing us to configure certain options manually.

    As with the other examples, let's make sure that we have a CNAME for nextcloud set up on our dns provider (a wildcard CNAME * will also cover this) and it is pointing to our A record that points to our server IP. If we are using the docker cli method, we also need to create the user defined bridge network (here named lsio) as described above. For DuckDNS, we do not need to create CNAMES, as all sub-subdomains automatically point to the same IP as our custom subdomain, but we need to make sure that it is the correct IP address for our server. We also need to make sure that port 443 on our router is forwarded to the correct port on our server."

     

    To be honest I'm not sure what all that means to what I have already done.  Have things changed since the SI video where I should now use a A record instead of a Cname and point it directly to my server ip address instead of a duckdns address?

     

    So is this saying that instead of doing it the way SI shows, I now need to make a single Cname like Nextcloud.mydomain.com that points to a A record that I also create at Godaddy which in turn points to my servers IP address, then basically dont do anything with DuckDNS?  I do have my router set to reserve the IP address so I think that means it will always keep that domain so I dont really NEED DuckDNS I dont THINK....but I'm not positive about how all that works.

    I'm not the author of that video and am not familiar with it. You'll have to contact the author.

    All the info we publish is in the github/docker hub readme (linked in the first post) and the docs article I linked above.

     

    Typically, if you already own your own domain name, you don't need duckdns. Duckdns is a free alternative to owning a domain name.

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

    in Docker Containers

    Posted

    15 minutes ago, SPOautos said:

    UPDATE to my last post - I went ahead and "applied" those settings I mentioned above.....

    "Currently I used my newly purchased Domain Name in the domain field, added the sub's, then dont have anything in the field asking for a DuckDNS tocken.....but I'm not wanting to move past this screen unless I know its correct because if all this doesnt work at the end, I will have NO idea where to look. So I REALLLLY want to get it right as I go though all of this."

     

    BUT in the logs all of the challanges failed. It seems like it was looking for a A record where I created CNames....is that why? With the A record though you have to point it to a IP address, it wont let me point it to a Duckdns address.

     

    Could this be because I just purchased the domain and created the Cnames about 2-3 hours ago? Does it need more time? Or do I just have the settings wrong?

     

    Here is the SWAG log.....

     

    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    [s6-init] ensuring user provided files have correct perms...exited 0.
    [fix-attrs.d] applying ownership & permissions fixes...
    [fix-attrs.d] done.
    [cont-init.d] executing container initialization scripts...
    [cont-init.d] 01-envfile: executing...
    [cont-init.d] 01-envfile: exited 0.
    [cont-init.d] 10-adduser: executing...

    -------------------------------------
    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/


    Brought to you by linuxserver.io
    -------------------------------------

    To support the app dev(s) visit:
    Certbot: https://supporters.eff.org/donate/support-work-on-certbot

    To support LSIO projects visit:
    https://www.linuxserver.io/donate/
    -------------------------------------
    GID/UID
    -------------------------------------

    User uid: 99
    User gid: 100
    -------------------------------------

    [cont-init.d] 10-adduser: exited 0.
    [cont-init.d] 20-config: executing...
    [cont-init.d] 20-config: exited 0.
    [cont-init.d] 30-keygen: executing...
    using keys found in /config/keys
    [cont-init.d] 30-keygen: exited 0.
    [cont-init.d] 50-config: executing...
    Variables set:
    PUID=99
    PGID=100
    TZ=America/Chicago
    URL=s2white.com
    SUBDOMAINS=server,sonarr,radarr,lidarr,nextcloud
    EXTRA_DOMAINS=
    ONLY_SUBDOMAINS=false
    VALIDATION=http
    DNSPLUGIN=
    [email protected]
    STAGING=false

    SUBDOMAINS entered, processing
    SUBDOMAINS entered, processing
    Sub-domains processed are: -d server.s2white.com -d sonarr.s2white.com -d radarr.s2white.com -d lidarr.s2white.com -d nextcloud.s2white.com
    E-mail address entered: [email protected]
    http validation is selected
    Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
    Generating new certificate
    Saving debug log to /var/log/letsencrypt/letsencrypt.log
    Plugins selected: Authenticator standalone, Installer None
    Obtaining a new certificate
    Performing the following challenges:
    http-01 challenge for lidarr.s2white.com
    http-01 challenge for nextcloud.s2white.com
    http-01 challenge for radarr.s2white.com
    http-01 challenge for s2white.com
    http-01 challenge for server.s2white.com
    http-01 challenge for sonarr.s2white.com
    Waiting for verification...
    Challenge failed for domain lidarr.s2white.com
    Challenge failed for domain nextcloud.s2white.com
    Challenge failed for domain radarr.s2white.com
    Challenge failed for domain s2white.com
    Challenge failed for domain server.s2white.com
    Challenge failed for domain sonarr.s2white.com
    http-01 challenge for lidarr.s2white.com
    http-01 challenge for nextcloud.s2white.com
    http-01 challenge for radarr.s2white.com
    http-01 challenge for s2white.com
    http-01 challenge for server.s2white.com
    http-01 challenge for sonarr.s2white.com
    Cleaning up challenges
    Some challenges have failed.
    IMPORTANT NOTES:
    - The following errors were reported by the server:

    Domain: lidarr.s2white.com
    Type: dns
    Detail: DNS problem: NXDOMAIN looking up A for lidarr.s2white.com -
    check that a DNS record exists for this domain

    Domain: nextcloud.s2white.com
    Type: dns
    Detail: DNS problem: NXDOMAIN looking up A for
    nextcloud.s2white.com - check that a DNS record exists for this



    Domain: radarr.s2white.com
    Type: dns
    Detail: DNS problem: NXDOMAIN looking up A for radarr.s2white.com -
    check that a DNS record exists for this domain

    Domain: server.s2white.com
    Type: dns
    Detail: DNS problem: NXDOMAIN looking up A for server.s2white.com -
    check that a DNS record exists for this domain

    Domain: sonarr.s2white.com
    Type: dns
    Detail: DNS problem: NXDOMAIN looking up A for sonarr.s2white.com -
    check that a DNS record exists for this domain
    - The following errors were reported by the server:

    Domain: s2white.com
    Type: unauthorized
    Detail: Invalid response from
    http://s2white.com/.well-known/acme-challenge/II7qAGyVqDFhBJ7WLQg2obnFCDxtWDqCxANhUwOgLVM
    [34.102.136.180]: "<!doctype html><html lang=\"en\"><head><meta
    http-equiv=\"content-type\"
    content=\"text/html;charset=utf-8\"><meta name=\"viewport\" con"

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address.
    - Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.
    ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

    This needs to return an ip address: https://dnschecker.org/#A/sonarr.s2white.com

     

    See here for details setup info: https://docs.linuxserver.io/general/swag

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

    in Docker Containers

    Posted

    22 minutes ago, blaine07 said:


    Thank you for the thorough response! (I won’t call you asshole BUT ironically that’s my wife’s favorite for me, tooemoji1787.png).

    Sounds like we all have the same first name 😅

     

    The only potential issue I'm aware of is in nextcloud's config.php where you allow a proxy. You'd have to change that to swag if you change the container name (and if you reverse proxy nextcloud)