Unreachable: https://repo.turris.cz/omnia/lists/base.lua:


#1

My router send me this message:

Error notifications

Updater failed:
unreachable: https://repo.turris.cz/omnia/lists/base.lua: SSL certificate problem: self signed certificate

What does it mean? What did it try?


#2

Hello,
can you try it again?

This was caused by:


#4

It still has to find out that there is an update to be approved :wink:


#5

I’ve got the same issue.

In Forris:

Error from 2017/12/18 16:23:01
Updater failed:
unreachable: https://repo.turris.cz/turris/lists/base.lua: SSL certificate problem: self signed certificate

Now, after logging to ssh:

root@turris:~# updater.sh 
WARN:Script file:///usr/share/updater/localrepo/localrepo.lua not found, but ignoring its absence as requested
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
WARN:Requested package foris-netmetr-plugin-l10n-cs that is missing, ignoring as requested.
WARN:Requested package kmod-crypto-arc4 that is missing, ignoring as requested.
WARN:Requested package libi2c that is missing, ignoring as requested.
Log: layer_ni2c: ni2c_read: Read packet failed
Working on message: 1513610581-15050
There is no message to send.

Turris 1.1,
Turris OS version 3.9
Kernel version 4.4.103-10d3ee495c67f4b8dea965e37ab9cc62-1


#7

For the record. Happened again today at noon. I was a little bit scared seeing repo.turris.cz has ‘CN=proxy’. Disappeared cca after two minutes.

wget -S https://repo.turris.cz/omnia/lists/base.lua
–2019-06-12 00:01:44-- https://repo.turris.cz/omnia/lists/base.lua
Resolving repo.turris.cz (repo.turris.cz)… 217.31.192.69, 2001:1488:ac15:ff80::69
Connecting to repo.turris.cz (repo.turris.cz)|217.31.192.69|:443… connected.
ERROR: cannot verify repo.turris.cz’s certificate, issued by ‘CN=proxy’:
Self-signed certificate encountered.
ERROR: no certificate subject alternative name matches
requested host name ‘repo.turris.cz’.
To connect to repo.turris.cz insecurely, use `–no-check-certificate’.


#8

hi, this is related to Outage of some of our services

You probably hit the mean time I was deploying out proxy server to a new hypervisor.


closed #9

This topic was automatically closed after 40 hours. New replies are no longer allowed.