Sysadmin test server

background official mysql docs MySQL :: MySQL 5.6 Reference Manual :: 13.7.1 Account Management Statements

---

 

ah it's due to backslashes having different meaning on SSH command line to mean a command

Code (Text):

`dbname`

change and remove backslashes

Code (Text):

`dbname`.*

to

Code (Text):

dbname.*

so

Code (Text):

mysql -e "GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE ON dbname.* TO 'dbuser'@'localhost';"

 

sorry my mistake updated instructions to remove backslashes at https://community.centminmod.com/threads/test-server.12225/page-2#post-51824

 

done info removed/replaced

also updated both guides with corrected step for grant migrations

• How To Transfer cPanel/WHM Sites To Centmin Mod LEMP Servers
• Centmin Mod Site Data Migration Guide

 

the guide at Centmin Mod Site Data Migration Guide transfers all site domains including the demodomain vhost from live to remote/new server

 

main host.domain.com for server is always only non-HTTPS based

or you mean your domain.com site ?

please clarify which server you visiting live or remote/new server's copy ?

 

main host.domain.com for server is always only non-HTTPS based as outlined in getting started step 1

summary for getting started guide

that's normal as no valid DNS for demo domain will always direct to main host.domain.com vhost

have you setup domain's local hosts file edit to preview domain yet Centmin Mod Site Data Migration Guide ?

 

if you have done local hosts edit preview to bypass DNS, and properly copied via rsync all site data to remote/new server, make sure you restarted nginx and php-fpm on remote/new server for the new vhosts to take effect

ensure all the nginx site config files outlined at https://centminmod.com/configfiles.html match on both live and new/remote servers

i.e. nginx vhost files at /usr/local/nginx/conf/conf.d

Code (Text):

ls -lah /usr/local/nginx/conf/conf.d

nginx ssl files at /usr/local/nginx/conf/ssl/

Code (Text):

ls -lah /usr/local/nginx/conf/ssl/

 

that is correct so you are visit mymaindomain.com on new server and that is down on new server if you comment out the line with hash in front and clear browser cache, should go back to visiting live server version

check remote/new server nginx vhost configs are matching live servers Sysadmin - test server

if you set a specific IP address to listen to in nginx vhost domain.com.conf and domain.com.ssl.conf on live server instead of just listen 80; directive, then on new server need to change that listen ip to the new remote server's ip.

 

on your live server, you can check the remote/new server's listing for nginx vhosts and ssl directory via commands

Code (Text):

remoteip=111.222.333.444
port=22
privatekey=my1.key

privatekey was created via keygen.sh so leave it as my1.key value and change remoteip variable to your remote server's ip
then to check type

check nginx vhosts on remote server, you are ssh in with private key and listing via ls command remote directory

Code (Text):

ssh -p $port -i $HOME/.ssh/$privatekey root@$remoteip ls -lah /usr/local/nginx/conf/conf.d

for nginx ssl directories

Code (Text):

ssh -p $port -i $HOME/.ssh/$privatekey root@$remoteip ls -lah /usr/local/nginx/conf/ssl