saarg

Community Developer
  • Posts

    5374
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by saarg

  1. 7 hours ago, Sinister said:

    Sorry if this has been covered but i could not find my specific error message, I thought i was going to be a smart guy and try to add hardware transcoding to plex. It would not start after the setup, i followed youtube guide to the T after finishing plex would not start and when checking the logs i get

     

    Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE

     

     

     

    here is a screenshot of docker i am using

     

    Please help i dont want to set it up all over again

     

    Plex Screwed.PNG

     

     

    Looks like your database is corrupt. Cache disk full or any other issues?

  2. 2 hours ago, juaaslo said:

     

    Thanks for answering. Just to explain myself, I arrived here from Linuxserver.io - MariaDB docker hub site, following the "Discord - realtime support / chat with the community and the team." link, and when arrived here I see in the first post "[Support] Linuxserver.io - MariaDB", which is exactly the docker image I have, so I thought it was the correct place to get support about my docker image and configuration. I am sorry I didn't even know what Unraid was, so for this particular case, and in order to avoid annoying posts like mine from people trying to follow the stones, I recommend this is explained more clearly in docker hub site, specifying that the proposed link is to get support only for users of a concrete OS and not the image itself.

    Sorry again, and BR!

     

    I'm not sure how you managed to get to the unraid forum by clicking on the discord link on mariadbs docker hub page? It takes you to an invite link for our Discord server and does not point to this forum.

  3. On 9/2/2021 at 11:48 PM, thomas said:

    @linuxserver.io

    Lately I have some CVE attacks on my Unraid due to Nextcloud container using nginx v1.18.0. The attacks are being blocked by Netgear Armor (Bitdefender) and I only receive a notification that it was blocked and it says there is a vulnerability due to nginx v1.18.0.

     

    Is there a way to update nginx to a newer/secure version?

     

    Thanks

    Screenshot from 2021-09-02 17-46-31.png

     

    Our nextcloud container use version 1.20.1 of nginx, so update your container. If its updated, it's not our nextcloud container that is the issue.

     

    • Like 1
  4. 4 hours ago, gnpunk said:

    Hello everyone.

     

    I'm trying to get Dynamic DNS set up via ddclient, but I'm hitting a bit of a wall. I thought I had everything set up but the "Data" section in my Google Domains is not updating.

     

    Here is what I have in my config file:

     

    daemon=300

    syslog=yes

    pid=/var/run/ddclient/ddclient.pid

    ssl=yes

    protocol=googledomains

    login=[generated login by GD]

    password=[generated pw by GD]

    my private server info

     

    Log file from Unraid is as follows:

     

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


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

    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] 30-config: executing...
    [cont-init.d] 30-config: exited 0.
    [cont-init.d] 90-custom-folders: executing...
    [cont-init.d] 90-custom-folders: exited 0.
    [cont-init.d] 99-custom-files: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-files: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    Setting up watches.
    [services.d] done.
    Watches established.
    WARNING: found neither ipv4 nor ipv6 address

    You have left out the part where you tell ddclient how to check for th IP. Check the default config file for the options.

  5. 3 hours ago, Squid said:

    What about MakeMKV-GUI?

     

    Someone pulled it two hours ago, so apparently someone is using it. But I have not updated it in at least a year. And I think there was a breaking change so couldn't update it without upgrading the baseimage.

    You even asked in the thread if you should remove it from CA and I said yes 🙂

     

     

  6. 3 hours ago, greenflash24 said:

    I have created a fork of the linuxserver container, and i will try to maintain this container in the future (at least until the builds break again). Therefore I and others can have security fixes for a bit longer at least.

     

    You can find a mirror of my fork here: https://github.com/fabianbees/docker-openvpn-as

    Docker images will be pushed here: https://hub.docker.com/r/fabianbees/openvpn-as

     

    I have not found time yet to update the Readme.md and change the dockerimage to point to my image instad of the linuxserver one, but this will be done in the future.

    As i don't use jenkins in my homelab i just added some build-scrips, so i can build this image with gitlab-ci on my private gitlab instance.

     

    For now my image has the latest version of openvpn-as, which is version 2.9.2 at this time. (Linuxserver has 2.9.0)

     

     

    If you want to switch to my docker image, you can do so my changing the image-repository in unraid from

    
    linuxserver/openvpn-as

    to

    
    fabianbees/openvpn-as

     

     

    But please make a backup of your appdata first, before changing to the new image just in case something goes wrong.

    Please remove references to linuxserver.io so it's clear the container is not released by or supported by us.

  7. 8 hours ago, darkrom said:

     

     

    Thank you for all the work done first of all.

    I just want to clarify that means there will likely be security fixes that do not end up here eventually?  I need openVPN due to Wireguard being blocked on many networks etc.  So perhaps the best thing to do would be use this for now since it works great, use Wireguard when I can, and setup openvpn configured some other way to get the updates?  I just would hate to run something as critical as a VPN without any future patches.

    We will not release any updates at all.

  8. 3 hours ago, CrashnBrn said:

    My initial thought would be something like mkvinfo

     

    or even something like 

     

     

    But I'm not sure if you can display all files with either of those

     

    My mkvtoolnix container is dead. So no point using it.

  9. 9 hours ago, blaine07 said:


    Is that a new thing this specific build, 71, is “looking for” since it has been an issue before out of curiosity?

    (I’m gonna spot check a few of my Confs to see how many it may be issue with before I upgrade…)

    The log says which proxy confs has the issue. No need to go through all configs.

     

    Alpine was updated from 3.13 to 3.14 and nginx also and they changed some things.

    • Like 1
  10. 8 hours ago, jortan said:

     

    I have a very basic setup and I've just experienced this as well - all sites returning:

     

    
    refused to connect.

     

    Nothing logged in access.log or error.log

     

    something broke between:

    1.17.0-ls70 and

    1.17.0-ls71

     

    For anyone else seeing this, edit swag docker and change repo to:

     

    
    linuxserver/swag:1.17.0-ls70

     

    No need to pull an earlier version. Just comment out the proxy_redirect off; statement in all confs nginx complains about.

    • Thanks 2
  11. 11 hours ago, Marioawe said:

    I apologize for the long post, running into two issues. I'll start with my main, more important one since it's a security issue. 

     

    I have SWAG set up on my unRAID box and it seems to run fine, except for the fact I can't get it to work correctly for it's main purpose. I have a few docker containers I have going through SWAG, but to access them, I have to punch a hole through my firewall for them, and include the port in the address. My address for Home Assistant, for example, would end up looking like http://ha.mydomain.com:8123. I know this is a big hole I leave in my network, and the reason SWAG exists, but I can't seem to get the set up for this correct, and the documentation I can find doesn't seem to help. My end goal is to patch up the holes I put in my firewall, and clean up the address so the above link would appear as https://ha.mydomain.com instead. 

     

    I'm not sure what all I should include to help diagnose my issue, but I'm more than willing to provide my set up.

     

    -------

     

    My second issue, I ran into while attempting to get the first issue fixed. Whenever I attempt to access a site, I can't access it within my own network (ex, while I'm on my desktop, or connected to Wi-Fi), but I can access it if I'm not on my network (ex, mobile data, friend's Wi-Fi).

     

    I'm not quite sure why this ended up happening, but again, whatever you guys need out of my set up to help diagnose it, I'll be more than happy to provide.

     

    Thanks in advance and again, I apologize for the giant wall of text.

    You have not configured your proxy-confs correctly if you have to use the port. The container needs to have the same name as in upstream_app in the proxy conf and all lowercase. You also need to remove the sample part from the file name.

    For this to work you need to create a custom bridge and add swag and set all the containers you reverse proxy to use that bridge.

    As it is now you are not going through Swag.

     

    The second issue has nothing to do with swag, but your router. You need to find out if it supports hairpinning or split DNS.

     

    Do you get the default welcome page if you just go to your domain?

  12. 17 hours ago, HH0718 said:

    Has anyone tried using this as a TFTP server?

    I have it installed and running on the right ports.

    However, when I try to get a file from the untracked list using a tftp command, I can't seem to get the file.

    Example on windows tftp client (firewall configured too):

     

    
    C:\Windows\system32>tftp -i 172.16.0.2 get /assets/test.txt
     Connect request failed

     

    I have also tried without the `/assets/` portion

     

    The file is there but can't seem to get it to download from any tftp on any device.... windows 10, cisco wlcs, cisco switches, etc.

    Any thoughts?

     

     

    That doesn't seem to be the correct IP. That looks like the internal docker bridge network IP

  13. 6 hours ago, sjaak said:

    is here someone who got SWAG fully working on IPv6? i trying to get it working but after view weeks of trail and error i'm out of idea's...

    Docker is fully working on IPv6, can confirm this. i have a tor relay running on unraid/docker and it external accessible through IPv6...

    SWAG does have an working IPv6 address. but Cloudflare won't get connection to SWAG on IPv6, resulting many times with error 522

     

    i did some research on nginx with ipv6, its needs '--with-ipv6'? when checking on SWAG with the command: nginx -V it gives me the following configure arguments:

     

    no --with-ipv6 in there...

    anyone have in idea what i can do???

     

    You can't add it yourself. We use the packages from the alpine repo.

  14. 6 hours ago, Unrayed said:

    Cheers, I've got this far with Unraid but cron is something I've no experience of (other than a predefined user script to shut the server down for me at night.) Is the file to control this a global file, or specific to each docker? I'm comfortable editing, & using a cron calculator to figure out what time I'd like, I just don't know what to actually edit! Would appreciate any help you might throw my way :)

     

    EDIT:

    I'm looking at the file located at /mnt/cache/appdata/swag/crontabs/root

     

    Using Notepad++, I can open this file on Windows and it shows:

     

    
    # do daily/weekly/monthly maintenance
    # min   hour    day     month   weekday command
    */15    *       *       *       *       run-parts /etc/periodic/15min
    0       *       *       *       *       run-parts /etc/periodic/hourly
    0       2       *       *       *       run-parts /etc/periodic/daily
    0       3       *       *       6       run-parts /etc/periodic/weekly
    0       5       1       *       *       run-parts /etc/periodic/monthly
    # renew letsencrypt certs
    8       2       *       *       *       /app/le-renew.sh >> /config/log/letsencrypt/letsencrypt.log 2>&1

     

    Is it case of editing one of these values, to change renewal time from the default of 2am to a time of my choosing?

    Yes I think you can just edot the file and set the time to when your server is on. Restart the container after modifying the file.

    • Like 1
  15. 9 hours ago, Unrayed said:

    Hi all,

     

    Basic setup is Unraid 6.9.2 with the Swag docker installed and running away perfectly (I use it for a reverse proxy for my family to use Unraid, having followed SpaceInvaderOne's guide to set up.) The docker itself works perfectly, My family and I can access my Emby library from on and off the lan (duckdns used also.) However, I received an email recently from [email protected], stating my Swag certificates were expiring soon. 

     

    My server turns off every evening at midnight, and starts back up every day at 16:00, so having googled this problem, most advice was that simply restarting the Swag docker would renew the certs (obviously this isn't happening for me, as my whole server restarts daily.) 

     

    I found some info which allowed me to renew my certificates manually, by using the following instructions:

    
    Open console for the specific docker (Swag) by clicking the docker name, and then choosing the console.
    Type: certbot renew

     

    ^^ This seems to have resolved the issue of the cert not renewing automatically. However I'm concerned that I'll have to do this every few months & maybe forget altogether. So my question is this, how on earth can I automate the renewal myself? I can access the terminal through the Unraid GUI, but after that I'm lost. I'm comfortable typing in commands, but automating this process is a step beyond my knowledge. 

     

    I have the User Scripts plugin installed, and I use this to shutdown my system every night. As for how I'd use this plugin though to automate cert renewal, I'm not sure. I think I'd have to write a script, and then point to that script in the plugin & then set the schedule? Can anyone help?

     

    EDIT:

     

    This is from my Swag docker log

     

    
    [cont-init.d] 60-renew: executing...
    The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
    [cont-init.d] 60-renew: exited 0.

     

    So perhaps the docker is set to renew automatically at 02:08 - and therein lies the problem because my Server is offline at that time?

    You either need to modify when the Cron job is running or leave your server running.

  16. 2 hours ago, Cytomax said:

    Sorry i thought this was for all the linuxserver.io containers... 

     

    im just running it in a manjaro box using docker... 

     

    So i figured it out... 

    1.16.0-ls67 and 1.16.0-ls68 dont work for me

    1.16.0-ls66 does work for me...

     

    Something changed between 

    1.16.0-ls66 and 

    1.16.0-ls67 that causes the container to crash 

     

    Hopefully its just me and its not some bigger problem... 

    https://linuxserver.io/support

  17. 25 minutes ago, Cytomax said:

    I want to start by saying letsencrypt/swag is amazing and i have been running it successfully for the last couple years....

    i usually update every few weeks or so...
    i ran an update today like normal... no recent config changes... and the container keeps crashing... 

    i backed up the container and made a new folder to start from scratch and the container keeps crashing....

    Here are the logs... no idea what to do now....

     

     


     -------------------------------------
    swag              |           _         ()
    swag              |          | |  ___   _    __
    swag              |          | | / __| | |  /  \ 
    swag              |          | | \__ \ | | | () |
    swag              |          |_| |___/ |_|  \__/
    swag              | 
    swag              | 
    swag              | Brought to you by linuxserver.io
    swag              | -------------------------------------
    swag              | 
    swag              | To support the app dev(s) visit:
    swag              | Certbot: https://supporters.eff.org/donate/support-work-on-certbot
    swag              | 
    swag              | To support LSIO projects visit:
    swag              | https://www.linuxserver.io/donate/
    swag              | -------------------------------------
    swag              | GID/UID
    swag              | -------------------------------------
    swag              | 
    swag              | User uid:    1000
    swag              | User gid:    1000
    swag              | -------------------------------------
    swag              | 
    swag              | [cont-init.d] 10-adduser: exited 0.
    swag              | [cont-init.d] 20-config: executing... 
    swag              | [cont-init.d] 20-config: exited 0.
    swag              | [cont-init.d] 30-keygen: executing... 
    swag              | using keys found in /config/keys
    swag              | [cont-init.d] 30-keygen: exited 0.
    swag              | [cont-init.d] 50-config: executing... 
    swag              | Variables set:
    swag              | PUID=1000
    swag              | PGID=1000
    swag              | TZ=America/New_York
    swag              | URL=*MY MAIN DOMAIN*
    swag              | SUBDOMAINS=*QUICK EDIT*
    swag              | EXTRA_DOMAINS=
    swag              | ONLY_SUBDOMAINS=false
    swag              | VALIDATION=dns
    swag              | CERTPROVIDER=
    swag              | DNSPLUGIN=cloudflare
    swag              | EMAIL=*QUICK EDIT MY EMAIL IS HERE*
    swag              | STAGING=false
    swag              | 
    swag              | Using Let's Encrypt as the cert provider
    swag              | SUBDOMAINS entered, processing
    swag              | SUBDOMAINS entered, processing
    swag              | Sub-domains processed are:  *QUICK EDIT THERE ARE LOTS OF SUBDOMAINS*
    swag              | E-mail address entered: *QUICK EDIT MY EMAIL IS THERE*
    swag              | dns validation via cloudflare plugin is selected
    swag              | Certificate exists; parameters unchanged; starting nginx
    swag              | Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please retrieve a free license key from MaxMind,
    swag              | and add a new env variable "MAXMINDDB_LICENSE_KEY", set to your license key.
    swag              | [cont-init.d] 50-config: exited 0.
    swag              | [cont-init.d] 60-renew: executing... 
    swag              | The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am).
    swag              | [cont-init.d] 60-renew: exited 0.
    swag              | [cont-init.d] 70-templates: executing... 
    swag              | [cont-init.d] 70-templates: exited 0.
    swag              | [cont-init.d] 90-custom-folders: executing... 
    swag              | chown: changing ownership of '/config/custom-cont-init.d': Operation not permitted
    swag              | chown: changing ownership of '/config/custom-services.d': Operation not permitted
    swag              | [cont-init.d] 90-custom-folders: exited 1.
    swag              | [cont-finish.d] executing container finish scripts...
    swag              | [cont-finish.d] done.
    swag              | [s6-finish] waiting for services.
    swag              | [s6-finish] sending all processes the TERM signal.
    swag              | [s6-finish] sending all processes the KILL signal and exiting.
    swag exited with code 1
     

    Are you using unraid? It doesn't look like you are and then this is not the place for support.

    The container doesn't crash, it's stopped by something.

  18. On 6/23/2021 at 7:57 PM, stFfn said:

    is noone here firm with swag to help? 😕

    I´m really stuck and need some help 😕

     

     

     

    On 6/23/2021 at 8:49 PM, Melawen said:

    Does rather seem that way at the moment unfortunately.  I'm relatively new to Unraid but notice the group do seem to put out a fair amount of dockers (and probably have real jobs too) so hopefully we'll get some responses when they have time.

     

    We don't read much here anymore. If you want help, you can either use our discourse forum or Discord server.

    https://www.linuxserver.io/support