Everything posted by llucps
-
Release file missing from Bullseye debian.froxlor.org?
Hi, Since yesterday, I've been suddenly receiving these messages from cron /usr/sbin/apticron; then /usr/sbin/apticron --cron; E: The repository 'http://debian.froxlor.org bullseye Release' no longer has a Release file. and with apt-get update it complains about not finding the Release file: Err:10 https://deb.froxlor.org/debian bullseye Release 404 Not Found [IP: 185.123.52.110 443] Reading package lists... Done E: The repository 'http://debian.froxlor.org bullseye Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I see the Release file for Bullseye on http://debian.froxlor.log.. Is anyone else having this problem? Or is it just me? Strange.. Thanks Lluc
-
Froxlor 0.10.29.1 (DB: 202109040) New domain no letsencrypt => error!
This also happened to me. What I did was first create the domain without SSL, and once done, this will add a A record for the new domain to the DNS and then I was able to create the certificate SSL with Let's encrypt. So basically I have to do it in two steps, this behavior I think is different when Froxlor was using certbot, I remember creating my previous domains and SSL certificates in one step. It's not a big deal but I just thought it was worth to mention. Is it also your case @d00p? Thanks,
-
Release 0.10.29 - Security improvements, czech language support and mysql tls support
Thanks @d00p 👍
-
Post Bullseye update (Bind9 installed and running but not in /etc/init.d/bind9)
Yes that's what I thought I need to get used to systemd services syntax.. old habits Thanks,
-
Post Bullseye update (Bind9 installed and running but not in /etc/init.d/bind9)
Hi @d00p, I just updated my server to Bullseye and although I had to reinstall mariadb, and also froxlor and some php7.4 packages it seems all is ok except with one thing bind9. After the upgrade the /etc/init.d/bind9 was missing.. the bind9 service is running fine because I can use service bind9 status and I see it running The problem is in DNS server reload command settings in Froxlor I had /etc/init.d/bind9 reload and obviously since it's not there it fails to reload the service. What I did was change the command to service bind9 reload and it seems to be working fine. My question is whether there should be really a bind9 in /etc/init.d When I installed bind9 again I get this message: Setting up bind9 (1:9.16.15-1) ... named-resolvconf.service is a disabled or a static unit not running, not starting it. Processing triggers for man-db (2.9.4-2) ... /etc/init.d/resolvconf status is working fine ● resolvconf.service - Nameserver information manager Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2021-08-22 08:03:27 CEST; 27min ago Docs: man:resolvconf(8) Main PID: 1774 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4559) Memory: 0B CPU: 0 CGroup: /system.slice/resolvconf.service Do you have any idea whether there should be bind9 in /etc/init.d/? or just using service bind9 reload/restart/start is fine? Thanks!
-
Release 0.10.28 - Custom database names, improved dns validation for let's encrypt domains & Buypass as Let's Encrypt alternative
Kudos to you @d00p! 👍 Thanks, Lluc
-
Release 0.10.27 - Debian Bullseye support, added ZeroSSL alternative to Let's Encrypt and custom logo upload
Congratulations! Just out of curiosity, I'm gladly surprise that Bullseye support has been added already. Does that mean that changes between Buster and Bullseye are not that big? Thank you @d00p!
-
Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
Hi there, I finally could update to the latest Froxlor version with the testing repository. Thanks!
- Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
-
Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
If I use this testing repository, can then I change to the "production" one for future updates? If there can be conflicts after using both.. I'll wait for @Dessa to fix repository. Thanks!
- Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
-
Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
I don't think Stretch packages have been updated yet.. last update was December 5th 2018.. Am I doing something wrong? Architectures: amd64 arm64 armel armhf i386 Codename: stretch Components: main Date: Wed, 05 Dec 2018 07:51:29 +0000 Label: Froxlor Repository Origin: froxlor.org Suite: stable
-
Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
Thanks d00p, I tried to update a Debian Stretch server to the latest 0.10.2 but it seems there are only packages for Buster? Is it possible to update Stretch to the 0.10.2 with Debian packages? Thanks!
-
Release 0.10.26 - API based froxlor with 2FA, MySQL8 compatibility, new Let's Encrypt implementation and much more...
Congratulations! and thank you for all your efforts and work! I'll update when Debian packages become available. Cheers.
-
Release 0.9.39.5 - Stretch support, multi-slot FPM, settings import/export and more *UPDATE*
Hi, I see that stretch packages are available already . I'll update my server to stretch this weekend. Fingers crossed !! Thanks
- Release 0.9.39.5 - Stretch support, multi-slot FPM, settings import/export and more *UPDATE*
-
Release 0.9.39.5 - Stretch support, multi-slot FPM, settings import/export and more *UPDATE*
Hi d00p, I'll wait for the 0.9.x packages. But if I installed froxlor using Debian packages, can I update using the auto-update? or would it screw up my froxlor system? I'm just curious. Thanks.