I’m encountering the same error on a freshly installed omv 3. If this is something caused by an update, shouldn’t it be fixed in omv source instead of by the user?
Can we not fix this for everyone with a patch update?
I’m encountering the same error on a freshly installed omv 3. If this is something caused by an update, shouldn’t it be fixed in omv source instead of by the user?
Can we not fix this for everyone with a patch update?