Is 10.9.70.175 the IP of your server? Assuming so, I'm oretty sure that's the problem. TBH I'm not particularly familiar with ownCloud but it looks to me like the update mechanism is trying to connect to itself via https. SSL/TLS certificates for IP addresses are not possible (under normal circumstance) so when it tries to connect to https://10.9.70.175 the SSL/TLS certificate (probably the self signed one that our appliance ships with) doesn't match the IP address so is considered invalid. Even if you access via a domain name, it will still fail as a self signed certificate is not considered "secure".

Also, to interrupt myself - if you haven't already, make sure that you have a working backup of your server - or at least your ownCloud directory and database. You may have already done it, but it would be remiss of me to not remind you.

If you really want the web UI upgrade to work and your server isn't publicly available (i.e. only available via a LAN), then one approach you could try is to disable the website http -> https redirect (in the Apache config). Then instead of accessing your server via https, use http instead. I can't guarantee that will work as it may not allow upgrade via an unencrypted connection, but could be worth a try?

The "proper" way to support a web UI upgrade would be to use a registered domain and get a "proper" CA signed SSL/TLS certificate for the domain. You can do that without needing your ownCloud server to be publicly available, but I won't get into the details of that here (ask if you want and I can give some pointers). With a domain and a CA signed cert, if you access your server via that domain via https, then I would expect the web UI upgrade should "just work".

If you don't need/want a domain and "valid" cert, then AFAIK using the "updater app" via CLI should work. Try that like this:

turnkey-occ upgrade

I would expect that to work fine, but it is possible that the same issue may occur - because the "updater app" CLI method essentially uses the same code as the web UI one. If it doesn't work, the OwnCloud docs recommend a manual upgrade instead.

The docs note that there is a "semi-manual" script guided upgrade method. Or a "full manual" upgrade via the doc instructions.

Please report back with your progress regardless. If you get stuck again hopefully I can help. If you are successful, your upgrade notes will be useful for others. Good luck.

That does seem very strange!? TBH I'm not really sure why that might happen, but I had a quick google and it sounds like there are a number of possible causes of that specific situation.

The first thing to check is that the "apps" directories exist and are writable.

They are most likely, but to be "/var/www/owncloud/apps" and "/var/www/owncloud/apps-external" but to be sure it's best to check the paths in the config file - which should be /var/www/owncloud/conf/config.php. Using grep is a quicker/easier way to get just the specific info:

grep apps_paths -A 11 /var/www/owncloud/conf/config.php

(finds the line/s that include 'apps_paths' and return that line and 11 lines after)

That should return something like this:

“apps_paths”: [
{
“path”: “/var/www/owncloud/apps”,
“url”: “/apps”,
“writable”: false
},
{
“path”: “/var/www/owncloud/apps-external”,
“url”: “/apps-external”,
“writable”: true
}
],

AFAIK there should only be 2 paths noted there, but if the last line of your output isn't '],' (notes the end of the apps_paths array) then double check by increasing the '11' in the grep command - e.g. try "-A 14".

I'll assume that the values in your config file match those noted above. If yours are different, be sure to change the paths in the commands I note below.

Once you've confirmed the paths, then make sure that they exist and are writable by the webserver user:

mkdir -p /var/www/owncloud/apps
chown -R www-data:www-data /var/www/owncloud/apps

mkdir -p  /var/www/owncloud/apps-external
chown -R www-data:www-data /var/www/owncloud/apps-external

Then open the config file in your preffered editor (if you're not sure, nano is a good option). Ensure that both of the "apps_paths" are configured as "writeable". E.g. given the above config snippet I would change:

“path”: “/var/www/owncloud/apps”,
“url”: “/apps”,
“writable”: false

To

“path”: “/var/www/owncloud/apps”,
“url”: “/apps”,
“writable”: true

(the other one is already “writable” in my example conf so doesn't need to be updated).

Then retry the 'turnkey-occ upgrade' command again. If nothing changes, then see if there is anything in the ownCloud log - which should be in /var/www/owncloud/data - I'm not exactly sure of the name of the log file, but it should include 'log' so be pretty obvious.

If you still continue to have the same issue, please post back. Feel free to post any log output or any other info you think might be relevant. Unless something jumps out at me from what you share, I'll probably have to launch one myself and have a poke around.

Either way, please post back.