Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by spants

  1. Strange, and the dns of all the clients is pointing to your server?
  2. so there are no directories in the appdata folder for pihole, just files?
  3. did you definitely do this : 2) in your appdata/pihole directory, it will have created 3 directories. Delete these directories and create 3 files (of the same name): touch blacklist.txt whitelist.txt pihole.log If you don't do this, it will not start. Tony
  4. Hi - sorry I dont know about stopping dnsmasq as it isnt starting on my system. I think there is a plexconnect docker which lason acts as a dns server and this caused problems for one user. I dont have access to /etc/pihole/adlists.default as my template is only fronting the docker built by diginc. You may want to clone his dockerfile if you want access to other files..
  5. Agreed! I dont use this anymore as I upgraded my router and run the openvpn server on it.
  6. if the address is in use, it must be on your server? weird! Also, see werfsd's posts earlier in the thread....
  7. ok - you have eth0 connected and not eth1. Why are they bonded without cables in both? My config is attached
  8. Could it be the two network cards? I have two installed but only one is enabled.
  9. Here's mine - note the advanced settings with extra params = --cap-add=NET_ADMIN
  10. ok, it doesn't do that job - it checks to see if they are in a blacklist and then forwards the request to the dns server ips on the template. Are they correct?
  11. If it killed dnsmasq then its probably a plugin or something rather than a docker image.
  12. k, I have two eth but I only use one. I wonder if this is the issue. Also, how is dnsmasq running? Is it a plugin or other docker?
  13. @gl3nn - sorry, I don't know the answer. Is this something the raspberry PI version does? @bluepr0 - How many network cards are in your server?, Is the serverip the same as your unraid server?. I think I saw the same error when the empty txt files had not been created correctly... Is it all pointing to the right place? (There is a manual step for this docker)
  14. Yes, you need pihole to run on 80, hence unraid will need to move.
  15. do you have port 53 in use by any other dockers?
  16. thanks for the reminder as to why there were two port 53. Shouldnt do fixes when I am tired. No apps should use port 53 as it is reserved for dns lookups. Not sure why your app is using it edit: I see, it is used to fool apple tv to use plex. Not sure how to get round that one.
  17. Give it some time, they should appear after 1hr of use
  18. The way it works is that you set your dns on machines (or via your router) to pint to your unraid box, this processes the requests and if they pass it will resolve by the dns entries in the template (which you can change). Do you only have one interface? (I do)
  19. This bit is strange!... are your running two of them?. I would delete/rename the appdirectory for pihole and try again.. Is this related? Its the template on a new setup: Could be!. silly me. Only needs one port 53.... I have updated the template... edit... mine had the same but ran ok. attached is my config.
  20. This bit is strange!... are your running two of them?. I would delete/rename the appdirectory for pihole and try again..
  21. Sorry about all the confusion Make sure that you use PIHOLE and not UNRAID-HOLE from now on. Pihole was in beta and I have now removed the beta flag.
  22. Any chance you could post a sanitized version of your reverse proxy conf file? Curious to see how you are assigning both stuff on 82 and on 1962. I have been trying to also figure out how to do the letsencrypt with the linuxserver Apache docker. I use the older reverse proxy docker still. And I simultaneously use the Apache Docker as well. I want to consolidate. I posted my issue w/ letencrypt on the Apache docker thread Many thanks!! H. Sorry for delay - I wasnt getting notifications. The Apache docker is different to the nginx-letsencrypt one Apache mappings for docker are 443/tcp 80/tcp Nginx-letsencrypt 443/tcp 80/tcp proxy.conf client_max_body_size 5000m; client_body_buffer_size 128k; #Timeout if the real server is dead proxy_next_upstream error timeout invalid_header http_500 http_502 http_503; # Advanced Proxy Config send_timeout 5m; proxy_read_timeout 240; proxy_send_timeout 240; proxy_connect_timeout 240; # Basic Proxy Config proxy_set_header Host $host:$server_port; 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 https; proxy_redirect http:// $scheme://; proxy_http_version 1.1; proxy_set_header Connection ""; proxy_cache_bypass $cookie_session; proxy_no_cache $cookie_session; proxy_buffers 32 4k; site-confs server { listen 80; listen 443 ssl default_server; if ($scheme = http) { return 301$request_uri; } root /config/www; index index.html index.htm index.php; server_name; ssl_certificate /config/keys/fullchain.pem; ssl_certificate_key /config/keys/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'snip'; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; client_max_body_size 5000M; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains" always; add_header Front-End-Https on; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } # amazon echo-node red location /echo { proxy_pass; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass; } } so the port changes are done via the docker mapping.
  23. Strange, working fine on mine. Is it cached in your browser?