Hardware: Dell Poweredge R710 YunoHost version: Powered by YunoHost 3.8.4.8 (stable). I have access to my server : Through SSH & through the webadmin Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
After running into issues with Jeedom working I managed to get jeedom.DOMAIN.COM working by changing the CAA from flag 128 to 0 for let’s encrypt.
Jeedom now opens, but it spits back The directory “/tmp/jeedom/cache” is not writable. and shows a blank screen.
I am wondering, I just realized that I might be “in a special context or did you perform some particular tweaking on your YunoHost instance ?”
My server wouldn’t let me download YUNO directly so I had to install debian first AND THEN jump over to yuno through “curl https://install.yunohost.org | bash”.
Can you check the permissions again?
I don’t know how the current jeedom YNH package works, but a few years ago I abandoned trying to fit jeedom in yunohost.
Jeedom ran a script every few minutes by Cron that messes all the permissions up. It modifies the /tmp permissions and even the webroot ones…
I like jeedom but it really is designed to be on it’s own machine. Even Docker is suboptimal.
Otherwise you can install it without root access. But you will have to install many of the plugins by hand (e.g. openzwave) and some will refuse to run