phishfi
-
Posts
19 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by phishfi
-
-
Sorry again for the late response. I'm not getting email notifications when there are thread responses, so I missed this. Here's the diagnostic output after:
- Removing the Tailscale plugin
- Restarting the server
Thanks again for your help!
-
1
-
-
OK, I went through the process of switching to ipvlan and installed the plugin you reccomended. I'm still getting the nmbd errors 4 times per second.
Jul 18 21:14:15 UnRAID nmbd[15268]: WARNING: no network interfaces found Jul 18 21:14:15 UnRAID nmbd[15268]: [2023/07/18 21:14:15.474657, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 18 21:14:15 UnRAID nmbd[15268]: WARNING: no network interfaces found Jul 18 21:14:15 UnRAID nmbd[15268]: [2023/07/18 21:14:15.725570, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 18 21:14:15 UnRAID nmbd[15268]: WARNING: no network interfaces found Jul 18 21:14:15 UnRAID nmbd[15268]: [2023/07/18 21:14:15.976462, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 18 21:14:15 UnRAID nmbd[15268]: WARNING: no network interfaces found Jul 18 21:14:16 UnRAID nmbd[15268]: [2023/07/18 21:14:16.227372, 0] ../../source3/lib/interface.c:685(load_interfaces)
I've googled similar issues and cannot find anything in common with other questions on linux forums.
-
ljm42,
Thanks for the recommendations! I'm switching to ipvlan and looking into that driver now. Out of curiosity, how can I confirm whether that's the NIC on my hardware? It's headless, so I can't check the BIOS.
-
On 7/13/2023 at 4:41 PM, ljm42 said:
If you are on 6.12.x, please upgrade to 6.12.3-rc3 as it has updates to networking that could affect this:
https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6123-rc3-available-r2572/If the issue continues, please provide diagnostics from 6.12.3-rc3
Sorry for the late reply, I've been busy with other stuff.
I just went through this process and I'm still getting the `No network interfaces found` lines in my logs. Here's the diagnostics output from 6.12.3 (Stable)
-
My UnRAID logs keep populating with these lines, nonstop. Does anyone know why or how I can address this?
Jul 13 15:37:08 UnRAID nmbd[9226]: WARNING: no network interfaces found Jul 13 15:37:08 UnRAID nmbd[9226]: [2023/07/13 15:37:08.328638, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 13 15:37:08 UnRAID nmbd[9226]: WARNING: no network interfaces found Jul 13 15:37:08 UnRAID nmbd[9226]: [2023/07/13 15:37:08.579520, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 13 15:37:08 UnRAID nmbd[9226]: WARNING: no network interfaces found Jul 13 15:37:08 UnRAID nmbd[9226]: [2023/07/13 15:37:08.830366, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 13 15:37:08 UnRAID nmbd[9226]: WARNING: no network interfaces found Jul 13 15:37:09 UnRAID nmbd[9226]: [2023/07/13 15:37:09.081282, 0] ../../source3/lib/interface.c:685(load_interfaces) Jul 13 15:37:09 UnRAID nmbd[9226]: WARNING: no network interfaces found Jul 13 15:37:09 UnRAID nmbd[9226]: [2023/07/13 15:37:09.332067, 0] ../../source3/lib/interface.c:685(load_interfaces) -
Hello all,
I keep getting an issue where the cache drive switches to read-only. As a result, all of my docker containers stop functioning correctly (tend to keep running, but basically unresponsive when I try to access them).
Here's a screenshot of the cache drive logs, and I attached a diagnostics output as well.
You can see the balance start -dusage=X commands earlier where I was following along in another forum thread, but that's all I've done with the drive and those efforts were to try and fix this issue, not the cause.
-
On 7/4/2023 at 9:35 PM, phishfi said:
So this isn't a completely safe fix, but it did the job for fixing my Tailscale SMB connectivity:
Add the following to you SMB Extra config in settings - > SMB:
You might only need to include the Tailscale interface name, whatever's relevant when you run `IP addr` from the Unraid terminal.
Just a follow up in case anyone ever finds this solution useful. It appears binding lo causes some issues with Docker containers accessing the shares. I recommend just including the Tailscale interface name and seeing how well that works before making any additional changes.
-
On 7/3/2023 at 3:36 PM, TBT said:
Can cofirm, this happens with Tailscale and Zerotier as well since 6.12.0. I am on 6.12.2, still not fixed. I have all the mentioned tricks applied, does not work.
It is still in there with 6.12.2.
So this isn't a completely safe fix, but it did the job for fixing my Tailscale SMB connectivity:
Add the following to you SMB Extra config in settings - > SMB:
Quote[global]
bind interfaces only = no
interfaces = lo tailscale1 br0You might only need to include the Tailscale interface name, whatever's relevant when you run `IP addr` from the Unraid terminal.
-
2
-
-
17 hours ago, EDACerton said:
Which version of 6.12 are you on? There was a bug in 6.12.0 that affected SMB.
I'm on 6.12.2.
-
I'm struggling to get this configured correctly ever since the 6.12 update to UnRAID.
Previously, I was using the Tailscale docker container, but I just found this Plugin while I was troubleshooting.
Basically, what I need is to configure Tailscale such that when I share my device to other Tailscale users, they can access the UnRAID shares via SMB. This was previously working perfectly by just having the UnRAID server shared to the Tailscale user (my dad), but now I'm able to reach any of the web interfaces via the Tailscale IP, but SMB times out when I try to browse to
\\<Tailscale IP>\
or
\\<Tailscale IP>\<Share Name>
Edit: I experience the same issue when trying to access a share from my phone over SMB as well. So it has nothing to do with the fact that I'm sharing the device over Tailscale to another user.
-
Hey all!
I have been working on getting CodiMD, a real-time collaboration tool for creating documents in Markdown, up and running. I've had it running no problem in the past, but the default configuration for that allowed anyone with access to the server to create an account and add/edit documents. There's a way to allow CodiMD to login via OAuth2, so I set that up using Nextcloud. I followed the instructions from CodiMD's Configuration Guide and their Nextcloud setup guide, but it seems the containers are unable to communicate with each other for the token exchange. What happens is Codi directs me to the NC auth site, then I confirm/allow Codi access to my NC account, then it directs me back to CodiMD and gives me an Internal Server Error 500. I have no clue how to correct this, and I've asked the CodiMD developers for help. We were able to determine that this appears to be an issue with Docker communication between the containers, because I'm unable to curl the public-facing URLs for either service from the docker terminal. It could be that my Nginx Proxy Manager isn't allowing the exchange to occur, but I have no idea how to correct that either.
Any help on this would be greatly appreciated. -
After fiddling around with things and re-imaging the new flash drive, I am consistently getting either LZMA data is corrupt, or the attached screen, where it hangs indefinitely...
-
So, for a bit of context... I bought a new motherboard, CPU, and RAM, and upgraded my server earlier today. When I did this, I was having trouble getting the old flash drive to boot, so I ran a backup against a new drive assuming I'd just switch the keys over once everything was up and running. The server booted to the new drive exactly as expected, but I left all the SATA drives unplugged to ensure a smooth transition, I just wanted to make sure UnRAID would boot.
Then, I had a bit of hardware changes to make, including plugged the SATA drives in, and now I cannot boot to the new (or old) flash drive. Every time I try to boot to either drive I get "LZMA data is corrupt". If I boot via UEFI, it just hangs at "Loading /bzroot...", but if I boot via legacy it get just past that like (add the "ok" at the end) and then tells me about the LZMA data corruption and then "-- System halted".
I wouldn't mind starting UnRAID from scratch, provided I can transfer my Docker containers and the raw data / parity over without delays/issues, but right now I'm at a total standstill.
Any help is greatly appreciated.
For troubleshooting, I'm back to having no storage devices attached except for the flash drives.
-
47 minutes ago, Frank1940 said:
First, make a copy of your flash drive before you try your next upgrade. Main >>> Boot Device and than click "Flash" under the 'DEVICE' Column. In the 'Flash Device Settings' section/tab, click on the "FLASH BACKUP" button. This will save time if something goes wrong. (Also provides protection if your flash drive should happen to fail in the future!)
Now, download the latest release. Unzip the file and copy (push) the bz* files to the flash drive. Now reboot the server. you should now be running the latest version. (This problem often occurs when there is not enough free memory in the server to allow the unzipping of the new version as it must all fit on RAM-- The downloaded zip file and the complete contents of that file.)
Awesome, thanks! I'll give that a try tomorrow. As for the RAM concern, I don't feel like that would be the issue, since I have 12Gb of RAM and the in-use RAM is usually hovering around 15-20%.
-
This has been the case since the first 6.7 release was available. When I attempt to upgrade to anything beyond 6.6.7, UnRAID acts like the update was successful and tells me to reboot. When I select 'reboot', it restarts but never comes back to the interface and the machine drops off the network. This is the second time this has happened with the same machine (first was months ago with 6.7, now it happened again when I tried to update to 6.7.2). The only solution I've found is to download 6.6.7 again and push bz* to the flash drive from my laptop, then boot the machine again from the flash drive...
Any help with continuing with updates beyond 6.6.7 would be greatly appreciated.
-
1 minute ago, Djoss said:
Why this?
Reading through the readme, I thought it said the container would not work without setting up your own config file. After getting the "internal error" from attempting to create an SSL cert, I assumed that was a potential cause.
1 minute ago, Djoss said:Did you verify that the DNS name resolves to the correct IP (should be your internet/public IP)?
I did. When I browsed to the DDNS link, it shows the "Congratulations" site indicating Nginx is working and accessible.
I see this congrats page, even though I have NPM set to direct this DuckDNS subdomain to one of my Docker apps (Ombi, this time, if that makes a difference).
1 minute ago, Djoss said:Are you using default container settings?
I am. For the sake of simplifying this whole thing, I've gone with ports 80 and 443 directly, and I've ordered my router to point those ports to my unraid server.
1 minute ago, Djoss said:Are you sure that ports 80 and 443 are properly forwarded to the container?
See above (yes).
Thanks for your help!
-
I'm definitely missing something here...
So, I've installed NPM using the CA option in Unraid, and then I copied the config.json into /mnt/user/appdata/NginxProxyManager. After that, I went to DuckDNS and set up a new subdomain (e.g. "phishfiSonarr"), then in NPM I added phishfiSonarr.duckdns.org and pointed it to local.unraid.ip.address (unraid's IP address on my internal network, port 8989 (Sonarr default). I went without an access list or SSL setting just to get it working first, but nothing's showing up (when I click/browse to phishfiSonarr.duckdns.org, it times out).Please let me know what I'm missing. Based on all the other comments, it's clear I must be missing something easy here, but I read through the readme, all the comments, and the issues on Github and I'm stuck.
Thanks!
Constant dump of logs with "WARNING: no network interfaces found" from nmbd
in General Support
Posted
Hmm, that does appear to have stopped the problem. Are there any potential concerns/lossed functionality asssociated with disabling netbios?
Thanks for the help!!