Jump to content

Mah1973

Priority Members
  • Posts

    32
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Mah1973

  1. 8 hours ago, Plamen K. said:

    I can't agree with you. Support is about helped you, no?!
    If you check, you can see - the prices are similar for all products +/- 10$ (without Plesk and cPanel, but they are on different level). I don't determine how much is the cost, the CWP team did it ... but if quality is bad customers goint be lost. Only to cleary - if I can solve all the problems, I don't pay for maintenance i pay only for Pro version ... have a big difference in the price 😉

    BTW support teem can't fix the problem and forwarded to developer teme - how can sove alone this problem in this case?

    Yes , if you are talking about the paid support then you are totally right. I thought you are referring to the regular pro version.

  2. 23 hours ago, torettos said:

    Hello Sandeep and all other users,

    many year I wasn't looking for web panel but with end of life on Cent OS 7 and very, vary bad payed support on CWP i start to research which web panel is better in 2024. and all yours experience and opinion will be helpful for me 🙂

    Watching the features, support, price and ecc. i don't have many criteries i want stable web panel with good support and on normal price. The beter option for me is if it can optimize the sites (for fast loading for reason of SEO) and have no problems with SSL or E-mail.

    To the question: which is the best option for 2024 and why?
    Thank you in advance!

    Stick with CWP—it's the best among them. Is the support bad? Yes, that's true. But really, what do you expect at that price point? if you have troubles learn how to fix them. I'm running all my servers with CWP and I still recommend them to every one.

  3. It worked !! , thanks. The guys behind the cwp documentation site should be fired !!. I wasted too much time on this silly thing. Is it really that hard to edit this sentence in edit package page ? "- Use -1 for Unlimited resources " just a simple edit will save us lots of time and efforts. Thanks for your help once again.

  4. I'm trying to write a hook to fix this using the info on the documentation site here

    https://wiki.centos-webpanel.com/action-hooks

     

    But I'm not getting anywhere! .. I created the php file as instructed in

    /usr/local/cwpsrv/htdocs/resources/admin/hooks/account/account_unsuspend.php

    and I added this to it :

     

    <?php
    
    function account_unsuspend($array) {
        // Extracting data from the array
        $username = $array['username'];
        $status = $array['status'];
    
        // Log the unsuspension event
        $logfile = '/var/log/cwp_account_unsuspend.log';
        $timestamp = date('Y-m-d H:i:s');
        file_put_contents($logfile, "$timestamp - User $username was unsuspended. Status: $status\n", FILE_APPEND);
    
        // Set unlimited quotas for the unsuspended user
        $command = "setquota -u $username 0 0 0 0 /";
        exec($command);
    
        // Send email notification
        $subject = "User Unsuspension";
        $message = "User $username has been unsuspended.";
        mail("myemail@gmail.com", $subject, $message);
    }
    
    ?>

     

    but when I unsuspend the user nothing happens and the log is empty. The documentation site is not clear enough on this or maybe outdated?

  5. this module only works with /112 so you will need to modify the file

     nano /etc/sysconfig/network-scripts/ifcfg-eth0

    to subnet your network to a /112 prefix

    You will need to add something like :
    IPV6ADDR=2a01:4f8:c17:1b52::1/112  // only an example

    then do

    sudo systemctl restart NetworkManager

    then

    ip addr show eth0

    to see the changes

    this is translated copy in English

    https://uploadnow.io/f/YZBDtNM

    I didn't test the module on live servers yet.

     

  6. On 4/17/2024 at 10:03 PM, Sandeep B. said:

    you can dm me with root logins 

    Thanks I can send you the root for one of our servers to test this. But I think I found the issue. When the package is unlimited resources the unsuspend function doesn't work properly. I have to edit the quota manually

    [root@vps ~]# repquota -a -s
    *** Report for user quotas on device /dev/sda1
    Block grace time: 7days; Inode grace time: 7days
                            Space limits                File limits
    User            used    soft    hard  grace    used  soft  hard  grace
    ----------------------------------------------------------------------
    unlimi    ++     40K      1K      1K  6days      11     1     1  6days

    and when the package has limited resources the suspend function works just fine.

    The problem is we do have 2 packages types for our clients ( limited and unlimited ). How to keep both types and fix this issue ???

  7. 17 hours ago, Sandeep B. said:

    you're not using cwp compatible quota you need to follow this tutorial https://forum.centos-webpanel.com/centos-configuration/how-to-setup-user-quotas/

    after adding to fstab :

    /dev/sda1 / ext4 srjquota=quota.user,jqfmt=vfsv0 0 0

     usrjquota=quota.user,jqfmt=vfsv0

    reboot the system and then run again 

    mount -o remount /
    quotacheck -avugm
    quotaon -avug

     

    this /dev/sda1 / ext4 srjquota=quota.user,jqfmt=vfsv0 0 0

    made the system unbootable and I had to rescue to revert the fstab changes and get the server back online.

    I also tried this

    /dev/sda1 / ext4 rw,usrjquota=quota.user,jqfmt=vfsv0        1       1

    the system boot correctly but the unsuspend problem didn't go away!

    now , I'm running the old options as is. I guess it's a bug in CWP.

  8. 1 hour ago, Sandeep B. said:

    can you post the output of this commands : 

     

    mount -o remount /
    quotacheck -avugm
    quotaon -avug

     

    [root@server16 /]# mount -o remount /
    [root@server16 /]# quotacheck -avugm
    quotacheck: Your kernel probably supports journaled quota but you are not using it. Consider switching to journaled quota to avoid running quotacheck after an unclean shutdown.
    quotacheck: Quota for users is enabled on mountpoint / so quotacheck might damage the file.
    Please turn quotas off or use -f to force checking.
    [root@server16 /]# quotaon -avug
    quotaon: using //aquota.group on /dev/sda1 [/]: Device or resource busy
    quotaon: using //aquota.user on /dev/sda1 [/]: Device or resource busy
    [root@server16 /]# 

     

    Thanks for your help.

  9. 16 hours ago, Sandeep B. said:

    it seems to be quota issue with kernel predefined quota recommended to use ext4 or xfs file system

    I'm already on ext4 file system.

     

    [root@server16 /]# df -Th
    Filesystem     Type      Size  Used Avail Use% Mounted on
    devtmpfs       devtmpfs  1.8G     0  1.8G   0% /dev
    tmpfs          tmpfs     1.8G     0  1.8G   0% /dev/shm
    tmpfs          tmpfs     1.8G   27M  1.8G   2% /run
    tmpfs          tmpfs     1.8G     0  1.8G   0% /sys/fs/cgroup
    /dev/sda1      ext4       75G   17G   56G  23% /
    /dev/sda14     vfat       64M  5.8M   59M  10% /boot/efi
    tmpfs          tmpfs     356M     0  356M   0% /run/user/0
    [root@server16 /]# 

     

    This problem is on all my Almalinux servers. Nothing I can do to fix it ?

  10. Hi,

    I have a problem with the CWP unsuspend function. When I unsuspend a user the quota doesn't get updated for him and I always have to edit it manually.

    edquota username
    and change all 1's to 0's to make it unlimited.

    I want it to be done automatically when the suspend / unsuspend functions are used.

     

    [root@server16 ~]# quotaon -pa
    group quota on / (/dev/sda1) is on
    user quota on / (/dev/sda1) is on
    project quota on / (/dev/sda1) is off
    [root@server16 ~]# cat /usr/local/cwp/.conf/quota_part.conf
    /
    [root@server16 ~]# cat /etc/fstab
    
    #
    # /etc/fstab
    # Created by anaconda on Mon Jun 12 13:24:27 2023
    #
    # Accessible filesystems, by reference, are maintained under '/dev/disk/'.
    # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
    #
    # After editing this file, run 'systemctl daemon-reload' to update systemd
    # units generated from this file.
    #
    /dev/sda1 / ext4 rw,relatime,quota,usrquota,grpquota 0 0
    UUID=C866-FB19          /boot/efi               vfat    defaults,uid=0,gid=0,umask=077,shortname=winnt 0 2
    /swapfile          swap            swap    defaults        0 0
    [root@server16 ~]# /scripts/cwp_api account update_diskquota_all
    setquota: invalid option -- '1'
    [root@server16 scripts]# ./cwp_version 
    0.9.8.1177

     

    Can you please tell me how to fix this ?

     

    more info

    • Distro Name: AlmaLinux release 8.9 (Midnight Oncilla)
    • Kernel Version: 4.18.0-513.24.1.el8_9.x86_64
    • Platform: x86_64 kvm

     

  11. 1 hour ago, Mah1973 said:

    Sorry for the off topic question , do you recommend activating "SNuffleupaugs" for shared Almalinux servers with lots of clients ? do you use basic or intermediate rules ? I would like to know about your experience , benefits and issues if any.

    This module with php7.4 is a big no on shared servers.

    grep "snuffleupagus" /opt/alt/php-fpm*/usr/var/log/php-fpm.log | grep "PHP Fatal error"

    I got lots of client websites down with fatal errors.

    grep "snuffleupagus" /opt/alt/php-fpm*/usr/var/log/php-fpm.log | grep "PHP Fatal error" | grep -v "php-fpm74"

    No issues for new php versions till now. ( Almalinux , basic rules )

  12. Sorry for the off topic question , do you recommend activating "SNuffleupaugs" for shared Almalinux servers with lots of clients ? do you use basic or intermediate rules ? I would like to know about your experience , benefits and issues if any.

  13. If you are hosting clients, then stick to PHP-FPM and Apache. PHP-FPM offers slightly less performance than nginx but also less headache. However, if you are hosting only your own sites, you can give it a try. In my trials, the extra performance boost is very minimal, if any.

  14. On 2/19/2024 at 8:30 PM, leisegang said:

     

    In Linux-based systems, you can use the following command on the CLI to mount the file system:

     

    mount.cifs -o user=<username>,pass=<password> //<username>.your-storagebox.de/backup /PATH/FOLDER

    By adding the following line to /etc/fstab, your system will automatically mount the file system at boot. (It is a single line!):

    //<username>.your-storagebox.de/backup /mnt/backup-server cifs iocharset=utf8,rw,credentials=/etc/backup-credentials.txt,uid=<system account>,gid=<system group>,file_mode=0660,dir_mode=0770 0 0

    The file /etc/backup-credentials.txt (mode 0600) should contain two lines as follows:

    username=<username>
    password=<password>


    In Debian-based distributions, the command is provided via the package cifs-utils.

    apt-get install cifs-utils

    On Debian Wheezy based systems, edit the parameters as follows if you are having problems:

    rsize=65536,wsize=130048

    You should also add the following lines to /etc/rc.local:

    modprobe cifs
    echo 0 > /proc/fs/cifs/OplockEnabled

     

    Tried this a year ago and after spending days testing I failed to get it to work. So I gave up and got a cheap storage vps with rsync and full ssh access. Works like a charm.

  15. Quick tip :

    One line command to clear wp-rocket cache on all sites on server :

    test it first (dry run) :

    find /home -type d -name "wp-rocket" | while read -r dir; do cache_dir=$(dirname "$dir")/cache/wp-rocket; [ -d "$cache_dir" ] || cache_dir=$(dirname "$(dirname "$dir")")/cache/wp-rocket; [ -d "$cache_dir" ] && echo "Clearing cache in $cache_dir" || echo "Cache directory not found in $dir"; done


     

    run it live (clear the cache files )  :
     

    find /home -type d -name "wp-rocket" | while read -r dir; do cache_dir=$(dirname "$dir")/cache/wp-rocket; [ -d "$cache_dir" ] || cache_dir=$(dirname "$(dirname "$dir")")/cache/wp-rocket; [ -d "$cache_dir" ] && echo "Clearing cache in $cache_dir" && rm -rf "$cache_dir"/* || echo "Cache directory not found in $dir"; done

     

    • Like 1
×
×
  • Create New...