spants

Community Developer
 View Profile  See their activity

  • Posts

    637

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by spants

    [support] Spants - NodeRed, MQTT, Dashing, couchDB

    in Docker Containers

    Posted

    On 8/18/2021 at 4:12 AM, Brandonb1987 said:

    getting an npm error in the nodered docker. When i try to update a pallet it gives me the following:

     

     I tried running the command in the console and just denies me.

     

    Any suggetions?

    1) You can try it from the console in the nodered template (I think that you did)

    2) or do it on the unraid console and substitute "/data" to "/mnt/user/appdata/nodered" or whatever you used....
    Let me know how you get on

    [SUPPORT] pihole for unRaid - Spants repo

    in Docker Containers

    Posted · Edited by spants

    On 8/13/2021 at 6:41 PM, Hydranmenace said:

    I understand I need to fix this but I do not know how. That is why I posted all the screen caps. I don't pretend to know what I'm doing. I'm a regular guy who followed a youtube tutorial.

    I noticed that in my router in DHCP settings my IP Pool Starting Address is 192.168.1.2 and that is the IP pihole is using. Would that be a conflict? I thought that just meant that is the number the router would use to start looking for things on the network. When I tried an IP range outside of that for pihole it gave me an error saying it was outside the range of my subnet. Whatever that means.

     

    Usually I set my DHCP range quite high up - maybe starting at 192.168.1.100 - so that nothing gets allocated in the ranges for my fixed IP. Some of the routers firmwares stop you allocating static addresses outside of this range.
    So you can either, set the static address on the device itself (set to manual not dhcp on the device) and not worry about it on the router or have the large range on the router, set the pihole address and restart any device that may have claimed that IP address already.
    Always set a DNS record manually (1.1.1.1 /8.8.8.8 or similar) for Unraid in the networking settings on unraid - dont let it use the DHCP dns as it will need DNS before the docker pihole as started (or if pihole is stopped)

     

    [support] Spants - NodeRed, MQTT, Dashing, couchDB

    in Docker Containers

    Posted

    16 hours ago, MrChip said:

    Will there be any updates to the MQTT version? I'm getting an error trying to configure the log timestamp format:

    Error: Unknown configuration variable "log_timestamp_format".

     

    It appears this variable applies to newer versions of the Mosquitto MQTT broker. Current version is now 2.0 on mosquitto.org.

     

    Bob

     

     

    Hi Bob

     

    I originally made this for my home automation system which works well and found no need to update (one of the later updates broke it). I will probably change to a Hive AMQP with MQTT plugin as it allows web based user management  - would that suit you too?

    [SUPPORT] pihole for unRaid - Spants repo

    in Docker Containers

    Posted

    7 hours ago, newunraiduser5 said:

    Hi, I am trying to set up a whitelist at https://github.com/anudeepND/whitelist/blob/master/README.md but cant seem to get it to work without Python 3. The instructions for a docker install / install without Python doesnt seem to work either. Can anyone help.

     

    Thanks in advance.

     

     

    There is a section on the readme that will help.

     

    0) If you dont have python3 on your unRaid, install it via the nerdtools plugin.

     

    1) find the path for /etc/pihole/  - for me it is /mnt/user/appdata/pihole/pihole/

    2) ssh to your unraid and cd to that directory

    3) git clone https://github.com/anudeepND/whitelist.git

    4) cd whitelist/scripts

    5) ./whitelist.py --dir /mnt/user/appdata/pihole/pihole/ --docker

    6) ./referral.sh --dir /mnt/user/appdata/pihole/pihole/ --docker

    7) restart pihole

     

     

    • Like 2
    • Thanks 1

    [SUPPORT] pihole for unRaid - Spants repo

    in Docker Containers

    Posted

    On 6/24/2021 at 7:42 AM, Rockstar said:

    I removed the container, image and everything else to start fresh but so far the issue remains and I am honestly not sure why.

    Inside the PHP error log is: 2021-06-23 23:34:18: (server.c.1464) server started (lighttpd/1.4.53)

    There's already routing in Unraid setup under br0 for 10.10.5.0/24, this is set within the container template.

    Navigating to 10.10.5.2/admin leads to nothing.  I'm not really sure what else to look at or pull, let me know and I will do so.

     

    Try it with Extra Parameters only containing:

     

    --cap-add=NET_ADMIN --restart=unless-stopped

     

    [support] Spants - NodeRed, MQTT, Dashing, couchDB

    in Docker Containers

    Posted

    On 6/24/2021 at 9:24 AM, OsoPolar said:

    HI Guys i setup a Node Red Docker last night on main PC and added an additional port to get access for my Alexa Pluging with a local IP http://192.168.23.100:3456/ and i could get to page and login to authenticate alexa cookie

     

    It keeps kept confirming with Alexa the cookie was saved.

    But NR kept reporting i needed to do it again it would not connect?

     

     

     

    Please use a location for the cookie to be something like this:

     

    /data/AlexaAuthFile.txt

     

    It will then save it in your appdata directly and not the container.

    [SUPPORT] pihole for unRaid - Spants repo

    in Docker Containers

    Posted

    Great - thats the way to do it. 

    The template is for the official Pi-hole docker, I don't make any changes so please check their github for issues.

     

    I just changed the template to remove the dns entries from the extra parameters setting though as this was causing issues for some... Unfortunately this change doesnt roll down if you have already have Pihole setup. ( I dont think this fixes your issue though).

     

    I will take another look tomorrow (I'm in the UK).

    [support] Spants - NodeRed, MQTT, Dashing, couchDB

    in Docker Containers

    Posted

    On 3/30/2021 at 1:29 PM, mavrrick said:

    I have recently run into a snag that i believe has been determined to be related to the version of Node.JS used by Node red in the docker. Is there any way to upgrade that to a newer version?

     

    Which version of NodeJS do you need? You can change the version by using the appropriate tag in the Repository field:

    https://hub.docker.com/r/nodered/node-red/tags?page=1&ordering=last_updated

     

    [support] Vaultwarden (formerly Bitwarden_rs)

    in Docker Containers

    Posted · Edited by spants

    8 hours ago, Roxedus said:


    They both do the work, and cater to different scenarios. My reasoning for my suggestion is that I dont want to be able to reach /admin at all with my reverse proxy.
    Another thing to think about is the resulting error code, where my suggestion gives a 404, while the deny gives a 403. A 403 might say to a potential attacker that there is something there (you could have it respond with a 404 instead)

     

    The problem with the 404 method is that if you use a custom network (say PROXYNET for dockers that can be reached from outside), then you cannot (well, I couldn't!) reach the /admin endpoint from inside either.

     

    I have made some changes regarding the 403/401 error codes and now use this.... (based on an old bitwarden template)
      

    #BITWARDEN
# make sure that your domain has dns has a cname or a record set for the subdomain bitwarden 
# This config file will work as is when using a custom docker network the same as letesencrypt (proxynet).
# However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve.  
# If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7

resolver 127.0.0.11 valid=30s;
upstream bitwarden {
    server bitwardenrs:80;
}


server {
  # return error code 404 if 401 or 403 would be returned to hide admin endpoint
  # no need to create the 404.html file unless you want to customise
  error_page 401 403 404 /404.html; 
    listen 443 ssl;
    server_name bitwarden.*;
    include /config/nginx/ssl.conf;
  client_max_body_size 128M;
  
  location /admin {
    # allow LAN access (match your IP range)
    allow 192.168.1.0/24;
    # allow VPN access (match your IP range)
    allow 10.0.10.0/24;
    # BLOCK all other access
    deny all;
    proxy_pass http://bitwarden;   
  }
  
  location / {
   proxy_pass http://bitwarden;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
  }
  
  location /notifications/hub {
   proxy_pass http://bitwarden;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }
  
  location /notifications/hub/negotiate {
    proxy_pass http://bitwarden;
  }
}

     

    [support] Vaultwarden (formerly Bitwarden_rs)

    in Docker Containers

    Posted

    For folks that want to protect the /admin page from being accessed from outside of the internal network when using SWAG, I think this is a better way.....

     

    Note 192.168.1.0 is the LAN network and 10.0.10.0 is a VPN network attaching remotely

      

      location /admin {
    allow 192.168.1.0/24; 
    allow 10.0.10.0/24;
    deny all;
    # enable the next two lines for http auth
    # auth_basic "Restricted";
    # auth_basic_user_file /config/nginx/.htpasswd;
    proxy_pass http://bitwarden;   
  }

     

    [SUPPORT] pihole for unRaid - Spants repo

    in Docker Containers

    Posted

    Dockers can't point to pi-hole, is my understanding, and my docker and plug-in update checks were taking upwards of 6-10 minutes.
     
    Also now I can do service on my server without taking down DNS for the whole house.
     
    The pi-hole docker is sweet but my needs are much better served with a real device.
     
    I have two network cards to avoid any problems and my main pihole is the docker. I have a secondary pihole as a physical machine with opnsense providing both DNS ips for DHCP

    Sent from my SM-N976B using Tapatalk

    [support] Spants - NodeRed, MQTT, Dashing, couchDB

    in Docker Containers

    Posted

    If you use RETAINED topics, it can write them to a temporary db in case of restarting. Most people dont need this.

    There seems to be a permissions issue with some dockers, I should take a look at this as I made it some time ago (it just works for me!).
    I saw on another thread that someone had similar issues on another docker and was advised to run a script (attached). It will reset the directory permissions on the appdata directory. Run it at your own risk (I just tried it)

     

    fixAppdataPerms.sh

    • Like 1