Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by spants

  1. Try it with Extra Parameters only containing: --cap-add=NET_ADMIN --restart=unless-stopped
  2. 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.
  3. try adding: dhcp-option DNS to your client's .ovpn config, where the DNS is your pihole address
  4. maybe you can add a variable TZ to the template = America/Chicago (I haven't tried it)
  5. No problem. If you needed Node.js 12 - just use nodered/node-red:latest-12 in the repository field of the template
  6. 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).
  7. 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 or
  8. Which version of NodeJS do you need? You can change the version by using the appropriate tag in the Repository field:
  9. 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!
  10. Your serverIP should be the same as the fixed ip address Sent from my SM-N976B using Tapatalk
  11. 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 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; # allow VPN access (match your IP range) allow; # 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; } }
  12. 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 is the LAN network and is a VPN network attaching remotely location /admin { allow; allow; deny all; # enable the next two lines for http auth # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; proxy_pass http://bitwarden; }
  13. 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
  14. 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)
  15. if you dont need persistance, please edit the mosquitto.conf: persistence false persistence_file mosquitto.db persistence_location /config/data/ and restart MQTT...
  16. Does your MQTT directory look like this?: You can also try setting open permissions on that directory: cd /mnt/user/appdata chmod -R 777 MQTT
  17. @Lebowski that is strange. That error looks to be caused by having persistence=true in the config file and not being able to write the mosquitto.db file. Can you share the config file (delete any private bits) ?
  18. @Lebowski sorry for the delay in the reply. please try this fix: Change the permissions of the appdata directory for your MQTT data: for example: chown -R nobody:users /mnt/user/appdata/MQTT and you should be ok.
  19. for serial devices (such as my two 3d printers using octoprint), I just use the /dev/serial/by-id/@xxxxxxxxxx paths for them.
  20. I use the /dev/serial/by-id/@xxxxxxxxxx paths for my devices
  21. You may have to keep changing it as the template is not refreshed on the update. Check your /boot/config directory structure for the cached templates and also edit it there Sent from my SM-N976B using Tapatalk
  22. I have pushed this - note that you will not see the change if you already downloaded NR as the template is cached on your boot drive. Thanks for the link - I didnt see it when I first made the template in 2016! You can change it on your own system btw