I'm getting that same error with Plex.I still get it though the error message in the log is different.
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Get \"https://192.168.2.230:10250/contain...true\u0026tailLines=500\u0026timestamps=true\": x509: certificate is valid for 127.0.0.1, 0.0.0.0, not 192.168.2.230","code":500}
The snapshot and replication also causing this is indeed a bug iX has been made ware of :)I thought this was a bug without a workaround in the nightlies I was trying until I came across this thread. For me, SMB shares and the SMB service running wasn't the issue. Once I disable snapshot/replication tasks on the datasets used by the apps I was able to get them started again.
This issue is killing me... Is there a jira ticket opened for this already?
Just to be sure I understand this correctly... I should NOT set and SMB share for a folder used by an app? Is that correct?
If so, what is the "correct" way to access folders that I cannot share?
chmod -R 777 /mnt/path to container storage folder
Thats what iX has decided for 22.12 "Bluefin" yes.
(to be clear: this rule does not apply to 22.02.04!)
Does this apply to the Plex config location, or to the media location too? I have the media location shared via SMB for easy access - will this no longer be practical in future releases?
+1 on this question for plex and other apps. Do I understand correctly that only the app storage/config dataset is restricted from using SMB shares? Meaning it is acceptable for additional storage added to the app (e.g. plex media files) to use a dataset with SMB and ACLs?Does this apply to the Plex config location, or to the media location too? I have the media location shared via SMB for easy access - will this no longer be practical in future releases?
This applies to all(!) cases of hostPath based storage on Bluefin.
/mnt/pool/dataset
as base, for example /mnt/default/media
. Inside it, you can create or move all the directories you want and never worry about any issues in Plex or any other application. This is actually the intended use of a shared dataset.