Jump to content
Froxlor Forum

llucps

Members
  • Content Count

    65
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by llucps

  1. I understand.. I would change to openkdim, but since it's not supported and I'm a bit afraid to make the change in case I screw up my email setup. I'll leave the change I did to remove .priv from lib/Froxlor/Cron/Dns/DnsBase.php for the moment. I would really appreciate if you can add the option the chose both options on the dkim Froxlor settings so I can continue it to use it with dkim-keys for the moment. eventually I'll have to make the change.. I know. Thanks @d00p
  2. umm. sorry I'm not sure I quite follow you.. Do you mean that commit should be revert it? and leave the key name as it was: $privkey_filename = \Froxlor\FileDir::makeCorrectFile(Settings::Get('dkim.dkim_prefix') . '/dkim' . $domain['dkim_id']);
  3. Both .priv and .public files are inside /etc/postfix/dkim directory.. but I don't recall at all the the public keys were referenced on the dkim-config.keys file, I'm pretty sure only the private keys are referenced. So.... I just removed the .priv extension that was added to the commit https://github.com/Froxlor/Froxlor/commit/15a13a7783d85f77efe1619ed85bd46e9ad3935b so the dkim-config.keys looks for: *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim1 *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim2 *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim3 *@xxxxxx.com:xxxxxxx.com:/etc
  4. Yes I posted the dkim-keys.conf on my previous post, which every line is for every domain I have on my system *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim1.priv *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim2.priv *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim3.priv *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim4.priv *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim5.priv *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim6.priv *@xxxxxx.com:xxxxxxx.com:/etc/postfix/dkim/dkim7.priv What I could try is to undo the .priv change on the commit you did on october the revert it how it was an
  5. Since according to DomainKeys settings in Froxlor, only dkim-filter is supported, I'm using dkim-filter with this following config: # Log to syslog Syslog yes # Required to use local socket with MTAs that access the socket as a non- # privileged user (e.g. Postfix) UMask 002 # Sign for example.com with key in /etc/mail/dkim.key using # selector '2007' (e.g. 2007._domainkey.example.com) Domain /etc/postfix/dkim/domains #KeyFile /etc/mail/dkim.key #Selector 2007 # Common settings. See dkim-filter.conf(5) for m
  6. Hi @d00p, Yes it did.. I just posted the new dkim.priv files as you can see... Strange that this change has broken my setup.. because it all looks good apparently, but obvisouly isn't working for me Thanks.
  7. Hi, I just found out the that starting on the 8th of November which I believe is when I updated to the latest 0.10.22 froxlor the DKIM fails to send the public key. Looking at the email message source: dkim=temperror (no key for signature) header.i=@xxxxxxxxx.com header.s=dkim1.priv header.b=kWkNNAzJ; I just checked the froxlor database and the public and private keys are there. I also check the /etc/postfix/dkim/ and all the keys are also there, including dkim-keys.conf which lists all domains and its keys In fact I haven't changed or modified anything related to this, not a
  8. It's ok! I'll wait it doesn't bother me at all. What's important is now we know why it was failing. Thanks.
  9. Yes! that was it It works now. For the moment I just modified the file manually until a new froxlor version comes out Thanks!
  10. Yes.. I'll wait and check again at the end of the day or tomorrow and see if it's a cache problem. I hope it is and it seems so, otherwise I don't know where else to look at. As you see the entry is valid and all looks good fingers crossed! Thanks and I let you know!
  11. I just sent you a private message with the domain Thanks!
  12. Hi, I've upgraded to 0.10.20 and I noticed the removal of underscore in the DKIM selector. I know it's old but I've been using dkim-filter perfectly for 6 years, I don't know if it's coincidence but after the upgrade Google and Outook give a: Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@xxxxxxxx.com header.s=dkim_1 header.b=gJgMgR3B; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=xxxxxxx.com; s=dkim_1; t=1596958620; bh=OcFrXmsxPwiq9nLiqWOthXQmkOsI8oRkgTPZrapwNcQ=; h=To:From:Subject:Message-ID:Date:MIME-Version:Content-Type:
  13. Hi, I forgot to attached the log I when the cron job failed: [Sat 18 Jul 2020 12:04:02 AM CEST] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 6 [Sat 18 Jul 2020 12:04:02 AM CEST] Can not init api. [Sat 18 Jul 2020 12:04:03 AM CEST] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 6 [Sat 18 Jul 2020 12:04:03 AM CEST] Can not init api. [Sat 18 Jul 2020 12:04:03 AM CEST] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 6 [Sat 18 Jul 2020 12:04:45 AM CEST] Can not get domain new authz.
  14. Hi, Yesterday I got an error when renewing two domains (they are subdomains, the parent domain is not managed or hosted by me) [information] apache::createVirtualHosts: creating vhost container for domain 17, customer xxxxx [error] Given SSL private key for xxxxx.xxxxx.com does not seem to match the certificate. Cannot create ssl-directives [information] apache::createVirtualHosts: creating vhost container for domain 18, customer xxxxx [error] Given SSL private key for xxxxx.xxxxx.com does not seem to match the certificate. Cannot create ssl-directives It's just worth to mention t
  15. I can't remember off the top of my head the screen immediately you login to finish the update.. I just remember clicking on the green button.. Anyway, yes it's weird that the update didn't remove those duplicates.. Just worth to mention that on another server the update went through without any problem. Thanks for everything!.
  16. I think I didn't explain myself.. That's what I did, as all the previous updates. apt-update & upgrade Froxlor Web Login with my admin user Clic continue to finish the process, this is where it failed because of the duplicated entries. I just follow the "official" steps
  17. By the way after removing the duplicated entries and continue the update, so at this point everything was working well, I manually ran /usr/bin/php /var/www/froxlor/scripts/froxlor_master_cronjob.php --force --debug Just to check everything else work too.. and it did.
  18. Steps I did: 1. apt-get update & upgrade 2. go to froxlor web 3 . Check database integrity Nothing else, after the check Froxlor detected duplicated entries. I had to manually remove the duplicated from the database and then I was able to continue and update sucessfully.
  19. Hi, I just upgraded to Froxlor 0.10.17 using the offical deb repository and after checking the database integrity which is the last step I get this error: Adding unique key on domainid field in domain ssl table A database error occurred SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '3' for key 'domainid' Can you point me out what table to look extacly? panel_domains? I see in domains_ssl_settings table: there are two entries for domainid 3 with id 24 and 25.. I'm not sure where to look. Thanks, UPDATE: I've managed to fix the probl
  20. Hi there, I finally could update to the latest Froxlor version with the testing repository. Thanks!
  21. 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!
  22. 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
×
×
  • Create New...