-
Posts
10232 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by bonienl
-
-
You have a port conflict, nginx can not start because port 80 is already used by something else.
Start in safemode and resolve the conflict.
-
Changed Status to Closed
Changed Priority to Other
-
ipvlan uses a shared mac address for multiple ip addresses.
This means the router must accept local ip addresses which may have the same. mac address.
host access makes use of so called “more specific routing”, this means the router must be able to handle multiple routes to the same destination.
- 1
-
-
My main server is configured with "ipvlan" and "host access enabled"
I have no issues to reach the Internet, but it appears certain home routers do not properly support the network functionality which is used by ipvlan and host access.
One solution to try: Instead of using DHCP set a static IP address on the server, this will leave the home router out of the picture for said IP address.
-
Changed Status to Closed
Changed Priority to Other
-
When configuration files on the usb stick get corrupted, it results in unpredictable GUI behavior. This looks such an example.
-
Use the stable version 6.12.1
And read the release notes about using tailscale.
-
The release notes were missing a NFS related change.
-
You have configured both IPv4 and IPv6, but IPv6 is not used.
I recommend to set IPv4 only.
-
In Unraid version 6.12.1 the avahi service binds to the available interfaces of the server.
This is from your log. Avahi is listening on 192.168.22.90
Jun 20 15:59:33 unRAID root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jun 20 15:59:33 unRAID avahi-daemon[5784]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jun 20 15:59:33 unRAID avahi-daemon[5784]: Successfully dropped root privileges. Jun 20 15:59:33 unRAID avahi-daemon[5784]: avahi-daemon 0.8 starting up. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Successfully called chroot(). Jun 20 15:59:33 unRAID avahi-daemon[5784]: Successfully dropped remaining capabilities. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Loading service file /services/sftp-ssh.service. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Loading service file /services/smb.service. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Loading service file /services/ssh.service. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.22.90. Jun 20 15:59:33 unRAID avahi-daemon[5784]: New relevant interface br0.IPv4 for mDNS. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Network interface enumeration completed. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Registering new address record for fe80::1a31:bfff:fedf:11a2 on br0.*. Jun 20 15:59:33 unRAID avahi-daemon[5784]: Registering new address record for 192.168.22.90 on br0.IPv4. Jun 20 15:59:33 unRAID emhttpd: shcmd (87): /etc/rc.d/rc.avahidnsconfd restart Jun 20 15:59:33 unRAID root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Jun 20 15:59:33 unRAID root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jun 20 15:59:33 unRAID avahi-dnsconfd[5793]: Successfully connected to Avahi daemon. Jun 20 15:59:33 unRAID emhttpd: shcmd (97): /usr/local/sbin/mount_image '/mnt/cache/system/docker/docker.img' /var/lib/docker 40 Jun 20 15:59:34 unRAID avahi-daemon[5784]: Server startup complete. Host name is unRAID.local. Local service cookie is 1453313680. Jun 20 15:59:35 unRAID avahi-daemon[5784]: Service "unRAID" (/services/ssh.service) successfully established. Jun 20 15:59:35 unRAID avahi-daemon[5784]: Service "unRAID" (/services/smb.service) successfully established. Jun 20 15:59:35 unRAID avahi-daemon[5784]: Service "unRAID" (/services/sftp-ssh.service) successfully established.
I am not familar with bonjour, perhaps it requires the specific address?
-
I can reproduce the issue, will make a fix.
Thx
-
Provide diagnostics when the situation occurs.
Also check you are not running out of docker space after a while.
-
Please PM diagnostics to me, so I can troubleshoot.
-
Without diagnostics we can not troubleshoot, it holds a lot more information than your one liner.
-
Please provide diagnostics
-
Changed Status to Closed
Changed Priority to Other
-
This is indeed expected behavior.
Settings are saved in cookies, which are valid per domain.
Local and remote access are different domains.
-
The code in the 'go' file needs a small revision.
The 'at' command does not support a waiting time in seconds, eventhough it can be given.
The updated code below properly waits 20 seconds.
# reload services after starting docker with 20 seconds grace period to allow starting up containers event=/usr/local/emhttp/webGui/event/docker_started mkdir -p $event cat <<- 'EOF' >$event/reload_services #!/bin/bash echo 'sleep 20;/usr/local/emhttp/webGui/scripts/reload_services' | at -M now 2>/dev/null EOF chmod +x $event/reload_services
-
Indeed NTP is broken in Unraid 6.12.0, will be fixed in the next release.
Thanks
- 1
- 2
-
5 hours ago, bkwq said:
NTP is also not working for me as of 6.12.
See my earlier answer. Post result of the requested command.
-
In the current implementation we do a 'soft' update to let SMB reread the configuration, this unfortunately does not change the listening interfaces of SMB (eventhough the config is updated).
In the next release this will be fixed.
- 1
-
Like it or not, but this isn't a bug. The implementation works as intended.
You can always make a feature request and explain how to improve.
-
Reboot your system and post the output of
ntpq -p
I have no problems with NTP.
Also understand that NTP does not immediately correct the time in one go, but adjust in gradual steps, which may take days if the time difference is big.
6.12 webui is not starting
in Stable Releases
Posted
To resolve the conflict, there are multiple ways to do so.
When changing GUI ports, make sure the new port assignments do not conflict with other running services. This means choose port numbers higher than 1024.