Darrell

Members
 View Profile  See their activity

  • Posts

    22

  • Joined

  • Last visited

 Content Type 

Everything posted by Darrell

  1. Darrell
    That is the current version I'm running on both servers.
  2. Darrell
    I think I figured it out. When I disable IPV6 on both of my Unraid servers, they both run without issue. When I enable IPV6 on both or my Unraid servers, the WebUI becomes inaccessible after a day or two.
  3. Darrell
    Upgraded to 6.12.2 issues still remains. I've tried various other suggestions like changing ngix port. nothing has resolved it. Posting diagnostics in case someone is able to assist. downgrading to 6.11.5 until I can figure out a solution. apollo-diagnostics-20230702-0838.zip
  4. Darrell
    Another update. I formatted the USB drive and reinstalled Unraid using the UnraidUSBCreator tool. Issue still remains
  5. Darrell
    UPDATE: WebUI is not accessible after the DNS change I tried accessing through IPv4, IPv6 address as well as http://tower.local Docker's and SMB shares are still working.
  6. Darrell
    Hi bonieni, Thanks for the quick reply. I am accessing through the ip address of the server. I'm using a couple of pihole devices and used IPV6 local IP DNS settings. I've updated the server to use Cloudflare DNS for both IPv4 and IPv6.
  7. Darrell
    Since the last couple of RC's as well as the current stable release. the WebUI becomes inaccessible randomly. When this happens, I am able to access all unraid shares and dockers and everything else is working perfectly, but I am unable to view the WebUI. The Chrome tab just spins and displays nothing I'm able to resolve it by using the power button on the server which does a graceful shutdown. I then turn on the server again and all is fine. Any suggestions? apollo-diagnostics-20230617-0811.zip
  8. Darrell
    It's been 10 days and I haven't had a kernel panic lockup (knock on wood). It appears that the change from macvlan to ipvlan has resolved my issue.
  9. Darrell
    I came across this post which sounds a lot like the symptoms I'm experiencing I changed macvlan to ipvlan and I'll report back in a week or so
  10. Darrell
    syslog server is enabled. I'll post the info after the next crash.
  11. Darrell
    Hello fellow Unraid users, I noticed this issue over the past month or so. It may be related to an upgrade to 6.10.3, but I'm not 100% sure. Every week or so the server becomes unresponsive and requires a hard reboot. I am not able to to log into the terminal, or use the power button to have Unraid shutdown gracefully. The last time I did a hard reboot, I typed in this command: tail /var/log/syslog -f as suggested by this thread I've attached a picture of what was left in the terminal before doing another hard boot. Can anyone point me in the right direction on how to resolve this issue? Thanks
  12. Darrell
    Hey everyone, I'm running into a strange issue. Since installing this docker, my unraid server has started randomly pinning the cpu at 100% and made the the gui unresponsive. I've had to do a couple of unclean shutdowns as the shutdown at terminal would hang. I didn't think it had anything to do with AudioBookshelf, but since disabling it in docker, I haven't had any issues. I'm currently running Unraid 6.10.0-rc3, but it was also happening on 6.10.0-rc2. Any suggestions?
  13. Darrell
  14. Darrell
    Found it! I tried your suggestion of adding a 20 second delay after a host or bridge that was moved to the top of the docker list. The issue still remains.
  15. Darrell
    How can I add a delay?
  16. Darrell
    Anyone have any ideas or suggestions?
  17. Darrell
    I did have two NIC cards setup previously on this server, but changed the cpu/motherboard that only had a single NIC. I don't think I ever setup bonding, but you are correct. The network settings had bonding enabled. I disabled bonding and rebooted the server. The issues persists. When I tried to manually start the containers, the error is "Execution error no such container." When I went into settings and disabled docker and then reenabled docker, all dockers containers started normally. FYI I also have this exact issue on my second unraid server.
  18. Darrell
    I've noticed this issue since 6.9 RC1. The issue was not present in 6.8x When I reboot the server, the docker containers that have network set to br0 will not auto start. If I try to manually start the affected docker containers, I will get an error "Execution error no such container." Any applications that have network settings to "host" or "bridge" auto start without issue. The only way I can get the docker containers that have network set to br0 to start, is to go into settings disable docker and then enable docker. After doing this, all docker containers will start without issue. I've tried deleting the docker image and reinstalling all the docker apps to no avail. This is happening on both of my unraid servers Any suggestions? apollo-diagnostics-20210301-1957.zip
  19. Darrell
    Great container. Thanks! Are there any plans to add privoxy support?
  20. Darrell
    I just discovered recordings-autoconverter. It works beautifully! Thanks for creating it and sharing with the community. Is there any option to have recordings-autoconverter leave the audio untouched? I have a 5.1 Home Theatre setup and would like to keep the 5.1 audio instead of convert it to 2 channel stereo. Thanks
  21. Darrell
    Thanks very much
  22. Darrell
    I'm new to Unraid, so please forgive my ignorance... I can't find a help button for the plugin. The only support I see is a link to this thread