Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(17) |
Sep
|
Oct
(1) |
Nov
(11) |
Dec
|
| 2026 |
Jan
(3) |
Feb
(10) |
Mar
(8) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
|
From: Lonnie A. <li...@lo...> - 2026-09-03 14:47:25
|
Hi Michael, I have seen Github randomly not show certain parts of repos unless logged-in with credentials. Too much AI bot traffic triggers the gating I suspect. Lonnie > On Sep 3, 2026, at 9:27 AM, Michael Keuter <li...@mk...> wrote: > > Hi Lonnie, > > thanks for the doku. > Just to be clear: I had this issue on 3 different locations (all around Hamburg, Germany) with at least 2 different ISPs. All these Pi-holes were running fine for years (they are running Debian 11 underneath). > Yesterday I wasn't able to create a new Pi-hole container with Debian 12, but Debian 13 worked. Today I tested again and now it worked. I have a script that does the same as you did, so no typos are possible. Very strange. > > Michael > > https://mksolutions.info > > >> Am 03.09.2026 um 15:19 schrieb Lonnie Abelbeck <li...@lo...>: >> >> Hi Michael, >> >> I had no issue creating a working pi-hole LXC in AstLinux. Only change from the docs was to add 'git' to the 'apt install'. (I updated wiki) >> >> The host was a MeLE QuieterDL CPU N100 >> >> <Screenshot 2026-09-03 at 8.10.34 AM.png> >> >> Detailed install at the end of this message. >> >> I added a NAT forward: >> >> <Screenshot 2026-09-03 at 8.05.17 AM.png> >> >> Accessed with: http://minipc.priv.abelbeck.com:8888/admin/ >> >> <Screenshot 2026-09-03 at 8.04.18 AM.png> >> >> >> Detailed install below: >> >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> minipc ~ # lxc-create -t download -n pi-hole -- -d debian -r bookworm -a amd64 --no-validate >> ... >> >> minipc ~ # service lxc restart >> Stopping LXC container... >> Starting LXC container... >> >> minipc ~ # lxc-attach pi-hole >> root@pi-hole:/# passwd >> New password: >> Retype new password: >> passwd: password updated successfully >> >> root@pi-hole:/# apt update >> ... >> All packages are up to date. >> >> root@pi-hole:/# apt install openssh-server iputils-ping curl git >> ... >> >> root@pi-hole:/# vi /etc/ssh/ssh_config >> root@pi-hole:/# exit >> exit >> >> minipc ~ # lxc-attach pi-hole >> root@pi-hole:/# cd >> root@pi-hole:~# mkdir install >> root@pi-hole:~# cd install/ >> root@pi-hole:~/install# curl -sSL https://install.pi-hole.net | bash >> >> [✓] Root user check >> >> .;;,. >> .ccccc:,. >> :cccclll:. ..,, >> :ccccclll. ;ooodc >> 'ccll:;ll .oooodc >> .;cll.;;looo:. >> .. ','. >> .',,,,,,'. >> .',,,,,,,,,,. >> .',,,,,,,,,,,,.... >> ....''',,,,,,,'....... >> ......... .... ......... >> .......... .......... >> .......... .......... >> ......... .... ......... >> ........,,,,,,,'...... >> ....',,,,,,,,,,,,. >> .',,,,,,,,,'. >> .',,,,,,'. >> ..'''. >> >> [i] SELinux not detected >> [✓] Update local cache of available packages >> [✓] Building dependency package pihole-meta.deb >> [✓] Installing Pi-hole dependency package >> >> [i] IPv4 address: 192.168.99.194/24 >> [i] Unable to find IPv6 ULA/GUA address >> [i] IPv6 address: >> [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) >> [i] Installing StevenBlack's Unified Hosts List >> [i] Query Logging off. >> [i] Using privacy level: 0 >> [✗] Check for existing repository in /etc/.pihole >> [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...HEAD is now at f47b8ed v6.4.3 (#6618) >> [✓] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole >> >> [✗] Check for existing repository in /var/www/html/admin >> [i] Clone https://github.com/pi-hole/web.git into /var/www/html/admin...HEAD is now at b2a4078 Web v6.6 (#3808) >> [✓] Clone https://github.com/pi-hole/web.git into /var/www/html/admin >> >> [✗] Checking for group 'pihole' >> [✓] Creating group 'pihole' >> [✓] Creating user 'pihole' >> >> [i] FTL Checks... >> >> [✓] Detected x86_64 architecture >> [✓] Downloading and Installing FTL >> [✓] Installing scripts from /etc/.pihole >> >> [i] Installing configs from /etc/.pihole... >> >> [✓] Installing latest Cron script >> >> [✓] Installing latest logrotate script >> [i] man not installed >> [i] Testing if systemd-resolved is enabled >> [✓] Disabling systemd-resolved DNSStubListener >> [i] Restarting services... >> [✓] Enabling pihole-FTL service to start on reboot... >> [✓] Restarting pihole-FTL service... >> [✓] DNS resolution is available >> >> [✗] Migrating the list's cache directory to new location >> [i] Creating new gravity database >> [i] Migrating content of /etc/pihole/adlists.list into new database >> [✓] Deleting existing list cache >> [i] Neutrino emissions detected... >> >> [✓] Preparing new gravity database >> [✓] Creating new gravity databases >> [✓] Pulling blocklist source list into range >> [i] Using libz compression >> >> [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts >> [✓] Status: Retrieval successful >> [✓] Parsed 78609 exact domains and 0 ABP-style domains (blocking, ignored 1 non-domain entries) >> Sample of non-domain entries: >> - fe80::1%lo0 >> >> [✓] Building gravity tree >> [✓] Building antigravity tree >> >> [i] Number of gravity domains: 78609 (78609 unique domains) >> [i] Number of antigravity domains: 0 (0 unique domains) >> [i] Number of exact denied domains: 0 >> [i] Number of regex denied filters: 0 >> [i] Number of exact allowed domains: 0 >> [i] Number of regex allowed filters: 0 >> >> [✓] Optimizing database >> [✓] Swapping databases >> [✓] The old database remains available >> [✓] Cleaning up stray matter >> >> [✓] Done. >> >> [i] You may now configure your devices to use the Pi-hole as their DNS server >> [i] Pi-hole DNS (IPv4): 192.168.99.194 >> [i] If you have not done so already, the above IP should be set to static. >> [i] View the web interface at http://pi.hole:80/admin or http://192.168.99.194:80/admin >> >> [i] Web Interface password: >> [i] This can be changed using 'pihole setpassword' >> >> [i] To allow your user to use all CLI functions without authentication, refer to >> our documentation at: https://docs.pi-hole.net/main/post-install/ >> >> >> [i] The install log is located at: /etc/pihole/install.log >> [✓] Installation complete! >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> >> Lonnie >> >> >> >>> On Sep 3, 2026, at 7:13 AM, Michael Keuter <li...@mk...> wrote: >>> >>> Hi David, >>> >>> good point! >>> >>> I was able to create a working Pi-hole container on Proxmox 8 ( Linux 6.8.12-43-pve) with a Debian 12 template (which doesn't work for me on AstLinux). >>> >>> Michael >>> >>> https://mksolutions.info >>> >>>> Am 02.09.2026 um 19:43 schrieb David Kerr <da...@ke...>: >>>> >>>> Have you tried in an LXC container on a different host (non-AstLinux)? Just to narrow down if the problem is AstLinux or something else. >>>> >>>> Does Pi-hole 6 require a specific kernel version? One of the "features" of containers like LXC is that they build upon the kernel of the host. AstLinux is on a 5.x kernel, so if Pi-hole needs something from a newer kernel then it might not work. >>>> >>>> David. >>>> >>>> On Wed, Sep 2, 2026 at 1:03 PM Michael Keuter <li...@mk...> wrote: >>>> Hi list, >>>> >>>> when I today tried to update a running Pi-hole 6 installation running in a LXC container on AstLinux, I was asked for my github username and password: >>>> >>>> ---- >>>> [i] SELinux not detected >>>> [✓] Update local cache of available packages >>>> [✓] Building dependency package pihole-meta.deb >>>> [✓] Installing Pi-hole dependency package >>>> >>>> [i] IPv4 address: 192.168.99.46/24 >>>> [i] Unable to find IPv6 ULA/GUA address >>>> [i] IPv6 address: >>>> [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) >>>> [i] Installing StevenBlack's Unified Hosts List >>>> [i] Query Logging on. >>>> [i] Using privacy level: 0 >>>> [✗] Check for existing repository in /etc/.pihole >>>> [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...Username for 'https://github.com': ^C >>>> ---- >>>> >>>> I tried out different things for quite some time. >>>> >>>> But I ended up creating a new LXC container with Debian 13 Trixie, installed Pi-hole and imported the "Teleporter" export I created before I started the update. >>>> The same error appeared on a newly created Debian 12 container :-(. All on the latest AstLinux 1.5.15-dev version. >>>> >>>> Michael > > > > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2026-09-03 14:28:07
|
Hi Lonnie, thanks for the doku. Just to be clear: I had this issue on 3 different locations (all around Hamburg, Germany) with at least 2 different ISPs. All these Pi-holes were running fine for years (they are running Debian 11 underneath). Yesterday I wasn't able to create a new Pi-hole container with Debian 12, but Debian 13 worked. Today I tested again and now it worked. I have a script that does the same as you did, so no typos are possible. Very strange. Michael https://mksolutions.info > Am 03.09.2026 um 15:19 schrieb Lonnie Abelbeck <li...@lo...>: > > Hi Michael, > > I had no issue creating a working pi-hole LXC in AstLinux. Only change from the docs was to add 'git' to the 'apt install'. (I updated wiki) > > The host was a MeLE QuieterDL CPU N100 > > <Screenshot 2026-09-03 at 8.10.34 AM.png> > > Detailed install at the end of this message. > > I added a NAT forward: > > <Screenshot 2026-09-03 at 8.05.17 AM.png> > > Accessed with: http://minipc.priv.abelbeck.com:8888/admin/ > > <Screenshot 2026-09-03 at 8.04.18 AM.png> > > > Detailed install below: > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=- > minipc ~ # lxc-create -t download -n pi-hole -- -d debian -r bookworm -a amd64 --no-validate > ... > > minipc ~ # service lxc restart > Stopping LXC container... > Starting LXC container... > > minipc ~ # lxc-attach pi-hole > root@pi-hole:/# passwd > New password: > Retype new password: > passwd: password updated successfully > > root@pi-hole:/# apt update > ... > All packages are up to date. > > root@pi-hole:/# apt install openssh-server iputils-ping curl git > ... > > root@pi-hole:/# vi /etc/ssh/ssh_config > root@pi-hole:/# exit > exit > > minipc ~ # lxc-attach pi-hole > root@pi-hole:/# cd > root@pi-hole:~# mkdir install > root@pi-hole:~# cd install/ > root@pi-hole:~/install# curl -sSL https://install.pi-hole.net | bash > > [✓] Root user check > > .;;,. > .ccccc:,. > :cccclll:. ..,, > :ccccclll. ;ooodc > 'ccll:;ll .oooodc > .;cll.;;looo:. > .. ','. > .',,,,,,'. > .',,,,,,,,,,. > .',,,,,,,,,,,,.... > ....''',,,,,,,'....... > ......... .... ......... > .......... .......... > .......... .......... > ......... .... ......... > ........,,,,,,,'...... > ....',,,,,,,,,,,,. > .',,,,,,,,,'. > .',,,,,,'. > ..'''. > > [i] SELinux not detected > [✓] Update local cache of available packages > [✓] Building dependency package pihole-meta.deb > [✓] Installing Pi-hole dependency package > > [i] IPv4 address: 192.168.99.194/24 > [i] Unable to find IPv6 ULA/GUA address > [i] IPv6 address: > [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) > [i] Installing StevenBlack's Unified Hosts List > [i] Query Logging off. > [i] Using privacy level: 0 > [✗] Check for existing repository in /etc/.pihole > [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...HEAD is now at f47b8ed v6.4.3 (#6618) > [✓] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole > > [✗] Check for existing repository in /var/www/html/admin > [i] Clone https://github.com/pi-hole/web.git into /var/www/html/admin...HEAD is now at b2a4078 Web v6.6 (#3808) > [✓] Clone https://github.com/pi-hole/web.git into /var/www/html/admin > > [✗] Checking for group 'pihole' > [✓] Creating group 'pihole' > [✓] Creating user 'pihole' > > [i] FTL Checks... > > [✓] Detected x86_64 architecture > [✓] Downloading and Installing FTL > [✓] Installing scripts from /etc/.pihole > > [i] Installing configs from /etc/.pihole... > > [✓] Installing latest Cron script > > [✓] Installing latest logrotate script > [i] man not installed > [i] Testing if systemd-resolved is enabled > [✓] Disabling systemd-resolved DNSStubListener > [i] Restarting services... > [✓] Enabling pihole-FTL service to start on reboot... > [✓] Restarting pihole-FTL service... > [✓] DNS resolution is available > > [✗] Migrating the list's cache directory to new location > [i] Creating new gravity database > [i] Migrating content of /etc/pihole/adlists.list into new database > [✓] Deleting existing list cache > [i] Neutrino emissions detected... > > [✓] Preparing new gravity database > [✓] Creating new gravity databases > [✓] Pulling blocklist source list into range > [i] Using libz compression > > [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts > [✓] Status: Retrieval successful > [✓] Parsed 78609 exact domains and 0 ABP-style domains (blocking, ignored 1 non-domain entries) > Sample of non-domain entries: > - fe80::1%lo0 > > [✓] Building gravity tree > [✓] Building antigravity tree > > [i] Number of gravity domains: 78609 (78609 unique domains) > [i] Number of antigravity domains: 0 (0 unique domains) > [i] Number of exact denied domains: 0 > [i] Number of regex denied filters: 0 > [i] Number of exact allowed domains: 0 > [i] Number of regex allowed filters: 0 > > [✓] Optimizing database > [✓] Swapping databases > [✓] The old database remains available > [✓] Cleaning up stray matter > > [✓] Done. > > [i] You may now configure your devices to use the Pi-hole as their DNS server > [i] Pi-hole DNS (IPv4): 192.168.99.194 > [i] If you have not done so already, the above IP should be set to static. > [i] View the web interface at http://pi.hole:80/admin or http://192.168.99.194:80/admin > > [i] Web Interface password: > [i] This can be changed using 'pihole setpassword' > > [i] To allow your user to use all CLI functions without authentication, refer to > our documentation at: https://docs.pi-hole.net/main/post-install/ > > > [i] The install log is located at: /etc/pihole/install.log > [✓] Installation complete! > -=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Lonnie > > > >> On Sep 3, 2026, at 7:13 AM, Michael Keuter <li...@mk...> wrote: >> >> Hi David, >> >> good point! >> >> I was able to create a working Pi-hole container on Proxmox 8 ( Linux 6.8.12-43-pve) with a Debian 12 template (which doesn't work for me on AstLinux). >> >> Michael >> >> https://mksolutions.info >> >>> Am 02.09.2026 um 19:43 schrieb David Kerr <da...@ke...>: >>> >>> Have you tried in an LXC container on a different host (non-AstLinux)? Just to narrow down if the problem is AstLinux or something else. >>> >>> Does Pi-hole 6 require a specific kernel version? One of the "features" of containers like LXC is that they build upon the kernel of the host. AstLinux is on a 5.x kernel, so if Pi-hole needs something from a newer kernel then it might not work. >>> >>> David. >>> >>> On Wed, Sep 2, 2026 at 1:03 PM Michael Keuter <li...@mk...> wrote: >>> Hi list, >>> >>> when I today tried to update a running Pi-hole 6 installation running in a LXC container on AstLinux, I was asked for my github username and password: >>> >>> ---- >>> [i] SELinux not detected >>> [✓] Update local cache of available packages >>> [✓] Building dependency package pihole-meta.deb >>> [✓] Installing Pi-hole dependency package >>> >>> [i] IPv4 address: 192.168.99.46/24 >>> [i] Unable to find IPv6 ULA/GUA address >>> [i] IPv6 address: >>> [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) >>> [i] Installing StevenBlack's Unified Hosts List >>> [i] Query Logging on. >>> [i] Using privacy level: 0 >>> [✗] Check for existing repository in /etc/.pihole >>> [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...Username for 'https://github.com': ^C >>> ---- >>> >>> I tried out different things for quite some time. >>> >>> But I ended up creating a new LXC container with Debian 13 Trixie, installed Pi-hole and imported the "Teleporter" export I created before I started the update. >>> The same error appeared on a newly created Debian 12 container :-(. All on the latest AstLinux 1.5.15-dev version. >>> >>> Michael |
|
From: Lonnie A. <li...@lo...> - 2026-09-03 13:19:57
|
Hi Michael, I had no issue creating a working pi-hole LXC in AstLinux. Only change from the docs was to add 'git' to the 'apt install'. (I updated wiki) The host was a MeLE QuieterDL CPU N100 |
|
From: Michael K. <li...@mk...> - 2026-09-03 12:13:33
|
Hi David, good point! I was able to create a working Pi-hole container on Proxmox 8 ( Linux 6.8.12-43-pve) with a Debian 12 template (which doesn't work for me on AstLinux). Michael https://mksolutions.info > Am 02.09.2026 um 19:43 schrieb David Kerr <da...@ke...>: > > Have you tried in an LXC container on a different host (non-AstLinux)? Just to narrow down if the problem is AstLinux or something else. > > Does Pi-hole 6 require a specific kernel version? One of the "features" of containers like LXC is that they build upon the kernel of the host. AstLinux is on a 5.x kernel, so if Pi-hole needs something from a newer kernel then it might not work. > > David. > > On Wed, Sep 2, 2026 at 1:03 PM Michael Keuter <li...@mk...> wrote: > Hi list, > > when I today tried to update a running Pi-hole 6 installation running in a LXC container on AstLinux, I was asked for my github username and password: > > ---- > [i] SELinux not detected > [✓] Update local cache of available packages > [✓] Building dependency package pihole-meta.deb > [✓] Installing Pi-hole dependency package > > [i] IPv4 address: 192.168.99.46/24 > [i] Unable to find IPv6 ULA/GUA address > [i] IPv6 address: > [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) > [i] Installing StevenBlack's Unified Hosts List > [i] Query Logging on. > [i] Using privacy level: 0 > [✗] Check for existing repository in /etc/.pihole > [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...Username for 'https://github.com': ^C > ---- > > I tried out different things for quite some time. > > But I ended up creating a new LXC container with Debian 13 Trixie, installed Pi-hole and imported the "Teleporter" export I created before I started the update. > The same error appeared on a newly created Debian 12 container :-(. All on the latest AstLinux 1.5.15-dev version. > > Michael |
|
From: Lonnie A. <li...@lo...> - 2026-09-02 18:40:26
|
Hi Michael, It works for me with manually trying the git clone. I tried on a test AstLinux box (astlinux-1.5-6672-5c3316) with LXC debian12... -- minipc ~ # lxc-attach debian12 root@debian12:/# cd root@debian12:~# mkdir test root@debian12:~# cd test root@debian12:~/test# apt install git Reading package lists... Done Building dependency tree... Done Reading state information... Done git is already the newest version (1:2.39.5-0+deb12u3). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@debian12:~/test# git clone https://github.com/pi-hole/pi-hole.git Cloning into 'pi-hole'... remote: Enumerating objects: 27180, done. remote: Counting objects: 100% (190/190), done. remote: Compressing objects: 100% (83/83), done. remote: Total 27180 (delta 157), reused 112 (delta 107), pack-reused 26990 (from 3) Receiving objects: 100% (27180/27180), 8.87 MiB | 21.72 MiB/s, done. Resolving deltas: 100% (17333/17333), done. -- Never did git ask for a user/pass. The "basic-install.sh" script [1] does not call for a user/pass but it calls some other git commands. -- git rev-parse --abbrev-ref HEAD and git reset --hard "$(git describe --abbrev=0 --tags)" -- Possibly it is a regional Github issue? Or possibly high traffic (AI bots) is requiring Github credentials? Lonnie [1] https://github.com/pi-hole/pi-hole/blob/master/automated%20install/basic-install.sh > On Sep 2, 2026, at 11:41 AM, Michael Keuter <li...@mk...> wrote: > > Hi list, > > when I today tried to update a running Pi-hole 6 installation running in a LXC container on AstLinux, I was asked for my github username and password: > > ---- > [i] SELinux not detected > [✓] Update local cache of available packages > [✓] Building dependency package pihole-meta.deb > [✓] Installing Pi-hole dependency package > > [i] IPv4 address: 192.168.99.46/24 > [i] Unable to find IPv6 ULA/GUA address > [i] IPv6 address: > [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) > [i] Installing StevenBlack's Unified Hosts List > [i] Query Logging on. > [i] Using privacy level: 0 > [✗] Check for existing repository in /etc/.pihole > [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...Username for 'https://github.com': ^C > ---- > > I tried out different things for quite some time. > > But I ended up creating a new LXC container with Debian 13 Trixie, installed Pi-hole and imported the "Teleporter" export I created before I started the update. > The same error appeared on a newly created Debian 12 container :-(. All on the latest AstLinux 1.5.15-dev version. > > Michael > > https://mksolutions.info |
|
From: David K. <da...@ke...> - 2026-09-02 18:13:23
|
Have you tried in an LXC container on a different host (non-AstLinux)? Just to narrow down if the problem is AstLinux or something else. Does Pi-hole 6 require a specific kernel version? One of the "features" of containers like LXC is that they build upon the kernel of the host. AstLinux is on a 5.x kernel, so if Pi-hole needs something from a newer kernel then it might not work. David. On Wed, Sep 2, 2026 at 1:03 PM Michael Keuter <li...@mk...> wrote: > Hi list, > > when I today tried to update a running Pi-hole 6 installation running in a > LXC container on AstLinux, I was asked for my github username and password: > > ---- > [i] SELinux not detected > [✓] Update local cache of available packages > [✓] Building dependency package pihole-meta.deb > [✓] Installing Pi-hole dependency package > > [i] IPv4 address: 192.168.99.46/24 > [i] Unable to find IPv6 ULA/GUA address > [i] IPv6 address: > [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) > [i] Installing StevenBlack's Unified Hosts List > [i] Query Logging on. > [i] Using privacy level: 0 > [✗] Check for existing repository in /etc/.pihole > [i] Clone https://github.com/pi-hole/pi-hole.git into > /etc/.pihole...Username for 'https://github.com': ^C > ---- > > I tried out different things for quite some time. > > But I ended up creating a new LXC container with Debian 13 Trixie, > installed Pi-hole and imported the "Teleporter" export I created before I > started the update. > The same error appeared on a newly created Debian 12 container :-(. All on > the latest AstLinux 1.5.15-dev version. > > Michael > > https://mksolutions.info > > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2026-09-02 17:03:06
|
Hi list, when I today tried to update a running Pi-hole 6 installation running in a LXC container on AstLinux, I was asked for my github username and password: ---- [i] SELinux not detected [✓] Update local cache of available packages [✓] Building dependency package pihole-meta.deb [✓] Installing Pi-hole dependency package [i] IPv4 address: 192.168.99.46/24 [i] Unable to find IPv6 ULA/GUA address [i] IPv6 address: [i] Using upstream DNS: Google (ECS, DNSSEC) (8.8.8.8, 8.8.4.4) [i] Installing StevenBlack's Unified Hosts List [i] Query Logging on. [i] Using privacy level: 0 [✗] Check for existing repository in /etc/.pihole [i] Clone https://github.com/pi-hole/pi-hole.git into /etc/.pihole...Username for 'https://github.com': ^C ---- I tried out different things for quite some time. But I ended up creating a new LXC container with Debian 13 Trixie, installed Pi-hole and imported the "Teleporter" export I created before I started the update. The same error appeared on a newly created Debian 12 container :-(. All on the latest AstLinux 1.5.15-dev version. Michael https://mksolutions.info |
|
From: Lonnie A. <li...@lo...> - 2026-06-30 16:06:34
|
Announcing AstLinux Release: 1.5.14 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.5.14 Highlights: * Asterisk Versions: 18.26.4, 20.20.1 * Linux Kernel 5.10.258-cip74, security and bug fixes * RUNNIX, version bump to runnix-0.6.26 * OpenSSL, version 1.1.1w, security fixes: CVE-2026-28387, CVE-2026-28388, CVE-2026-28389, CVE-2026-28390, CVE-2026-7383, CVE-2026-9076, CVE-2026-34180, CVE-2026-42766, CVE-2026-45447 * WireGuard, wireguard-tools, version bump to 1.0.20260223 * strongSwan, version 5.5.3, security fixes: CVE-2026-25075, CVE-2026-35330, CVE-2026-35333, CVE-2026-35332, CVE-2026-35329, CVE-2026-35331, CVE-2026-35334, CVE-2026-47895 * libcurl (curl) version bump to 8.17.0, disable smb/smbs support, security fix: CVE-2025-11563 (wcurl) * libpng, version bump to 1.6.58, security fixes: CVE-2026-33416, CVE-2026-33636, CVE-2026-34757 * libsodium, version bump to 1.0.22 * libsrtp, version bump to 2.8.0 * libxml2, version bump to 2.15.3, security fixes: CVE-2025-27113, CVE-2025-32414, CVE-2025-32415, CVE-2025-49794, CVE-2025-49795, CVE-2025-49796, CVE-2026-1757, CVE-2026-0989, CVE-2026-0990, CVE-2026-0992 * beep, version bump to 1.4.12, supports /dev/input/by-path/platform-pcspkr-event-spkr * dnsmasq, version bump to 2.93, security fixes: CVE-2026-2291, CVE-2026-4890, CVE-2026-4891, CVE-2026-4892, CVE-2026-4893, CVE-2026-5172 * expat, version bump to 2.8.2, security fixes: CVE-2026-32776, CVE-2026-32777, CVE-2026-32778, CVE-2026-41080, CVE-2026-45186, CVE-2026-50219, CVE-2026-56131, CVE-2026-56132, CVE-2026-564[03-12] * iperf3, version bump to 3.21 * jitterentropy-rngd, version bump to 1.3.1 * sqlite, version bump to 3.53.2, fixes the rare WAL-reset database corruption bug * stunnel, version bump to 5.78 * unbound, version bump to 1.25.1, security fixes: CVE-2026-33278, CVE-2026-42944, CVE-2026-42959, CVE-2026-32792, CVE-2026-40622, CVE-2026-41292, CVE-2026-42534, CVE-2026-42923, CVE-2026-42960, CVE-2026-44390, CVE-2026-44608 * unionfs (fuse), version 3.7, compile with -DDISABLE_AT to fix chmod issue * ca-certificates, update trusted root certificates 2026-05-14 * mac2vendor, oui.txt database snapshot 2026-06-06 * Time Zone Database update, tzdata2026a and php-timezonedb-2026.1 * Asterisk 18.26.4, backport applicable security fixes from Asterisk 20.20.1: CVE-2026-57188, CVE-2026-57189, CVE-2026-57198, CVE-2026-57194, CVE-2026-57195, CVE-2026-57199 * Asterisk 20.20.1, pjsip version bump to 2.17 * Asterisk 'ast18se-firmware-1.x' is the last Asterisk 18.x "Legacy" version, built --without-pjproject and --without-dahdi * Asterisk 'ast20-firmware-1.x' is the current Asterisk 20.x version, built --with-pjproject and --with-dahdi Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.14/docs/ChangeLog.txt AstLinux Project |
|
From: Gonzalo I. <gon...@ho...> - 2026-03-12 22:07:02
|
Thanks anyway for all these years of fun and entertainment and for your dedication to this project which made it possible. Whenever Astlinux reach EOL it will be still worth using it as a second life for analog phones and old boxes on isolated environments. Regards. |
|
From: Michael K. <mic...@ip...> - 2026-03-12 21:27:01
|
I will most certainly second that. Regards Michael Knill From: Dan Ryson <da...@ry...> Date: Thursday, 12 March 2026 at 10:25 pm To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] New AstLinux installations are no longer recommended ??? All, This seems like a good time for me to express thanks to Lonnie and all the AstLinux developers for their decades of hard work, professionalism, and dedication. Your efforts are greatly appreciated. Dan On Wednesday, 11-03-2026 at 17:58 David Kerr wrote: I recently (within last month) bought myself a Unifi Cloud Gateway Fiber... it replaced my Astlinux as the household gateway. I made this switch with a heavy heart, I've been a huge supporter of Astlinux, I have used it since 2008, I've contributed fixes and enhancements to it, I maintain my own fork for my personal use, it has provided me hours of enjoyment (yes, I love coding). But... as I get older and consider the future I felt the time had come to switch to a commercial solution. For years there was no commercial solution that came close to the flexibility that Astlinux offered, but that is no longer the case. Unifi gateway is very powerful and can do everything I was using Astlinux for and more. There are others, I picked Unifi because I already use their WiFi AP's and switches. There are some things that I was running on Astlinux that I now run in separate servers (proxmox containers), e.g. web server. And I have "simplified" my VoIP by directly registering my phones with voip.ms<http://voip.ms> (I am considering running Unifi Talk... but you need at least one of their proprietary phones before you can add other generics). Lonnie has been carrying the weight of keeping Astlinux up-to-date for years. And I am sure this was hard for him. But I suspect his rationale was very similar to mine. David. On Wed, Mar 11, 2026 at 4:10 PM Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote: > On Mar 11, 2026, at 2:59 PM, Steve Barlow <ste...@gm...<mailto:ste...@gm...>> wrote: > > Please have a look here.... > > https://www.astlinux-project.org/about.html > > It is saying: > > AstLinux Now: > After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended. > Comments please... > Steve Not sure what is unclear. Updating existing installations is encouraged, but consider other solutions when starting "new". Lonnie _______________________________________________ Astlinux-users mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. |
|
From: Lonnie A. <li...@lo...> - 2026-03-12 19:44:48
|
> -- > After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended. > -- I have been asked to clarify the wording. "Deprecation" [1] does not mean ending updates/security fixes, updates/security fixes will continue for some (unspecified) period of time. Why? I'm pushing 70 years old. There are other reasons as well. AstLinux's core is in the same era as Debian 11 'bullseye' which is also considered deprecated. Similarly, new Debian 11 deployments are no longer recommended. "EOL" [2] would imply no updates. That is *not* currently the case at 2026-03-01. Lonnie [1] "Deprecation refers to the discouragement of using a particular technology, feature, or practice. It often indicates that something is considered inferior compared to newer alternatives." [2] "End of Life (EOL) refers to the stage in a product's lifecycle when it is no longer sold or supported by the manufacturer, meaning it will not receive updates, patches, or new features." |
|
From: Dan R. <da...@ry...> - 2026-03-12 11:25:00
|
All, This seems like a good time for me to express thanks to Lonnie and all the AstLinux developers for their decades of hard work, professionalism, and dedication. Your efforts are greatly appreciated. Dan On Wednesday, 11-03-2026 at 17:58 David Kerr wrote: I recently (within last month) bought myself a Unifi Cloud Gateway Fiber... it replaced my Astlinux as the household gateway. I made this switch with a heavy heart, I've been a huge supporter of Astlinux, I have used it since 2008, I've contributed fixes and enhancements to it, I maintain my own fork for my personal use, it has provided me hours of enjoyment (yes, I love coding). But... as I get older and consider the future I felt the time had come to switch to a commercial solution. For years there was no commercial solution that came close to the flexibility that Astlinux offered, but that is no longer the case. Unifi gateway is very powerful and can do everything I was using Astlinux for and more. There are others, I picked Unifi because I already use their WiFi AP's and switches. There are some things that I was running on Astlinux that I now run in separate servers (proxmox containers), e.g. web server. And I have "simplified" my VoIP by directly registering my phones with voip.ms [1] (I am considering running Unifi Talk... but you need at least one of their proprietary phones before you can add other generics). Lonnie has been carrying the weight of keeping Astlinux up-to-date for years. And I am sure this was hard for him. But I suspect his rationale was very similar to mine. David. On Wed, Mar 11, 2026 at 4:10 PM Lonnie Abelbeck * wrote: > On Mar 11, 2026, at 2:59 PM, Steve Barlow wrote: > > Please have a look here.... > > https://www.astlinux-project.org/about.html > > It is saying: > > AstLinux Now: > After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended. > Comments please... > Steve Not sure what is unclear. Updating existing installations is encouraged, but consider other solutions when starting "new". Lonnie _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... Links: ------ [1] http://voip.ms |
|
From: Edson W. <eds...@vi...> - 2026-03-12 01:05:15
|
Em 11/03/2026 03:59 PM, Steve Barlow escreveu: > Please have a look here.... > > https://www.astlinux-project.org/about.html > > It is saying: > > _AstLinux Now:_ > _After over 21 years (2026-03-01), AstLinux is considered deprecated. > __New AstLinux installations are no longer recommended._ > Comments please... > Steve > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... > After over 21 years (2026-03-01), AstLinux is considered deprecated. > New AstLinux installations are no longer recommended. -- Why is that? It's super compatible with all our hardware...!?!? A persistência é o caminho do êxito. Charles Chaplin |
|
From: David K. <da...@ke...> - 2026-03-11 23:50:59
|
I recently (within last month) bought myself a Unifi Cloud Gateway Fiber... it replaced my Astlinux as the household gateway. I made this switch with a heavy heart, I've been a huge supporter of Astlinux, I have used it since 2008, I've contributed fixes and enhancements to it, I maintain my own fork for my personal use, it has provided me hours of enjoyment (yes, I love coding). But... as I get older and consider the future I felt the time had come to switch to a commercial solution. For years there was no commercial solution that came close to the flexibility that Astlinux offered, but that is no longer the case. Unifi gateway is very powerful and can do everything I was using Astlinux for and more. There are others, I picked Unifi because I already use their WiFi AP's and switches. There are some things that I was running on Astlinux that I now run in separate servers (proxmox containers), e.g. web server. And I have "simplified" my VoIP by directly registering my phones with voip.ms (I am considering running Unifi Talk... but you need at least one of their proprietary phones before you can add other generics). Lonnie has been carrying the weight of keeping Astlinux up-to-date for years. And I am sure this was hard for him. But I suspect his rationale was very similar to mine. David. On Wed, Mar 11, 2026 at 4:10 PM Lonnie Abelbeck <li...@lo...> wrote: > > > On Mar 11, 2026, at 2:59 PM, Steve Barlow <ste...@gm...> wrote: > > > > Please have a look here.... > > > > https://www.astlinux-project.org/about.html > > > > It is saying: > > > > AstLinux Now: > > After over 21 years (2026-03-01), AstLinux is considered deprecated. New > AstLinux installations are no longer recommended. > > Comments please... > > Steve > > Not sure what is unclear. > > Updating existing installations is encouraged, but consider other > solutions when starting "new". > > Lonnie > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2026-03-11 20:10:49
|
> On Mar 11, 2026, at 2:59 PM, Steve Barlow <ste...@gm...> wrote: > > Please have a look here.... > > https://www.astlinux-project.org/about.html > > It is saying: > > AstLinux Now: > After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended. > Comments please... > Steve Not sure what is unclear. Updating existing installations is encouraged, but consider other solutions when starting "new". Lonnie |
|
From: Steve B. <ste...@gm...> - 2026-03-11 19:59:18
|
Please have a look here.... https://www.astlinux-project.org/about.html It is saying: AstLinux Now: After over 21 years (2026-03-01), AstLinux is considered deprecated. New AstLinux installations are no longer recommended. Comments please... Steve |
|
From: Lonnie A. <li...@lo...> - 2026-02-28 19:09:20
|
Announcing AstLinux Release: 1.5.13 More Info: AstLinux Project https://www.astlinux-project.org/ Changes to supported firmware builds: * Previous 'ast16se' and 'ast18' firmware branches are no longer updated. * New 'ast18se' firmware branch, Asterisk 18.x built --without-pjproject and --without-dahdi * Previous 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and --with-dahdi AstLinux 1.5.13 Highlights: * Asterisk Versions: 18.26.4, 20.18.2 * Linux Kernel 5.10.249-cip69, security and bug fixes * RUNNIX, version bump to runnix-0.6.25 * OpenSSL, version 1.1.1w, security fixes: CVE-2025-68160, CVE-2025-69418, CVE-2025-69419, CVE-2025-69420, CVE-2025-69421, CVE-2026-22795, CVE-2026-22796 * libcurl (curl) version bump to 8.17.0 * libpng, version bump to 1.6.55, security fixes: CVE-2025-64505, CVE-2025-64506, CVE-2025-64720, CVE-2025-65018, CVE-2025-66293, CVE-2026-22695, CVE-2026-22801, CVE-2026-25646 * libsodium, version bump to 1.0.21, security fix * avahi, version 0.6.32, security fixes: CVE-2021-3468, CVE-2023-38469, CVE-2023-38470, CVE-2023-38471, CVE-2023-38472, CVE-2023-38473, CVE-2024-52616, CVE-2024-52615, CVE-2025-68276, CVE-2025-68468, CVE-2025-68471, CVE-2026-24401 * expat, version bump to 2.7.4, security fixes: CVE-2026-24515, CVE-2026-25210 * fping, version bump to 5.5 * iperf3, version bump to 3.20 * netsnmp, version 5.9.4, security fix: CVE-2025-68615 * pcre2, new package, version 10.47, newer though incompatible API from older pcre * php, version 7.2.34, add security fixes: CVE-2025-14177, CVE-2025-14178, GHSA-www2-q4fc-65wf * sqlite, version bump to 3.51.2 * strongSwan, version 5.5.3, security fix: CVE-2025-62291 * unbound, version bump to 1.24.2, security fix: CVE-2025-11411 * unixodbc, version bump to 2.3.14 * ca-certificates, update trusted root certificates 2025-12-02 * mac2vendor, oui.txt database snapshot 2026-01-16 * Time Zone Database update, tzdata2025c and php-timezonedb-2025.3 * Asterisk '18se' (stable edition) version 18.26.4 is the last Asterisk 18.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.13/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Project |
|
From: David K. <da...@ke...> - 2026-02-20 20:57:29
|
Thank you, this works. David. On Thu, Feb 19, 2026 at 6:31 PM Michael Knill < mic...@ip...> wrote: > Yep works well. I have used it on lots of my gateway only boxes. > > Regards > > Michael Knill > > > *From: *Michael Keuter <li...@mk...> > *Date: *Friday, 20 February 2026 at 4:47 am > *To: *ast...@li... < > ast...@li...> > *Subject: *Re: [Astlinux-users] Start without Asterisk? > > Hi David, > > simple, add this to your „user.conf“: > > ASTERISK_DAHDI_DISABLE="yes" > > Sent from a mobile device. > > Michael Keuter > > Am 19.02.2026 um 17:48 schrieb David Kerr <da...@ke...>: > > > Is there a way to have astlinux boot up without automatically starting > Asterisk? > > Thanks > David > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2026-02-19 23:31:10
|
Yep works well. I have used it on lots of my gateway only boxes. Regards Michael Knill From: Michael Keuter <li...@mk...> Date: Friday, 20 February 2026 at 4:47 am To: ast...@li... <ast...@li...> Subject: Re: [Astlinux-users] Start without Asterisk? Hi David, simple, add this to your „user.conf“: ASTERISK_DAHDI_DISABLE="yes" Sent from a mobile device. Michael Keuter Am 19.02.2026 um 17:48 schrieb David Kerr <da...@ke...>: Is there a way to have astlinux boot up without automatically starting Asterisk? Thanks David _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2026-02-19 17:46:22
|
Hi David, simple, add this to your „user.conf“: ASTERISK_DAHDI_DISABLE="yes" Sent from a mobile device. Michael Keuter > Am 19.02.2026 um 17:48 schrieb David Kerr <da...@ke...>: > > > Is there a way to have astlinux boot up without automatically starting Asterisk? > > Thanks > David > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: David K. <da...@ke...> - 2026-02-19 16:47:41
|
Is there a way to have astlinux boot up without automatically starting Asterisk? Thanks David |
|
From: Michael K. <mic...@ip...> - 2026-02-04 21:57:55
|
Oh man. Of course! That was the problem.
Thanks so much Lonnie.
Regards
Michael Knill
From: Lonnie Abelbeck <li...@lo...>
Date: Wednesday, 4 February 2026 at 10:37 pm
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Certificate authority files missing
Check your sip.conf file, for ACME certs you only need:
--
# grep -r '/sip-tls/' /etc/asterisk/
/etc/asterisk/sip.conf:tlscertfile=/mnt/kd/ssl/sip-tls/keys/server.crt
/etc/asterisk/sip.conf:tlsprivatekey=/mnt/kd/ssl/sip-tls/keys/server.key
--
Possibly you have 'tlscafile' defined, and the self-signed CA is no longer valid.
Lonnie
> On Feb 4, 2026, at 12:26 AM, Michael Knill <mic...@ip...> wrote:
>
> Sorry Lonnie
>
> Here is the error Im getting after an Asterisk reload:
>
> [Feb 4 17:13:48] ERROR[17736]: tcptls.c:524 __ssl_setup: TLS/SSL CA file(/mnt/kd/ssl/sip-tls/keys/ca.crt)/path() error
> [Feb 4 17:13:48] ERROR[17736]: tcptls.c:126 write_openssl_error_to_log: 23216157824768:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/mnt/kd/ssl/sip-tls/keys/ca.crt','r')
> 23216157824768:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
> 23216157824768:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:crypto/x509/by_file.c:199:
>
> I tried the 'openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer’ and it seemed to show the correct info.
>
> Strange!
>
> Regards
> Michael Knill
> From: Lonnie Abelbeck <li...@lo...>
> Date: Wednesday, 4 February 2026 at 6:23 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Certificate authority files missing
>
> Hi Michael,
>
> I have not seen and issues related to SIP-TLS certificates.
>
> When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"
>
> <Screenshot 2026-02-03 at 10.39.37 AM.png>
>
>
> The ACME, Let's Encrypt cert gets installed and the service is restarted.
>
> You can test what is the issuer from the localhost shell
>
> ## HTTPS
> $ openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
>
> ## SIP-TLS
> $ openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
>
> $ ls -l /mnt/kd/ssl/sip-tls/keys/
> total 8
> -rw-r--r-- 1 root root 3620 Dec 21 01:18 server.crt
> -rw------- 1 root root 1679 Dec 21 01:18 server.key
>
> There are no ca.crt or ca.key files since they are ACME, only self-signed needs those files.
>
> What Asterisk error are you getting?
>
> The SIP-TLS self-signed cert can be generated, but with warnings of overwriting the Let's Encrypt version.
>
> Lonnie
>
>
>
>
> > On Feb 2, 2026, at 8:02 PM, Michael Knill <mic...@ip...> wrote:
> >
> > Hi Team
> >
> > An email from my developer.
> >
> > Regards
> > Michael Knill
> > From: Matthew Knill <mat...@ip...>
> > Date: Tuesday, 3 February 2026 at 12:51 pm
> > To: Michael Knill <mic...@ip...>
> > Subject: Certificate authority files missing
> >
> > We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.
> > I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…
> > Regards,
> > Matthew Knill
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2026-02-04 11:36:16
|
Check your sip.conf file, for ACME certs you only need:
--
# grep -r '/sip-tls/' /etc/asterisk/
/etc/asterisk/sip.conf:tlscertfile=/mnt/kd/ssl/sip-tls/keys/server.crt
/etc/asterisk/sip.conf:tlsprivatekey=/mnt/kd/ssl/sip-tls/keys/server.key
--
Possibly you have 'tlscafile' defined, and the self-signed CA is no longer valid.
Lonnie
> On Feb 4, 2026, at 12:26 AM, Michael Knill <mic...@ip...> wrote:
>
> Sorry Lonnie
>
> Here is the error Im getting after an Asterisk reload:
>
> [Feb 4 17:13:48] ERROR[17736]: tcptls.c:524 __ssl_setup: TLS/SSL CA file(/mnt/kd/ssl/sip-tls/keys/ca.crt)/path() error
> [Feb 4 17:13:48] ERROR[17736]: tcptls.c:126 write_openssl_error_to_log: 23216157824768:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/mnt/kd/ssl/sip-tls/keys/ca.crt','r')
> 23216157824768:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
> 23216157824768:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:crypto/x509/by_file.c:199:
>
> I tried the 'openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer’ and it seemed to show the correct info.
>
> Strange!
>
> Regards
> Michael Knill
> From: Lonnie Abelbeck <li...@lo...>
> Date: Wednesday, 4 February 2026 at 6:23 am
> To: AstLinux Users Mailing List <ast...@li...>
> Subject: Re: [Astlinux-users] Certificate authority files missing
>
> Hi Michael,
>
> I have not seen and issues related to SIP-TLS certificates.
>
> When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"
>
> <Screenshot 2026-02-03 at 10.39.37 AM.png>
>
>
> The ACME, Let's Encrypt cert gets installed and the service is restarted.
>
> You can test what is the issuer from the localhost shell
>
> ## HTTPS
> $ openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
>
> ## SIP-TLS
> $ openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer
> ...
> issuer=C = US, O = Let's Encrypt, CN = R12
>
> $ ls -l /mnt/kd/ssl/sip-tls/keys/
> total 8
> -rw-r--r-- 1 root root 3620 Dec 21 01:18 server.crt
> -rw------- 1 root root 1679 Dec 21 01:18 server.key
>
> There are no ca.crt or ca.key files since they are ACME, only self-signed needs those files.
>
> What Asterisk error are you getting?
>
> The SIP-TLS self-signed cert can be generated, but with warnings of overwriting the Let's Encrypt version.
>
> Lonnie
>
>
>
>
> > On Feb 2, 2026, at 8:02 PM, Michael Knill <mic...@ip...> wrote:
> >
> > Hi Team
> >
> > An email from my developer.
> >
> > Regards
> > Michael Knill
> > From: Matthew Knill <mat...@ip...>
> > Date: Tuesday, 3 February 2026 at 12:51 pm
> > To: Michael Knill <mic...@ip...>
> > Subject: Certificate authority files missing
> >
> > We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.
> > I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…
> > Regards,
> > Matthew Knill
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <mic...@ip...> - 2026-02-04 06:41:40
|
Sorry Lonnie
Here is the error Im getting after an Asterisk reload:
[Feb 4 17:13:48] ERROR[17736]: tcptls.c:524 __ssl_setup: TLS/SSL CA file(/mnt/kd/ssl/sip-tls/keys/ca.crt)/path() error
[Feb 4 17:13:48] ERROR[17736]: tcptls.c:126 write_openssl_error_to_log: 23216157824768:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/mnt/kd/ssl/sip-tls/keys/ca.crt','r')
23216157824768:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:
23216157824768:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:crypto/x509/by_file.c:199:
I tried the 'openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer’ and it seemed to show the correct info.
Strange!
Regards
Michael Knill
From: Lonnie Abelbeck <li...@lo...>
Date: Wednesday, 4 February 2026 at 6:23 am
To: AstLinux Users Mailing List <ast...@li...>
Subject: Re: [Astlinux-users] Certificate authority files missing
Hi Michael,
I have not seen and issues related to SIP-TLS certificates.
When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service"
[cid:e6e...@au...]
The ACME, Let's Encrypt cert gets installed and the service is restarted.
You can test what is the issuer from the localhost shell
## HTTPS
$ openssl s_client -connect 127.0.0.1:443 -showcerts </dev/null | openssl x509 -noout -issuer
...
issuer=C = US, O = Let's Encrypt, CN = R12
## SIP-TLS
$ openssl s_client -connect 127.0.0.1:5061 -showcerts </dev/null | openssl x509 -noout -issuer
...
issuer=C = US, O = Let's Encrypt, CN = R12
$ ls -l /mnt/kd/ssl/sip-tls/keys/
total 8
-rw-r--r-- 1 root root 3620 Dec 21 01:18 server.crt
-rw------- 1 root root 1679 Dec 21 01:18 server.key
There are no ca.crt or ca.key files since they are ACME, only self-signed needs those files.
What Asterisk error are you getting?
The SIP-TLS self-signed cert can be generated, but with warnings of overwriting the Let's Encrypt version.
Lonnie
> On Feb 2, 2026, at 8:02 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Team
>
> An email from my developer.
>
> Regards
> Michael Knill
> From: Matthew Knill <mat...@ip...>
> Date: Tuesday, 3 February 2026 at 12:51 pm
> To: Michael Knill <mic...@ip...>
> Subject: Certificate authority files missing
>
> We have noticed that for a number of our systems, the ca.key and ca.crt file were missing in /mnt/kd/ssl/sip-tls/keys/ which ended up causing errors in Asterisk. We update our SSL certificates using Let's Encrypt, however, it seems that these files are not actually changed by Let's Encrypt at all and are exclusively self-signed.
> I have been unable to figure out why the files did not exist for this specific system. Looking through the system, I did find that the ast_tls_cert script does seem to be what generates these files, though I was unable to figure out where and how it’s actually run…
> Regards,
> Matthew Knill
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2026-02-03 19:23:12
|
Hi Michael, I have not seen and issues related to SIP-TLS certificates. When the ACME certs get renewed (via CRON) depending on what is checked "ACME Deploy Service" |
63 messages has been excluded from this view by a project administrator.
