I just need to RTFM in future.

Onefang, thanks for the excellent clarification.

Sometime I just get a bit paranoid and maybe I should switch to a https mirror.

I used to use the more specific, if still http, gb.deb.devuan.org until that was deprecated and we were recommended to use deb.devuan.org.

Maybe a disclaimer in the documentation about its load-sharing round-robin nature would help.

Documentation covering all those points is (and has been) on the website, in the installer and now also stickied here:

Index
    » Documentation
    » Devuan package mirrors, deb.devuan.org, HTTPS, and mirror monitoring

Sometime I just get a bit paranoid and maybe I should switch to a https mirror.

I used to use the more specific, if still http, gb.deb.devuan.org until that was deprecated and we were recommended to use deb.devuan.org.

Maybe a disclaimer in the documentation about its load-sharing round-robin nature would help.

The name deb.devuan.org is a DNS round robin, which means that when you try to access it you will be sent to one of the mirrors that are part of it.  None of those mirrors have a HTTPS certificate that matches "deb.devuan.org", but likely have their own HTTPS certificate, due to the security issues involved in letting lots of people have a copy of a security certificate.  So all use of deb.devuan.org must be done via HTTP, as using HTTPS will result in the errors you have seen.

If you do wish to use HTTPS, you should instead directly use one of the mirrors that supports HTTPS.  https://pkgmaster.devuan.org/mirror_list.txt lists all the mirrors, and what protocols they support.

I am also the author of apt-panopticon, a script that regularly checks the health of the entire Devuan mirror system.  The results of that script are currently available on two servers.  https://borta.devuan.dev/apt-panopticon … t-web.html which checks the mirrors once an hour, though is currently having timeout problems which are being investigated.  https://sledjhamr.org/apt-panopticon/re … t-web.html which checks every ten minutes.

With large parts of the world working from home as part of COVID-19 lockdowns, the Internet is being used more than is usual.  So there tends to be more random network issues.  Any particular network issue might be at your end, at the other end, or somewhere in between.

It's good to see your issue fixed itself.

Still odd about the SSL Server Certificate being wrong though (of course http doesn't have a certificate).

i assume my original problem was because there was a short outage, which is now fixed.

rolfie

However still getting the SSL server certificate error however (it's a free Lets Encrypt Cert).
Is it just one of the sysops setting it up wrong, and reusing another certificate?

No I'm not using https://.

The repository list is unchanged from when it was working yesterday.

I realise that I can switch to another mirror, and may do that now, but I thought I ought to flag up the issue, since this is the recommended mirror.

And that doesn't explain the web certificate issue.

And trying to access the site using Firefox-esr I get a certificate error, saying that the certificate is only good for sledjhamr.org.

Acessing devuan.org and beta.devuan.org on Firefox-esr is fine.

Is the problem at my end or wiith deb.devuan.org?