TristanP

unRAID has the ability to send system notifications via email. However my SMTP service provider requires SASL to be able to authenticate. How do I go about setting up SASL so unRAID can use my provider to be able to send email?

Finally got time and puled the LSI SAS controller with no change. I them pulled the SAS Expander card (HP 468405-002) and disconnected it from the MB. Now I get a new error: That's after I redid the original USB with the latest unRAID writer (See above). Gotta admit....This is a new error for me.

Thanks for the suggestion. Now off to trial and error

Did the above. No change from the new one. Here's a screen shot of the console (Wish I could get the entire output):

Just to make sure: - Copy the /config directory off the flash drive - Use the unRAID USB creator to rewrite the 6.11.5 version back on the stick - Copy the /config directory back Sorry for being dense but before I do destructive operations I want to make sure I understand the process.

I'll give it a shot. I thought the license was tied to some unique id on the USB stick though, So I downloaded the USB creator, created a new flash drive with the correct version (6.11.5) and copied the old /config folder onto the USB /config. Unfortunately it seems to have gotten worse. There are now dozens of listings after this text: instead of just the one prior. And there it sits. It's wondering what is going on that annoys me. Sigh

I shutdown my unRAID machine to remove two unneeded disks and reroute cables. That went smoothly and the SAS controllers showed the right drives on the right interface. While booting it spit out the following: And there it sits. Pushing 30 minutes now. Any ideas what may be going on? Do I interrupt it or let it run. I am using unRAID v6.11.5. Thanks.

You're not kidding that the documentation is crappy. But I did as you suggested. Now off to see if I can tweak the api docker. EDIT: Once I did this and restarted the API docker it created /app/vikunja/files/[config|data] directories and created the default config.yml file. Now I have two But which one gets precedence? I wonder if I can unmount /etc/vikunja and it'll use the files and directories it just created.

I have two questions about the vikunja-api container. Thanks to LTM I have the front end and API dockers working and talking to each other. The first is: how does one create an admin account? I can create normal users but not an admin account The second is: There's no config.yml anywhere in the api docker image. If I create a new one where does the docker image expect it to be?

It doesn't unfortunately. All it does is demand a server location, even if none are listed (Even after a restart of the docker container).

Running unRAID 6.9.2 I goofed up my Jellyfin docker config (Linixserver version) so I uninstalled the docker and deleted the directory in appdata. However on reinstall the docker container said there was an existing server on unRAID and would not kick of the first time install script. I repeated the above process and used a different jellyfin docker image (Jellyfin's direct official image) and now I have two. Each instance is using an unique string (I'd say GUID but it's not the official MS format) that doesn't seem to exist anywhere on disk. What can I do to convince the docker engine to remove these "ghost" servers? I tried rebooting unRAID to no effect.

Running unRAID 6.9.2 I have removed the Jellyfin docker image and the directory in /mnt/user/appdata. However after reinstalling the image instead of going through the usual initialization process it asks for a server. I give it the IP and port of itself and shockingly it is unable to log in. What am I missing to convince Jellyfin to go through it's initialization process?

Yup. I seem to like putting random characters like that in output. Everything else looks fine.

I have been mounting several CIFS shares from an unRAID (v6.8.3) instance on a Centos VM for months without issue. With the new kernel and package update (Called 8.2) all I get from trying to mount the share is the following: domain=cargo.<personal domain> mount.cifs kernel mount options: ip=1q92.168.1.118, unc=\\cargo.<personal domain>\Video,vers=3.0,sec=ntlmsspi,file_mode=0777,user=<valid share user>,domain=cargo.<personal domain>,pass=********* mount error(13): Permission denied The share can still easily be mounted on a Windows machine and via smbclient without error. The behavior has changed with this update. Does anyone have any insight what may have changed and what I should look at to try and determine what specifically is wrong? Also it looks like the SMB logs are turned off on unRAID. What's the proper changes to get Samba to log logon failures? Here's other info: Output of uname -or: 4.18.0-193.19.1.el8_2.x86_64 GNU/Linux fstab line: //cargo.<personal domain>/Video /mnt/movies cifs vers=3.0,credentials=/root/creds_smb_library_core,sec=ntlmsspi,file_mode=0777,dir_mode=0777 0 0 credential file: username=<valid share user> password=<valid password>

Can someone tell me where the Nextcloud error logs are located? This latest version reports that the "Community Document Server" and "Talk" fail to install when the docker image is installed. However after login I see both listed under Apps but when I click on "Remove" Nextcloud reports "an error occured". Can't diagnose when the error message is "It's broken".