Jump to content

spants

Community Developer
  • Posts

    637
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by spants

  1. 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
  2. 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)
  3. I was just looking at the whitelist website - did it work for you?
  4. 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?
  5. 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
  6. Unfortunately the author of the docker has not updated it for sometime. I will see if I can use the octoprint/octoprint version. https://github.com/nunofgs/docker-octoprint/issues
  7. Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use. Are you sure nothing is on that IP?
  8. For ther NodeRedv2 Beta docker -= please change the repositiory tag to nodered/node-red-dev:v2.0.0-beta.2 to get the latest. The NodeRed team have just changed their build process and it is not using the beta tag.
  9. Try it with Extra Parameters only containing: --cap-add=NET_ADMIN --restart=unless-stopped
  10. 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.
  11. try adding: dhcp-option DNS 10.11.12.13 to your client's .ovpn config, where the DNS is your pihole address
  12. maybe you can add a variable TZ to the template = America/Chicago (I haven't tried it)
  13. No problem. If you needed Node.js 12 - just use nodered/node-red:latest-12 in the repository field of the template
  14. 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).
  15. how did you update? Was it the docker container or inside the docker container (which you shouldn't do)?. My template pulls down the official docker container with no changes. If there are bugs with Pi-hole, please log them at https://github.com/pi-hole/pi-hole/issues or https://pi-hole.net/
  16. 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
  17. Thanks guys - unfortunately I only made the template and cannot vouch for the actual docker container. I'm sure they will fix the docker component quickly!
  18. Your serverIP should be the same as the fixed ip address Sent from my SM-N976B using Tapatalk
  19. 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; } }
  20. 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; }
  21. 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
  22. 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
×
×
  • Create New...