Openrepos down, or certificate expired?

Applications
82

I had this with browser in the morning but now it is working againđŸ’Ș

83

openrepos.net is working fine, their current certificate starts at Jan 21. But the patchmanager’s web catalog has a separate cerrtificate which is expired since yesterday.

Not sure about other subdomains, haven’t checked.

Since the openrepos certificate includes plenty of subdomains already, can it not be shared with these subdomains? @Basil, @coderus?

84

should be fine now.

chars up to 20

9 Likes
85

The OpenRepos certificate expiration be like:

4 Likes
86

Here we go again. No need to say it.

4 Likes
87

@Basil @coderus im experienced with automated certificates and renewal from Lets encrypt, if you need / want my help to Automate the renewal process, please ping me. I would offer some help

19 Likes
88

Just my two cents
: Wouldn’t it be a good idea if Jolla opened up their store a bit for apps like these? Or maybe a “Beta Section” or something similar for untested apps
 Don’t get me wrong. I appreciate the work done by the guys at Openrepos. These apps are essential!! However, for the future, an alternative—and above all, an official—solution would be better. Just my opinion. P.S. Openrepos still doesn’t have a certificate, and the same goes for the patch manager


3 Likes
89

Just to note that Let’s Encrypt is in the process of reducing (by 2028) the renewal period for issued certificates from the current 90 days to 45 days, so I’d hope that will be a reliable automation solution in place for openrepos.net.

90

Is this ever going to be updated? It’s been a while now


91

I have commented on this before; since then the patchmanager web catalog and openrepos proper share the same certificate. This is progress.

I suspect that something still isn’t working properly with Letsencrypt automation. These certs are only valid for 3 months and therefore automation is basically a must.

BTW the sites are still encrypted despite the browser basically telling you that this is just as bad as a completely unencrypted connection.

Are softwares affected by this? Meaning Storeman and Patchmanager? Shouldn’t they have a setting to ignore certificate errors?

1 Like
92

Storeman says “Network error”

I think having such a setting to work around failed certificate management is dangerous. My understanding is that it would enable a man-in-the-middle to serve malware-enriched apps to your device.

93

Thanks for Update. Runs :wink:

94

My guess is that the post-renewal hook is not in place as the server always after these events seems to come back up with a certificate that is a month old – i.e. the actual renewal probably takes place in the default timeframe, but the renewed certificate is not loaded by the server process until someone manually restarts/reloads it.

95

yes, that could be indeed the case - i forgot that in the past several times on my servers to reload new created certificates until i automated it via script.

If - for example - NGINX is used, after new certificates are created, a reload will get the new certificates without the need to stop or restart the service:

systemctl reload nginx

1 Like
96

Exactly, and very often in certbot setups this command would be in the renew hook, configured in /etc/letsencrypt/renewal/<sitename>.conf in the section [renewalparams] as follows:

[renewalparams]
renew_hook = systemctl reload nginx

That is all it takes for the command to run automatically after every certificate renewal.

3 Likes
97

Hi all, looks like this has not been automated as again the certificate has expired

Not After Sat, 20 Jun 2026 23:08:10 GMT

:slight_smile:

4 Likes
98

Is it possible to add a permanent SSL exception for openrepos.net in Storeman? I guess that’s a feature request.

1 Like
99

Maybe cronjob with automatic certificate upate on openrepos site would help here?

100

Or better yet an endpoint support so I can create and set my own proxy.

101 
## Disable SSL checks for openrepos
me=backup
for i in /etc/zypp/repos.d/ssu_openrepos-*.repo; do
    cp "$i" "$i".$me
    sed -i '/^baseurl=/ s/$/\&ssl_verify=no/' "$i"
done
i=/etc/ssu/ssu.ini
cp "$i" "$i.$me"
sed -i '/^openrepos-/ s/$/\?ssl_verify=no/' "$i"
sed -i '/^harbour-storeman-obs=/ s/$/\?ssl_verify=no/' "$i"

This helps at least for updating installed packages, unfortunately not much more beyond that. Only use if you know how to move the backup’d files back into their original place.

1 Like