Bleak

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bleak's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Stubby (DOT/TLS) by default uses google. you can change this in the stubby config file in your appdata by adding # to the google config and removing them from the cloudflare config. If you already did this then perhaps the file got removed or corrupt on the last update and was replaced. I've had issues in the past with cloudflared(DOH/https) but it seems to be working fine for me for a long time now, so consider using that. As in my opinion it is marginally better privacy wise as you will "hide" your dns traffic under the gianourmous load of https traffic. You could use both doh and dot but I do need see the benefit of this.
  2. Hi Everyone, As the title states my usb died. It died just a few weeks after I replaced my old 3.0 usb which died after a few years of service. As recommended by unraid and the community I bought the usb 2.0 Kingston DTSE9 (I bought 2 as if I knew this would happen). Sadly today I logged into unraid it was a white background which I normally do not have and it all just looked wrong after clicking around I saw in the USB log that it was throwing many errors very rapidly. I then thought it was a usb port issue and did a shutdown and put it into a different port it sadly did not boot anymore. I was able to copy out the config from the usb before it died permanently and windows said it was raw and could not be used until formatted. I replaced the usb and unraid support helped me to get a new key and everything works again. Now hopefully this is just 1 bad usb and it won't happen again just to be sure could someone help me check if I did not misconfigure anything that puts a lot of stress on my usb. I also included a diagnostics file. Many thanks! zeus-diagnostics-20210525-1928.zip
  3. Is is one of the config files that it comes with thr cloudflared config file is for DOH (DNS over https) and the stubby config file is for DOT (DNS over TLS). I am having issues eith DOH so I set The DOT as the first dns server. Since then no issues.
  4. Can you try setting stubby(tls) as first and doh as second and see if your issues go away? I have too little knowledge to be certain but DOH seems to cause my issues.
  5. I had the cloudflared (DOH) as both options set it back to how it was only changed the stubby (TLS) to cloudflared instead of google. Seems bit better now.. not sure why everything goes to **** with only DOH. (Also maybe it was not very smart of me to have unraid get it's dns by DHCP which would be the phole docker on unraid...)
  6. I am now also having the following error shown in the logs(see attachment) also fix common problems says I should connect to 8.8.8.8 or github could be down so seems unraid thinks there is no connection anymore. (nothing is being blocked for unraid)
  7. Hi when I restart the docker it stops after DNS service is not running it will only continue when I change the /etc/resolv.conf to a dns server instead of 127.0.0.11 It will always revert that change by itself once it has started. While it is stuck there I cannot access the web page. I thought it was because of the server variable but that seems to not care whatever it is (can someone explain to me what that variable is for?) [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! Converting DNS1 to PIHOLE_DNS_ Converting DNS2 to PIHOLE_DNS_ Setting DNS servers based on PIHOLE_DNS_ variable ::: Pre existing WEBPASSWORD found DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "10.11.22.33", "VIRTUAL_HOST" => "10.11.22.33", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Enabling Query Logging [i] Enabling logging... ::: Docker start setup complete [✗] DNS service is not running [i] Neutrino emissions detected...
  8. Okay went in the bios (Just note it has been stable on these bios settings for at least half a year until a few weeks ago) noticed my bios was flickering and bit unresponsive.. Decided to replace the CMOS battery since this motherboard is getting older not sur eif replacing the cmos battery or just the clear cmos fixed the bios flickering but one of the two things did it's job. Re applied all the settings and for some reason it now has been stable for over 24 hours... keeping my fingers crossed for now but I really hope this nightmare is over. Next unraid system is not going to be a Ryzen system anymore it might be fun for desktop but that is all I will consider it for in the future.. Edit: has been stable for almost a week now issue is solved.
  9. Okay so It is happening again so turned on the syslog again. I mirrored it to flash since I do not want to turn it back on again until I need to or know how to fix it cause me having to do a hard reboot cannot be healthy to the system. please see attached the syslog you can see that the syslog ends at 17:49:24 on july 5th and it starts again when I do the hard reboot at 19:14:16. Hope someone can point me in the right direction... syslog(1)
  10. It has not happened since I stopped the container it was the Unifi controller docker not sure if it was the ports or something else but will try it again later whenever I have some free time to deal with it. Thanks for your link will certainly help with future troubleshooting.
  11. Happened to notice that one port was used by two containers changed that not sure if that fixed it but has been running fine since this post.
  12. So for the last two days my unraid becomes unresponsive about every two to 3 hours only solution is a hard shutdown (holding the power button). I am unable to hook up a monitor to it so not sure if it is a network thing or the system hangs itself? It used to work fine and never had any major issues. I have part of a syslog here (with the last entry at 00:35:18 before it became unresponsive and I restarted it hours later) but no clue if any of this clarifies why I am having this issue any help is welcome. Jun 26 23:48:25 Zeus rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="31503" x-info="https://www.rsyslog.com"] start Jun 26 23:48:53 Zeus ntpd[2043]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jun 26 23:53:05 Zeus sshd[5142]: Accepted password for root from 192.168.1.10 port 58976 ssh2 Jun 26 23:54:00 Zeus root: Fix Common Problems Version 2020.05.05 Jun 26 23:54:12 Zeus root: Fix Common Problems: Warning: Syslog mirrored to flash Jun 27 00:35:17 Zeus kernel: veth5490b91: renamed from eth0 Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(vethd3da599) entered disabled state Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(vethd3da599) entered disabled state Jun 27 00:35:17 Zeus kernel: device vethd3da599 left promiscuous mode Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(vethd3da599) entered disabled state Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(veth3fcd9d0) entered blocking state Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(veth3fcd9d0) entered disabled state Jun 27 00:35:17 Zeus kernel: device veth3fcd9d0 entered promiscuous mode Jun 27 00:35:17 Zeus kernel: IPv6: ADDRCONF(NETDEV_UP): veth3fcd9d0: link is not ready Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(veth3fcd9d0) entered blocking state Jun 27 00:35:17 Zeus kernel: br-aff798abb7c1: port 9(veth3fcd9d0) entered forwarding state Jun 27 00:35:18 Zeus kernel: eth0: renamed from vethb75b213 Jun 27 00:35:18 Zeus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3fcd9d0: link becomes ready Jun 27 12:56:42 Zeus kernel: Linux version 4.19.107-Unraid (root@38721b48cdfb) (gcc version 9.2.0 (GCC)) #1 SMP Sun Mar 8 14:34:03 CDT 2020 Jun 27 12:56:42 Zeus kernel: Command line: BOOT_IMAGE=/bzimage isolcpus=0-1,8-9 initrd=/bzroot Jun 27 12:56:42 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jun 27 12:56:42 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jun 27 12:56:42 Zeus kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jun 27 12:56:42 Zeus kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jun 27 12:56:42 Zeus kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format. Jun 27 12:56:42 Zeus kernel: BIOS-provided physical RAM map: Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d7ffff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x0000000009d80000-0x0000000009ffffff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20afff] ACPI NVS Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x000000000a20b000-0x000000000affffff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000dbc62fff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000dbc63000-0x00000000dbdd1fff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000dbdd2000-0x00000000dc254fff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000dc255000-0x00000000dc36cfff] ACPI NVS Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000dc36d000-0x00000000dcfd9fff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000dcfda000-0x00000000deffffff] usable Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000ffffffff] reserved Jun 27 12:56:42 Zeus kernel: BIOS-e820: [mem 0x0000000100000000-0x000000081f37ffff] usable Jun 27 12:56:42 Zeus kernel: NX (Execute Disable) protection: active Jun 27 12:56:42 Zeus kernel: e820: update [mem 0xca4df018-0xca4ed057] usable ==> usable Jun 27 12:56:42 Zeus kernel: e820: update [mem 0xca4df018-0xca4ed057] usable ==> usable Will try to get a diagnostics file but it is difficult to get one..
  13. I swear I've searched this whole thing 10 times no clue how I missed this... Thanks anyway sorry for missing this..
  14. Added --cap-add=NET_ADMIN to extra parameters. Found it somewhere in a forum apparently it should be mentioned somewhere that you need this but could not find it. Can someone link me something that explains what this does exactly? (or tell me ofcourse) want to understand what i just did and why i missed it..
  15. Hey so I am trying to setup basic auth with fail2ban and the authenticating is working great but fail2ban does not seem to do it's part: 020-05-09 18:31:32,502 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:31:31 2020-05-09 18:31:38,515 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:31:37 2020-05-09 18:31:43,727 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:31:43 2020-05-09 18:31:44,462 fail2ban.actions [388]: NOTICE [nginx-http-auth] Ban 84.241.199.134 2020-05-09 18:31:44,465 fail2ban.utils [388]: #39-Lev. 1501c3a14110 -- exec: iptables -w -N f2b-nginx-http-auth iptables -w -A f2b-nginx-http-auth -j RETURN iptables -w -I INPUT -p tcp -m multiport --dports http,https -j f2b-nginx-http-auth 2020-05-09 18:31:44,466 fail2ban.utils [388]: ERROR 1501c3a14110 -- stderr: "iptables v1.8.3 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)" 2020-05-09 18:31:44,466 fail2ban.utils [388]: ERROR 1501c3a14110 -- stderr: 'Perhaps iptables or your kernel needs to be upgraded.' 2020-05-09 18:31:44,466 fail2ban.utils [388]: ERROR 1501c3a14110 -- stderr: "iptables v1.8.3 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)" 2020-05-09 18:31:44,466 fail2ban.utils [388]: ERROR 1501c3a14110 -- stderr: 'Perhaps iptables or your kernel needs to be upgraded.' 2020-05-09 18:31:44,466 fail2ban.utils [388]: ERROR 1501c3a14110 -- stderr: 'getsockopt failed strangely: Operation not permitted' 2020-05-09 18:31:44,466 fail2ban.utils [388]: ERROR 1501c3a14110 -- returned 1 2020-05-09 18:31:44,467 fail2ban.actions [388]: ERROR Failed to execute ban jail 'nginx-http-auth' action 'iptables-multiport' info 'ActionInfo({'ip': '84.241.199.134', 'family': 'inet4', 'fid': <function Actions.ActionInfo.<lambda> at 0x1501c3ece3a0>, 'raw-ticket': <function Actions.ActionInfo.<lambda> at 0x1501c3ece940>})': Error starting action Jail('nginx-http-auth')/iptables-multiport 2020-05-09 18:31:48,940 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:31:48 2020-05-09 18:31:54,150 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:31:54 2020-05-09 18:31:59,362 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:31:58 2020-05-09 18:31:59,686 fail2ban.actions [388]: NOTICE [nginx-http-auth] 84.241.199.134 already banned 2020-05-09 18:32:05,374 fail2ban.filter [388]: INFO [nginx-http-auth] Found 84.241.199.134 - 2020-05-09 18:32:04 Basically trying from my phone on 4g to get myself banned but i can just keep retrying even though max retry's is at 3 if i try it for the 10th time and enter it correctly i just get in. dont know what the above errors mean tried to google it but did not find anything that helped me..