Jump to content
Froxlor Forum


  • Content Count

  • Joined

  • Last visited

  • Days Won


llucps last won the day on October 23 2019

llucps had the most liked content!

Community Reputation

1 Neutral

About llucps

  • Rank
    Advanced Froxie
  1. 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!.
  2. 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
  3. 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.
  4. 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.
  5. 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 problem.. there were 5 more entries with duplicated ID on the domain_ssl_settings table. I had to remove the duplicates ones, making sure there was only one ID per entry and then I was able to continue with the update.. It seems that those duplicate entries weren't cleaned up by the cron job? it's seems it could be a bug but I don't really know. Happy to dig a bit more if you want, but I don't know where to start..
  6. Hi there, I finally could update to the latest Froxlor version with the testing repository. Thanks!
  7. 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!
  8. 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
  9. 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!
  10. Congratulations! and thank you for all your efforts and work! I'll update when Debian packages become available. Cheers.
  11. Hi there, Are there any plans to implement a proper DKIM, I guess using openkdim instead of the deprecated dkim-filter? I remember I had to scavenged a bit to find the dkim-filter and I think I even had to compile it for Debian 9. Thanks!
  12. DONE!!!!! sorry you're going to kill me... I swear I thought did that step but obviously I didn't. Alias "/.well-known/acme-challenge" "/var/www/froxlor/.well-known/acme-challenge" <Directory "/var/www/froxlor/.well-known/acme-challenge"> Require all granted </Directory> it makes total sense if that directive wasn't present. Thanks for your help and understanding.!
  • Create New...