Jump to content

captainfeeny

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by captainfeeny

  1. On 5/29/2022 at 4:12 PM, aeleos said:

     

    If you are willing to look at the official docs you can modify the docker to only run with a token in the extra parameters, and the configuration can be done on the CF website. This should solve any permission issues.

     

    On the part about 6.10, my understanding is any permission is

    On 5/20/2022 at 11:55 AM, Goldmaster said:

    Seam to having permission issues with this on 6.10

    sues aren't anything to do with the container or unraid but with incorrect permissions that unraid wasn't respecting before. Its possible you may need to force the container to use the user id you want, which can be done with --user 99:100 (for nobody:users) in extra parameters.

     

     

     

    chmod 777 /mnt/user/appdata/cloudflared seems to solve this. Whether that's a good idea or not, however...

  2. 12 hours ago, Greyberry said:

    Could you go into more detail on how you did it? I still can not get it to work.

    What do you mean with labels? Don't the containers show up automatically? I thought that is what its for?

     

    I had this problem too. What you need to do is add certain labels to your Docker containers. See the attached for an example one for Jellyfin. I had to add these labels to all my containers for it to work--even if the containers didn't have a Webui. Once I added all these labels, Flame populated automatically without any errors. It also seems I didn't have to add these for new containers. Flame would work without them being added. But if you want them to show up in Flame, you have to add these labels to new containers.

     

    2022-04-12_12-02.png

    • Like 1
  3. On 4/30/2021 at 1:43 PM, Alexstrasza said:

     

    This is probably due to the fact that Docker containers are prevented from talking to the host by default. So the traffic will be trying to do this:

     

    You -> Tailscale tunnel -> Tailscale Docker on Unraid Host -x> Pihole container

     

    Before it was doing this:

     

    You -> LAN -> Directly in the network interface of the Unraid host and routed to the PiHole

     

    To fix, try going to Settings -> Docker and changing "Host access to custom networks" to "Enabled". You'll have to temporarily disable Docker to do this and then restart it.

     

    Let me know if that works!

    This helped me too, thanks! 

     

    Maybe it should be added to the instructions?

    • Like 1
  4. For posterity:

     

    tldr; Change your motherboard.

     

    After USB ethernet proved unstable as well, I plugged in both the USB ethernet and the motherboard NIC and achieved stability. The motheboard NIC still didn't work, but simply having it plugged in did... something? 

     

    In any case, it seemed to me the problem was with the motherboard. So I changed it out for an MSI B450i, which I've been running for a day without any of the issues I had with the Gigabyte B450i.

     

     

    • Like 1
  5. Well, it turns out the USB->Ethernet cable didn't solve anything. I still lose network regularly, and only a reboot brings it back. Sometimes the network goes down after minutes, sometimes after several hours. 

     

    I finally caught this in my syslog following the latest network drop. If it means anything I was downloading a Windows ISO at the time, so maybe the connection was flooded? It's probably coincidence.

     

    Would anyone know what might be causing this?

     

    kernel: ------------[ cut here ]------------
    Jan 23 18:26:37 potzdorf kernel: NETDEV WATCHDOG: eth0 (ax88179_178a): transmit queue 0 timed out
    Jan 23 18:26:37 potzdorf kernel: WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:465 dev_watchdog+0x161/0x1bb
    Jan 23 18:26:37 potzdorf kernel: Modules linked in: xt_nat vhost_net tun vhost tap kvm_amd ccp kvm veth md_mod xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs nfsd lockd grace sunrpc k10temp it87 hwmon_vid edac_mce_amd btusb btrtl btbcm ax88179_178a btintel bluetooth usbnet crct10dif_pclmul crc32_pclmul crc32c_intel i2c_piix4 ghash_clmulni_intel wmi_bmof i2c_core pcbc aesni_intel aes_x86_64 crypto_simd mii ahci ecdh_generic cryptd nvme glue_helper nvme_core libahci wmi button [last unloaded: md_mod]
    Jan 23 18:26:37 potzdorf kernel: CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.19.107-Unraid #1
    Jan 23 18:26:37 potzdorf kernel: Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS F60e 12/09/2020
    Jan 23 18:26:37 potzdorf kernel: RIP: 0010:dev_watchdog+0x161/0x1bb
    Jan 23 18:26:37 potzdorf kernel: Code: 5f 94 00 00 75 39 48 89 ef c6 05 4e 5f 94 00 01 e8 a1 a8 fd ff 44 89 e9 48 89 ee 48 c7 c7 57 2a da 81 48 89 c2 e8 cd 0b af ff <0f> 0b eb 11 41 ff c5 48 81 c2 40 01 00 00 41 39 cd 75 95 eb 13 48
    Jan 23 18:26:37 potzdorf kernel: RSP: 0018:ffff88881e703ea0 EFLAGS: 00010286
    Jan 23 18:26:37 potzdorf kernel: RAX: 0000000000000000 RBX: ffff88881aa53438 RCX: 000000000000047a
    Jan 23 18:26:37 potzdorf kernel: RDX: 0000000000000001 RSI: 0000000000000002 RDI: 0000000000000247
    Jan 23 18:26:37 potzdorf kernel: RBP: ffff88881aa53000 R08: 0000000000000003 R09: 0000000000015800
    Jan 23 18:26:37 potzdorf kernel: R10: 0000000000000000 R11: 0000000000000060 R12: ffff88881aa5341c
    Jan 23 18:26:37 potzdorf kernel: R13: 0000000000000000 R14: ffff888819a32280 R15: 0000000000000004
    Jan 23 18:26:37 potzdorf kernel: FS:  0000000000000000(0000) GS:ffff88881e700000(0000) knlGS:0000000000000000
    Jan 23 18:26:37 potzdorf kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jan 23 18:26:37 potzdorf kernel: CR2: 00000000006cb698 CR3: 00000007e58be000 CR4: 0000000000340ee0
    Jan 23 18:26:37 potzdorf kernel: Call Trace:
    Jan 23 18:26:37 potzdorf kernel: <IRQ>
    Jan 23 18:26:37 potzdorf kernel: call_timer_fn+0x18/0x7b
    Jan 23 18:26:37 potzdorf kernel: ? qdisc_reset+0xc0/0xc0
    Jan 23 18:26:37 potzdorf kernel: expire_timers+0x7e/0x8d
    Jan 23 18:26:37 potzdorf kernel: run_timer_softirq+0x72/0x120
    Jan 23 18:26:37 potzdorf kernel: ? __hrtimer_run_queues+0xc3/0x10b
    Jan 23 18:26:37 potzdorf kernel: ? ktime_get+0x44/0x95
    Jan 23 18:26:37 potzdorf kernel: __do_softirq+0xc9/0x1d7
    Jan 23 18:26:37 potzdorf kernel: irq_exit+0x5e/0x9d
    Jan 23 18:26:37 potzdorf kernel: smp_apic_timer_interrupt+0x80/0x93
    Jan 23 18:26:37 potzdorf kernel: apic_timer_interrupt+0xf/0x20
    Jan 23 18:26:37 potzdorf kernel: </IRQ>
    Jan 23 18:26:37 potzdorf kernel: RIP: 0010:native_safe_halt+0xe/0xf
    Jan 23 18:26:37 potzdorf kernel: Code: 60 02 df f0 83 44 24 fc 00 48 8b 00 a8 08 74 0b 65 81 25 55 a9 98 7e ff ff ff 7f c3 e9 07 00 00 00 0f 00 2d fa c4 57 00 fb f4 <c3> e9 07 00 00 00 0f 00 2d eb c4 57 00 f4 c3 53 e8 44 0f a1 ff 65
    Jan 23 18:26:37 potzdorf kernel: RSP: 0018:ffffc9000326bec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
    Jan 23 18:26:37 potzdorf kernel: RAX: 0000000000000004 RBX: ffff88881af95100 RCX: 0000000000000020
    Jan 23 18:26:37 potzdorf kernel: RDX: 000000000462cbe6 RSI: 0000000000000083 RDI: ffff88881e7207c0
    Jan 23 18:26:37 potzdorf kernel: RBP: 0000000000000000 R08: ffff88881e71cb00 R09: 0000000000000000
    Jan 23 18:26:37 potzdorf kernel: R10: 0000000000000004 R11: ffff88881e71fb40 R12: 0000000000000000
    Jan 23 18:26:37 potzdorf kernel: R13: 0000000000000004 R14: 0000000000000000 R15: 0000000000000000
    Jan 23 18:26:37 potzdorf kernel: default_idle+0xc/0x16
    Jan 23 18:26:37 potzdorf kernel: do_idle+0xdb/0x1fc
    Jan 23 18:26:37 potzdorf kernel: cpu_startup_entry+0x6a/0x6c
    Jan 23 18:26:37 potzdorf kernel: start_secondary+0x197/0x1b2
    Jan 23 18:26:37 potzdorf kernel: secondary_startup_64+0xa4/0xb0
    Jan 23 18:26:37 potzdorf kernel: ---[ end trace 11126c867701d57a ]---
     

  6. An update: I reset my CMOS and booted Windows from a USB stick. The NIC works fine in Windows 10. I updated to the latest driver and all continues to work.

     

    However, when I boot into UNRAID, I'm told I have an IP, ifconfig confirms I have an IP, but the router says the LAN port that UNRAID is attached to is unplugged. (Before it said plugged in but 10Mbps connection.) And I can't ping anything inside or outside the network. 

     

    What's interesting is that the router says I have a 1000Mbps connection to that port while the motherboard logo is showing, but as soon as UNRAID gets past loading bzroot, the router says that port is unplugged again. It seems something is turning off the NIC during the boot process?

     

     

     

  7. Hi all,

     

    I'm having a difficult time with connecting to my server. Sometimes I get an IP and I can connect to it for ~5 minutes before it goes down, sometimes I get the 169 ip that means it wasn't assigned an IP at all.

     

    Gigabyte B450i Aorus Pro Wifi

    Ryzen 5 3600

    UNRAID 6.8.3

    **DIAGNOSTICS ATTACHED**

     

    What I've tried:

    * deleting config/network.cfg

    * disabling bonding in config/network.cfg

    * using a different port on my router

    * using a known-good ethernet cable

    * reseating the ethernet cable

    * updating my bios

    * looking in the bios for anything related to the LAN connection. There's nothing.

    * rebooting many times

    * pinging the router (Destination Unreachable)

    * pinging from another device to my server (Destination Unreachable)

     

    If I get an IP, the ~5 minute disconnection is pretty reliable. Then it showns eth0 down in the UNRAID GUI. 

     

    If I run ifconfig in the terminal, it shows the correct IP despite there being no connection. 

     

    One other thing I noticed is that my router (Netgear R6400v2) will show 1000Mbps in the 'Ethernet port state' when the server has a connection, but after the connection drops, it shows the UNRAID ethernet port at 10Mbps.

     

    I have two Raspberry Pis connected via ethernet to the router that have been running trouble-free for months.

     

    Would anyone have any suggestions of what to try?

     

    Thanks!

    tower-diagnostics-20210110-1600.zip

×
×
  • Create New...