managed server

Error:  Allowed memory size of 792723456 bytes exhausted (tried to allocate 184320 bytes) in /var/www/html/Demo/vendor/magento/framework/Profiler.php on line 153 cause: Low memory value in php.ini just vi /etc/php.ini and set php memory value to be 2048M

Error: FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught Magento\Framework\Exception\FileSystemException set file owner correctly chown -R admin:group public_html

Error: PHP Warning:  realpath(): open_basedir restriction in effect. File(/tmp) is not within the allowed path(s) cause /tmp directory is not accessible by the user just open config file vi domain.httpd.conf php_admin_value open_basedir /home/bumserver/web/bumserver.ga/public_html:/home/bumserver/tmp:/tmp and add the directory which is not within the allowed path

/etc/yum.repos.d/ you will have all the list of repo that is added to the system  to enable a package just vi that repo name like  vi remi.repo just change enabled=1 1 means enabled and 0 means disabled to check the packages that are currently enabled  just do yum repolist or dnf repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile epel/x86_64/metalink                                                             | 5.9 kB  00:00:00       * base: mirrors.praction.in  * epel: repos.del.extreme-ix.org  * extras: mirrors.praction.in  * remi: rpms.remirepo.net  * remi-php73: rpms.remirepo.net  * remi-safe: rpms.remirepo.net  * updates: mirrors.praction.in base        ...

check if you have two web server whether both the server is running or not systemctl status nginx systemctl start nginx and systemctl status httpd systemctl start httpd or check if you are using php-fpm wheather it is running or not systemctl status php-fpm if not start with systemctl start php-fpm

be sure to perform in a public_html folder: CODE:  SELECT ALL find . -type f -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \; chown -R user:group * of course, replace user and group to vesta username. And there must be index.php or index.html. This usually enough.

Error: Internal WordPress links 404 after migration add this line in the configuration file I'm using wordpress multisite with custom permalink setting: /%category%/%postname%/ /etc/nginx/site-available/domain.conf for vestacp add in both files yourhosting.in.nginx.ssl.conf yourhosting.in.nginx.conf On server{ location / { try_files $uri $uri/ /index.php?$args; } Greetings! This can be difficult to eyeball so I’m going to try my best. I think it’s this line: try_files $uri $uri/ /index.php?q=$uri&$args; I believe adding the $uri to the end may be breaking it. What if it were instead: try_files $uri $uri/ /index.php?$args; You can find more about Nginx config for Wordpress here: https://codex.wordpress.org/Nginx Jarland or add this in .htaccess <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php ...

Setting sync with Internal IP will save a lot of cost Master-slave data replication allows for replicated data to be copied to multiple computers for backup and analysis by multiple parties. Needed changes identified by a group member must be submitted to the designated “master” of the node. This differs from  Master-Master replication , in which data can be updated by any authorized contributor of the group. This article provides steps for setting up MySQL® master-slave database replication between two cloud servers. The operating system used for the examples in the article is CentOS® 6, built from a Rackspace Cloud Servers base image. Before you begin The steps in this article use two cloud servers,  db01  and  db02 . Cloud servers have two IP addresses (one public, one private). The examples demonstrate configuring replication over the private IP interface so that no bandwidth charges are incurred. For the duration of the article,  db01  is con...

1. Log in to your CentOS 7 VPS via SSH as user root # ssh root@IP_Address and update all installed services # yum update 2. Run the ‘arch’ command in the terminal to check if your system is 32-bit (i686) or 64-bit (x86_64) # arch x86_64 3. In our case the system is 64-bit and we will download the 64-bit version of ionCube Loader # wget http://downloads3.ioncube.com/loader_downloads/ioncube_loaders_lin_x86-64.tar.gz 4. If your system is 32-bit download the following archive # wget http://downloads3.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz 5. Once it is downloaded, unpack the tar archive # tar xfz ioncube_loaders_lin_x86-64.tar.gz The ionCube Loaders for all PHP versions will be extracted in a new ‘ioncube’ directory. 6. We need to know the PHP version installed on the server. We can find out using the following command # php -v PHP 5.4.16 (cli) (built: Aug 11 2016 21:24:59) Copyright (c) 1997-2013 The PHP Group Zend Engine v2.4.0, Copyright (c) ...

checkout /usr/local/vesta/ssl/ directory. Replace files accordingly and restart vesta service vesta restart vi /usr/local/vesta/nginx/conf/nginx.conf  # Vhost     server {         listen          8083;         server_name     _;         root            /usr/local/vesta/web;         charset         utf-8; ./certbot-auto certonly --webroot -w /usr/local/vesta/web -d server.cloudserverfree.com