Messages

1

22.1 Legacy Series / Re: [FIXED] - Unable to update to 22.1.8

« on: May 26, 2022, 09:15:44 pm »

Thank you Franco that makes sense.

I'll switch to another mirror. I just chose that one as there are no mirrors close to me at all (New Zealand). Cheers!

2

22.1 Legacy Series / Re: Unable to update to 22.1.8

« on: May 26, 2022, 09:02:16 pm »

After a few experiments, it seems that the reason was an outdated/broken mirror.

Thank you very much! It was in fact an outdated mirror. It worked just fine this morning using the mirro I had selected before (cloudflare). Thank you all for the help. Cheers!

3

22.1 Legacy Series / [FIXED] - Unable to update to 22.1.8

« on: May 25, 2022, 09:53:43 pm »

I attempted to run the update to 22.1.8 this morning, but it is failing.

The software seems to thin it's on 22.1.5 even though it's on 22.1.7. I show as being on

Code: [Select]

OPNsense 22.1.7_1-amd64
I attempt to update and the following shows

Code: [Select]

    ***GOT REQUEST TO UPDATE***
    Currently running OPNsense 22.1.7_1 (amd64/OpenSSL) at Thu May 26 07:41:51 NZST 2022
    Updating OPNsense repository catalogue...
    OPNsense repository is up to date.
    Updating mimugmail repository catalogue...
    mimugmail repository is up to date.
    All repositories are up to date.
    Updating OPNsense repository catalogue...
    OPNsense repository is up to date.
    Updating mimugmail repository catalogue...
    mimugmail repository is up to date.
    All repositories are up to date.
    Checking for upgrades (61 candidates): .......... done
    Processing candidates (61 candidates): ... done
    The following 18 package(s) will be affected (of 0 checked):
   
    Installed packages to be UPGRADED:
    crowdsec: 1.3.3 -> 1.3.4 [OPNsense]
    curl: 7.83.0 -> 7.83.1 [OPNsense]
    glib: 2.70.4_5,2 -> 2.70.4_6,2 [OPNsense]
    libffi: 3.3_1 -> 3.4.2 [OPNsense]
    libfido2: 1.10.0 -> 1.11.0 [OPNsense]
    libnghttp2: 1.46.0 -> 1.47.0 [OPNsense]
    openssl: 1.1.1o,1 -> 1.1.1o_1,1 [OPNsense]
    opnsense: 22.1.7_1 -> 22.1.8 [OPNsense]
    opnsense-update: 22.1.5 -> 22.1.8 [OPNsense]
    php74-pecl-radius: 1.4.0b1_1 -> 1.4.0b1_2 [OPNsense]
    py38-cffi: 1.15.0 -> 1.15.0_1 [OPNsense]
    py38-cryptography: 3.3.2 -> 3.4.8 [OPNsense]
    python38: 3.8.13_1 -> 3.8.13_2 [OPNsense]
    sqlite3: 3.37.2_1,1 -> 3.38.2,1 [OPNsense]
    strongswan: 5.9.5 -> 5.9.6 [OPNsense]
    telegraf: 1.22.3 -> 1.22.4 [OPNsense]
   
    Installed packages to be REINSTALLED:
    cyrus-sasl-2.1.28 [OPNsense] (options changed)
    pcre2-10.40 [OPNsense] (options changed)
   
    Number of packages to be upgraded: 16
    Number of packages to be reinstalled: 2
   
    40 MiB to be downloaded.
    [1/11] Fetching pcre2-10.40.pkg: .......... done
    pkg-static: cached package pcre2-10.40: size mismatch, fetching from remote
    [2/11] Fetching pcre2-10.40.pkg: .......... done
    pkg-static: cached package pcre2-10.40: size mismatch, cannot continue
    Consider running 'pkg update -f'
    Starting web GUI...done.
    Generating RRD graphs...done.
    ***DONE***

I ran the force update as requested in the log and it stated everything was up to date:

Code: [Select]

    root@OPNsense:~ # pkg update -f
    Updating OPNsense repository catalogue...
    Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
    Fetching packagesite.pkg: 100%  219 KiB 223.9kB/s    00:01
    Processing entries: 100%
    OPNsense repository update completed. 793 packages processed.
    Updating mimugmail repository catalogue...
    Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
    Fetching packagesite.pkg: 100%   52 KiB  53.0kB/s    00:01
    Processing entries: 100%
    mimugmail repository update completed. 172 packages processed.
    All repositories are up to date.
I rebooted and got the same for the updates. Attached are photos of the current version under dashboard and the version it seems to be attempting to update from. Not sure if it's due to the misreporting of the version (22.1.5 instead of 22.1.7). Any help would be greatly appreciated. Cheers.

4

Documentation and Translation / Re: AdGuard Home setup guide

« on: May 11, 2022, 06:06:44 am »

This broke unraid for me as well, not sure what happened that broke it, but it started in the past 3 days. I went to update today, and couldn't update anything.

Even when I set the DNS on unraid to use something else (quad9 in my case), it still tried to go through adguard and got blocked.