spants

Community Developer
  • Content Count

    577
  • Joined

  • Last visited

Everything posted by spants

  1. 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
  2. Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use. Are you sure nothing is on that IP?
  3. 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.
  4. Try it with Extra Parameters only containing: --cap-add=NET_ADMIN --restart=unless-stopped
  5. 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.
  6. try adding: dhcp-option DNS 10.11.12.13 to your client's .ovpn config, where the DNS is your pihole address
  7. maybe you can add a variable TZ to the template = America/Chicago (I haven't tried it)
  8. No problem. If you needed Node.js 12 - just use nodered/node-red:latest-12 in the repository field of the template
  9. 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).
  10. 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/
  11. 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
  12. 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!
  13. Your serverIP should be the same as the fixed ip address Sent from my SM-N976B using Tapatalk
  14. 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
  15. 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; }
  16. 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
  17. 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
  18. if you dont need persistance, please edit the mosquitto.conf: persistence false persistence_file mosquitto.db persistence_location /config/data/ and restart MQTT...
  19. 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
  20. @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) ?
  21. @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.
  22. can you do an ls -al on that directory please?