managed server

https://wpengine.com/support/troubleshooting-high-time-first-byte-ttfb/ TROUBLESHOOT HIGH TTFB Copy to  staging or development  site, or  take a backup  before proceeding. Test the TTFB on a few different pages of your website If it’s just a few pages that are slow, it’s likely an element that is being used in common across the pages. Test a static HTML file instead of a dynamic WordPress page If TTFB is high on a static page, then there may be a load issue on the server. Contact Support for assistance. If TTFB is low on a static page, then some content on your site is likely causing the issue. Activate a different theme If TTFB is lower, your theme is likely causing the issue. Check for an update or reach out to the theme developer. If TTFB is still high, try disabling plugins. Deactivate all plugins If TTFB is still high, it’s potentially due to a database issue. Check your  autoload data  and  queries . If TTFB is lower, try enabling the plugins one by one t

You can update file permission 777 for the “plugin” and “wp-content” directory. chmod -R 777  wp-content

follow all the steps of Zimbra installations use the same package of the primary one. like an entry in etc/hosts disable postfix and selinux after completing all move /opt/zimbra   /opt/zimbra.old scripts to copy data from primary set this scripts in primary harddisk after rebooting mount the secondary harddisk df  -h /dev/sdb4 /mnt [root@zimbra ~]# crontab -l 33 15 22 02 * /bin/sh /home/sas/with-delete.sh &> /home/sas/withdelete.log 2>&1 [root@zimbra script]# cat with-delete.sh #!/bin/sh Date1=`date +%d-%m-%Y` T1=`date` rsync -avz --delete /opt/zimbra /secondary/opt/zimbra > /home/sas/withdelete.log 2>&1 T2=`date` echo "START :  " $T1 >> /home/sas/withdelete.log echo "END   :  " $T2 >> /home/sas/withdelete.log ---------------------------------------------------- above method giving errors "Starting ldap...[sudo] password for zimbra:" after fixing this MySQL is crashing ** buffer overf

if it is because of ElementPress or diff elementor plugin then disable single and Archive  page make it inactive Just go to page or post and click on quick edit and then choose elementor full width then click on update and after this edit the page

To enable the  gzip compression  for your site, follow the steps: Go to yourdomain.com/cpanel and log in Look for  Optimize Website  entry ( SOFTWARE  cPanel section) Here you have 3 options: – Disabled  – which will disable the compression – Compress All Content  – with this option all content will be compressed – Compress the specified MIME types  – here, you will be able to input only certain MIME file types. So, choose the second option and click the  Update Settings  button. A confirmation message will appear:  Website optimization preferences updated. Content compression is now enabled. Content compression is now enabled for all content. Your site is using now the gzip compression. Enable Gzip Compression - Configuration for Nginx and ApacheHow to enable Gzip compression? # Depending on which web server you are using, the method to enable Gzip will vary. The following describes both an Apache Gzip configuration as well as an Nginx Gzip configuration. Apache Gzip configura

If the Greylisting filter is enabled, the message you are seeing is quite normal, and will be applied to all incoming mail that your server receives. Please see  Greylisting - Version 64 Documentation - cPanel Documentation  for full details. WHM Server wide settings Home >> Email >> Greylisting Individual cPanel Account settings (per domain) cPanel >> EMAIL >> Configure Greylisting

1. mv /opt/zimbra /opt/zimbra.old 2.set cronjob for data migration 34 22 21 * * /bin/sh /home/sas/opt.sh >>/home/sas/optzimbra.log 3.create scripts in /home/sas/ create optzimbra.sh and pass chmod optzimbra.sh 754 [root@mail sas]# cat optzimbra.sh #!/bin/sh T1=`date` rsync -avz --password-file=/home/sas/pass -u  root@115.112.176.21::opt/zimbra  /opt/ > /home/sas/opt.log  2>&1 T2=`date` echo "START : " $T1  >> /home/sas/opt.log echo "END : " $T2  >> /home/sas/opt.log set same password from live server from /etc/rsyncd.secrets chmod 400 pass enter the opt location in rsync.conf of live server from where you want to fetch data [opt]         path = /opt         comment = An Example         auth users = root         secrets file = /etc/rsyncd.secrets         read only = no         uid = root         gid = root         use chroot = yes

check folder   path ( directory permission which is allowed to access) from where you are taking data for rsync daemon

https://unix.stackexchange.com/questions/252936/grub2-boot-to-a-second-another-hard-disk /boot/grub2 cat device.map (hd0)      /dev/sda (hd1)      /dev/sda

https://wiki.zimbra.com/index.php?title=Mysql_Crash_Recovery Generate SQL dumps of all databases /opt/zimbra/conf/my.cnf  socket         = /opt/zimbra/data/tmp/mysql/mysql.sock su - zimbra zmlocalconfig -s | grep mysql | grep password The output will look something like this. mysql_logger_root_password = AWHZ60JYaBw8_hVkA9NDVGh0irmp7xVz mysql_root_password = lkAd7vkYI.Q_VeWt8uyL9kj0 zimbra_logger_mysql_password = 2iiyAVj3GeH0akkCe6M1o_HvY zimbra_mysql_password = uMv4EsNqPZdK5htERx97VY5m mysql --batch --skip-column-names -e "show databases" | grep -e mbox -e zimbra > /tmp/mysql.db.list Note: If you are using ZCS v8.8.x with Chat/Talk enabled then you should take Chat database dump as well mysql --batch --skip-column-names -e "show databases" | grep -e mbox -e zimbra -e chat > /tmp/mysql.db.list mkdir /tmp/mysql.sql for db in `cat /tmp/mysql.db.list`; do  /opt/zimbra/common/bin/mysqldump $db -S /opt/zimbra/data/tmp/mysql/mysql.s

Installing OpenSSH From  https://github.com/PowerShell/Win32-OpenSSH/releases , download the latest .zip of OpenSSH. The typical choice for Windows 2016 is to download the [OpenSSH-Win64.zip] option. Extract the OpenSSH-Win64.zip file and save it on your console. The easiest way to find it locally would be to save it in your [C:\Program Files\]. C:\Program Files\OpenSSH-Win64 move it and then

First, create child nameserver ATTENTION   (Anchor:  errors ) If the Name Server(s) you are submitting has/have  not  been registered with the Registry, you will encounter the below error message: Name server <nameserver> is not a valid name server Please contact your Web Hosting Company and ask them to provide Name Servers that are valid and registered with the Registry. You will encounter the below error message in case you try to set only 1 Name Server for a domain name extension that requires a minimum of 2 Name Servers: There should be atleast 2 Nameserver(s)

https://forums.zimbra.org/viewtopic.php?t=60713

Mar 18 23:39:32 zimbra saslauthd[12057]: authentication against url 'https://zimbra.kshdistriparks.com:7073/service/admin/soap/' caused error 'curl_easy_perform: error(28): Connection timed out after 15001 milliseconds' Mar 18 23:39:32 zimbra postfix/submission/smtpd[19330]: warning: unknown[111.125.221.38]: SASL LOGIN authentication failed: authentication failure iptables -A INPUT -p tcp --dport 7073 -j ACCEPT iptables -A OUTPUT -p tcp --sport 7073 -j ACCEPT iptables -A INPUT -p tcp --sport 7073 -j ACCEPT iptables -A OUTPUT -p tcp --dport 7073 -j ACCEPT

PHP Fatal error:  Allowed memory size of 157286400 bytes exhausted diractadmin Loaded Configuration File /usr/local/lib/php.ini memory_limit 199M

amavisd-new seems to be down. Try to restart

whmcs font sixe for configure got resolved from cp: overwrite ‘/home/cloudhostweb/public_html/client/templates/six/includes/head.tpl’? y

try sudo chmod 400 file name or change file location to different place

By checking the PTR record of your IP we have recognized that this has not been changed yet. Therefore, we are kindly asking to have a look at the following tutorials which will guide you with setting up your DNS properly in order to enhance the mail delivery from your VPS.  Please keep in mind that the hostname should be a full qualified domain name matching the main domain in use and that the PTR record has to match the hostname. Full qualified means that it has to include a subdomain. The authentication for addon domains will be handled by the SPF and DKIM records mentioned in the tutorials below: you can set from where you have purchased server

Log In as Customer > account > my profile

wait a while after adding a user to spam experts it takes some time to reflect

Add IP by going to outgoing manage users and save

add domain Step 3 of 3: Summary Domain cloudhostweb.com Destination route hostname server.cloudhostweb.com: 587  Connection and recipient validation appears to work. In exim.conf begin routers Section: ROUTERSTART in whm spamexperts_smarthost_router:   driver = manualroute   domains = ! +local_domains   senders = ^.*@cloudhostweb.com   ignore_target_hosts = 127.0.0.0/8   #condition = "${perl{check_limits}}"   # Exclude null sender messages from relaying via the smarthost   #condition = ${if or {{!eq{$sender_address}{}} {!eq{$sender_host_address}{}}}}   transport = spamexperts_smarthost_transport   route_list = $domain 4274.smtp.antispamcloud.com::587 no_more telnet 4274.smtp.antispamcloud.com 587 begin transports spamexperts_smarthost_transport:   driver = smtp # # In-case your server continues to send outbound over port 25 please add the below line   port = 587   hosts_require_tls = 4274.smtp.antispamcloud.com #  .include_if_exi

cd /home/cloudhostweb/public_html/client/templates/six/css vi wordpresscss.css  #Custom_mega_menu .custom_menu_box h3{margin:0;color:#222;font-size:16px;line-height:18px;font-weight:500}                                                                                           .new_pagesmega_menu{font-size:10px;line-height:10px;color:#fff;padding:2px 5px;background-color:#009688;margin-left:10px;border-radius:4px}                                                                                           .new_pagesmega_tpmenu{font-size:12px;line-height:12px;color:#fff;padding:2px 5px;background-color:#f7941d;margin-left:10px;border-radius:4px;right:-15px;top:4px}                                                                                           .new_pagesmega_menu.hot{background-color:#ed1c24}                                                                                           .new_pagesmega_menu.coming-soon{background-color:#1cc1ff!important}                      

Installing LDAP configuration database...done. Setting defaults.../opt/zimbra/bin/zmjava: line 59: /opt/zimbra/common/lib/jvm/java/bin/java: No such file or directory /opt/zimbra/bin/zmjava: line 59: /opt/zimbra/common/lib/jvm/java/bin/java: No such file or directory /opt/zimbra/bin/zmjava: line 59: /opt/zimbra/common/lib/jvm/java/bin/java: No such file or directory /opt/zimbra/bin/zmjava: line 59: /opt/zimbra/common/lib/jvm/java/bin/java: No such file or directory /opt/zimbra/bin/zmjava: line 59: /opt/zimbra/common/lib/jvm/java/bin/java: No such file or directory Address unconfigured (**) items  (? - help) yum remove zimbra*

If your server or website has already been compromised and your server is sending out malicious HTTP requests like scans, brute force attempts, etc. You can detect and log the outgoing packets and find out which user caused the problem by adding the following iptables rule. This rule will log any packet that leaves your server and targets port 80. It also logs the user id so you can identify which user initiated the request. To avoid flooding, we limit the number of logs to 5 per minute. You can increase or decrease this number if you need to fine tune. iptables -I OUTPUT -p tcp -m tcp --dport 80 -j LOG --log-uid -m limit --limit = 5 /minute --log-prefix BITNINJA After running this command, you have to monitor the kernel log for any captured packets. You can see the kernel logs with this command: dmesg -T Note On some older versions of dmesg the -T option is not supported. In this case you can simply run dmesg. An example of packets made by root. (UID=0 GID=0)

The iptables rules are evaluated in order, which means that if you block everything in the first rule, there is no point to allow something later, those rules will never be reached. I'm quite sure you don't want to match the source address, you want the destination. iptables -A OUTPUT -p tcp -d 127.0.1.1 --match multiport --dports 25,587,465 -j ACCEPT iptables -A OUTPUT -p tcp -d **.**.**.*** --match multiport --dports 25,587,465 -j ACCEPT iptables -A OUTPUT -p tcp -d **.**.**.*** --match multiport --dports 25,587,465 -j ACCEPT iptables -A OUTPUT -p tcp --match multiport --dports 25,587,465 -j REJECT

You cannot repair an InnoDB type table, If you want to repair them you’ll have to change the table engine from InnoDB to MyIsam. To Do this, follow these simple steps Open your phpmyadmin Select the database you want to repair. Look for the table(s) with InnoDB type storage engine and note down their names. Now you need to perform an SQL command by clicking on the SQL tab that appears on the top section of that page. Now use the command given below ALTER TABLE table_name ENGINE=MyISAM; Replace the table_name with the name of the table you want to change from InnoDB to MyISAM. Note: You will have to do the table change one by one. For each time, chose one table and change its engine and so on.