If you need to install something from OpenRepos, you can download the rpm with browser and then side load.
Thanks a lot, this worked perfectlyđ
That is an easy procedure for new application. I am more worried about updates. Probably that needs manual tracking and sideloading
Storeman is breaking the Sailfish update. I was having trouble updating to 4.6.0.15 till I disabled all the repos in Storeman
I will disable all stores in Storeman before starting the SFOS update. I will enable the stores and execute devel-su pkcon refresh after the SFOS update is complete. Maybe it would help you.
Will not work! My advice is to forget about using Storeman until certificate is renewed. Donât even try to reenable repositories, that will only result in âendlessâ error messages.
ExactlyâŚ
As Matias said above, you just have to manually set the date in the Sailfish settings back a few days, and Storeman works again (and Sailfish updates too). No need to deactivate repos or to sideload apps through the browser.
I wouldnât do that, as it will trigger other system errors, but thatâs me.
It âmightâ, maybe, but it didnât trigger any errors on my XA2, when Iâve updated to 4.6.0.15. And adjusting the date temporarily to be able to get the latest app updates with Storeman should be riskfree.
Works for me at the moment.
To debug the issue, in terminal use e.g.
openssl s_client -connect openrepos.net:443
This will tell you, if the certificate is the issue. For me it returns (apart from some other stuff):
Verify return code: 0 (ok)
The Letâs Encrypt intermediate certificate changed recently. Maybe thatâs the culprit.
Storeman seems to be back up.
Yes, the TLS certificate has been renewed. Until next time, Friday, 27 December 2024 17:10:09 GMT⌠
Today Storeman is back on my phones without doing anything, but just waited. Thank you very much!
is openrepos down or is it just me?
Storeman on the phone and OpenRepos on computer works normal for me.
11:40 West european DST.
thanks, I need to do more testing but still not working on my side.
It is not only you. There is DNS issue with openrepos.net.
ah thanks for the info, I thought my vpn or something on my side could be causing the issue.
Actually, it seems that the domain openrepos.net expired:
$ whois openrepos.net
Domain Name: OPENREPOS.NET
Registry Domain ID: 1813071317_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.r01.ru
Registrar URL: http://r01.ru
Updated Date: 2025-07-08T00:31:09Z
Creation Date: 2013-07-05T15:42:43Z
Registry Expiry Date: 2026-07-05T15:42:43Z
Registrar: Registrar R01 LLC
Registrar IANA ID: 1426
Registrar Abuse Contact Email: tld-abuse@r01.ru
Registrar Abuse Contact Phone: +7(495) 783-3-783
Domain Status: clientHold https://icann.org/epp#clientHold
Name Server: NS1.R01.RU
Name Server: NS2.R01.RU
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
This is likely up to @basil to solve, as heâs the owner of the domain.