bonienl
-
Posts
10233 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bonienl
-
-
How do remotely access the server?
Are you using vpn or other method?
The picture shows there is no nchan communication (this is the background communication to update the gui).
Some how your remote access blocks this.
-
Kubernetes is aimed at datacenter environments, the Unraid solution is mostly used in home environments.
Probably this is not a widely requested feature for home use.
-
Unraid should detect address changes and update.
Can you provide diagnostics after an address change happened and the gui still listens to the old address.
Ps. Are you not using ipv4?
-
Thanks for the recommendations.
I made some updates for Unraid 6.13.
-
1
-
1
-
-
@SpencerJ can you have a look?
-
1
-
-
For upcoming version 6.12.4 I added a new option to specify the life time of notifications. Default is 3 seconds.
-
2
-
1
-
-
10 hours ago, Kurkoko said:
I've got a strange issue that seems to freeze unraid interfaces for minutes and then come back again.
Looks like a wrong network configuration, please provide diagnostics
-
10 hours ago, Kurkoko said:
Why unraid renames eth0 by itself??? I
This is docker renaming the interfaces and perfectly normal.
-
43 minutes ago, JorgeB said:
@bonienlcan you confirm if bridging has any advantages for this? Without bridging the call traces should not appear, or at least they should be much less likely to appear.
Bridging is only needed when VMs are used, otherwise it can be disabled.
-
These error messages come from 'netbios'
I recommend to disable netbios and use WSD instead for host discovery. See Settings -> SMB settings
-
1
-
-
You have two wireguard tunnels with the same IP address, that won't work. Delete the duplicate tunnel.
We made some additional fixes in the upcoming version. I recommend you use the new version once available, it should work better with WG VPN tunnels.
-
38 minutes ago, Kilrah said:
It has been the default for new setups since 6.11...2 I think? But it's naturally not being auto-changed since that may need additional changes in people's setups.
Since 6.11.4, see https://docs.unraid.net/unraid-os/release-notes/6.11.4
Only for new installations, existing installations (people upgrading) need to change manually.
-
45 minutes ago, Ford Prefect said:
The issue is only in the router,
With "gear" I mean different equipment from Ubiquiti, including a router, the USG-Pro-4 in my case.
45 minutes ago, Ford Prefect said:now, where the static table gets messed up
This is only a display thing. Connections work fine.
Unifi shows MAC addresses but does not further split out the table when multiple IP addresses have the same MAC address.
If it is a concern, why not report an issue to Ubiquiti?
-
2
-
-
17 minutes ago, Ford Prefect said:
If some of the internationl users , running a unify router box
I have Unifi network gear and no issues.
For those who need macvlan, because ipvlan doesn't work for them (Fritz users), an alternative solution is to disable the bridge function of br0 and make it a plain eth0 interface. Disabling the bridge function is only applicable when no VMs are used using br0.
In the docker container settings, the network needs to be re-assigned to the custom-eth0 interface instead of the custom-brr0 interface.
We are collecting as much information as possible about the macvlan issue and are looking into getting the Linux kernel developers involved to find a solution. Rest assurred, we also want this issue to be solved.
-
2
-
2
-
1
-
-
Not correct. When using ipvlan it is still possible to set up containers on br0 with a fixed ip address. And this works correctly. I have about 10 containers running this way, including Plex.
-
Quote
Here is a Diagnostic if it is needed of the server in a healthy state and I will monitor it over the next couple of days allowing the server to remain powered on.
This looks a lot better, it is a bit of a puzzle why IPv6 gives so much grief on your system.
-
Can you test with "IPv4 only" setting on br0 and see if that makes a differrence?
Please provide diagnostics of the new test.
Thx
-
Unraid 6.12 has improved security, as part of that services are forced to listening to proper network interfaces (both IPv4 and IPv6).
If something is not working correctly networkwise due to wrong configurations, it will impact communication.
-
Your logs contains traces of macvlan issues, see https://docs.unraid.net/unraid-os/release-notes/6.12.0 about known issues.
- Change in your docker settings macvlan to ipvlan
- Update to the latest stable version 6.12.3
-
You need to check your router configuration, it has issues with IPv6.
Jul 10 22:15:50 xxxx dhcpcd[1697]: br0: expired address fda2:612d:c297:4585:265e:beff:fe43:dc4d/64 Jul 10 22:15:50 xxxx dhcpcd[1697]: br0: part of a Router Advertisement expiredAlternatively set "IPv4 only".
-
I have seen this happening when the network.cfg file contains incorrect/corrupted information.
As suggested above delete the file "network.cfg" and redo your network settings.
-
Keep in mind that Unraid completely runs from RAM, which is a different situation as Truenas.
-
What is not working?
-
There are some unexplainable events in your log which prevents nfs to start.
You should remove the packages from the folder /extra and restart the server without them installed and test again running in safe mode.
In particular "llfuse-1.4.2-x86_64-1_SBo_nerdtools.txz" is suspicious (this one is no longer developed). Why is this installed?
UI Blank when loging in
in General Support
Posted
This looks like a problem with your USB stick not being read properly.
Please take the USB stick out (shutdown server first) and run a file system check on a windows machine.