Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

illegal-deference8464

Members
  • Joined

  • Last visited

Everything posted by illegal-deference8464

  1. This looks super cool im new to php but if im understanding this right if i wanted to expand on this. i have a few questions for you if you have some time to chat about it.
  2. so i rebuilt the server and started over and then updated again and it started again. it seems something in the update system keeps breaking it. im not sure where to go from here when i run the "ss -tulpn" it says "bash: ss: command not found"
  3. maybe not update but since last restart of it atleast. i moved it to the top of my list of containers to start as well so it would kick off first
  4. Nothing else should be running on that ip i also attempted to change ip address and get same error this is from the unraid console inside the docker container
  5. i just updated my container and started getting this error has anyone else experienced it lately? ❯ Starting nginx ... nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] still could not bind()
  6. oh its off the development branch not the nightly. ok thank you
  7. what determines the build of readarr you are using in this repo? there are some updates that were released today that i would like to get that fix some bugs im getting @binhex
  8. ok we are up for 2 days straight now slowly enabling more dockers and i think we are working now!. thank you for your help
  9. ok so it kept happening then i remembered that i was having issues with 2 sticks of the ram i put in here and thats why i had extras around. i swapped out the ram for a different set of 2 sticks so we will monitor it now for the next few days and see what happens
  10. here is syslog from last crash and i havent ran it since syslog
  11. @JorgeB any other ideas? i can try to get another diagnostic bundle and i was running syslog when it crashed on me last time. i also have clocked the ram down to the 1886 since its 2x2 8Gb sticks,
  12. so i finally got this all reconnected and everything reseated, i have one drive showing as disabled so when attempting to start the array in maintenance mode to rebuild it i had to leave before i could start it and it crashed while i was gone. makarov-diagnostics-20230901-2308.zip so im gonna attempt to rebuild disc 5 with the same disc now that im home and watching it
  13. alright i am making some changes and adding more drives tomorrow, i will swap out ram and i dont think its over clocked its supposed to be 3200 or 3400 but i will correct it if thats also there. and ill rebuild the qbittorent docker
  14. i also found this in my clipboard from the logs. i think it might be related? it looks like issues with my cache drive. makarov-diagnostics-20230826-0913.zip
  15. I believe I also got a call trace? I think it said
  16. i had several dockers that after my server did a kernel panic seem to have reverted to an older config. and im routinely getting kernel panics now. makarov-diagnostics-20230826-0046.zip tower-diagnostics-20230825-2346.zip
  17. that kind of worked i got as much data off of it i could. i still lost a couple hundred gigs of downloads and some application conffigurations that i set yesterday but. im back up and running thank you for your help
  18. do i type that in the terminal in the web gui or how do i start that?
  19. I lost power last night and cant get my array to start looking at the log i think it is my cache drive, but i dont know how i can get it mounted to copy files off of it or what i can do any help would be appreciated. included diagnostics bundle but i dont know how helpful it will be with the server getting stuck and unable to export diagnostics once i have attempted to start the array tower-diagnostics-20230824-0933.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.