Update owncloud 9.0.4 to 9.1.0 through the center updates

Server
1

Hello! has decided to continue the further updatings from 9.0.4 to 9.1.0.

In the center of renovation choose the beta channel. Next, choose to open the update window.
a minute later I receive an error:

_[GuzzleHttp\Ring\Exception\ConnectException] _
cURL error 7: Failed to connect to xxx.xxx.xxx.xxx port 443: Connection timed out

Prompt please with what it can be connected?
How can it be cured?
Thank you!

2

Please do a manual upgrade like described here:

https://doc.owncloud.org/server/9.1/admin_manual/maintenance/manual_upgrade.html

9.0.4 -> 9.0.5 -> 9.1.1

3

Do I understand correctly that the version 9.1.0 can be skipped?
Thank you!

4

Yes, its always only the latest version you need to update to. An upgrade path from 8.2.3 for example would be:

8.2.3 -> latest 8.2.x -> latest 9.0.x -> latest 9.1.x

without any older versions in between.

5

RealRancor,
Thank you! Update successful

6

Great. The updater shipped with oC 9.1.1 might be not showing this issue so it could be possible that you can use the updater onwards without doing that steps.

7

Just some additional info. It seems that the "beta" channel is actually even providing 9.1.0 RC1 where it is claiming that 9.1.0 is shipped. In between there where also RC2, RC3 and RC4.

8

Hi All,
Although this issue has been fixed by manual update, I would like to share the solution where you can run the update from web gui for anyone that is searching around in this error just like me.
The reason we get "Failed to connect to xxx.xxx.xxx.xxx port 443: Connection timed out" is due to no connection from public to your owncloud server from owncloud server itself.
Let me explain more. Normally, owncloud server is hosted in DMZ or your LAN and you NAT 443 traffic from your firewall to your OC server. Therefore OC server cannot access itself from NAT public IP.
Solution is that change DNS server on your OC server or create alias so that when you ping your OC DNS, it should resolve local IP rather than public IP. Once you doing that, web gui update could run without curl error.
Change DNS server or remove alias once upgrade is done.
I just did on my server and want to share to everyone.

Regards.