Dev {Tricks}

You are here: Home / Archives for Server and Hosting / VPS Management

by

Verify your SPF and DKIM records

How to verify your DKIM records

To check DKIM verification:

  1. Go to http://dkimcore.org/tools/keycheck.html.
  2. In the Selector field, enter SENDER.
  3. In the Domain name field, enter your domain name (without www).
  4. Click Check.
  5. If your DKIM Key is valid, the following message displays: This is a valid DKIM key.
  6. Compare the key to your DKIM records in DNS Records.

How to verify your SPF records

To check SPF verification:

  1. Go to http://www.webtoolhub.com.
  2. In the Enter URL field, enter the full domain name and click Show.
  3. Compare the key to your SPF records in DNS Records.

by

Migrate aaPanel to New Server using One-Click Migration Tools

  • How to migrate aaPanel account(s) from server A to server B
  • aaPanel settings migration.
  • Cloning aapanel accounts
  • Moving from old error aapanel to new aapanel server
  • How To Migrate Data On aaPanel With 3 Steps
  • How Migrate aaPanel using One-Click Migration API version 3.0
  • ERROR After Migration to AAPANEL

Follow the following steps to migrate aaPanel account(s) easily.

On new Server:

  1. Install aaPanel
  2. Set server configuration same as old server
  3. Update aaPanel to latest version
  4. Click API (Panel Setting) and allow API
  5. Reset API to get new api key and enter whitelist IP (ip address of old server)

On old server:

  1. Update aaPanel to latest version
  2. Install “One-Click Migration”
  3. Open “One-Click Migration” and enter required data
    1. Target panel Addr: Panel address. For example, https://103.81.224.71:7800
    2. Target panel API: API from new server
    3. Select website(s) and database(s)
  4. Just follow the steps and choose which website you want to migrate, then wait for the process, then you’re done

 

 

 

 

by

MySQL: Error Code: 1118

  • #1118 – Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
  • Change limit for “Mysql Row size too large”
  • Row size too large 8126 Changing some columns
  • 1118 Row size too large

The error was: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

  • Solution
  • Login to phpMyAdmin with root previllege
  • Go to Variables
  • Then edit Innodb Strict Mode as follows 
    innodb_strict_mode = 0

 

by

How to change the SSH port | WHM

How to change the SSH port

  • Log in to the server with root user
  • Open /etc/ssh/sshd_config. 
    vi /etc/ssh/sshd_config
  • Edit the port line. Change the default port 22 to your choice, for example 1234. 
    port 1234
  • Restart SSHD 
    /scripts/restartsrv_sshd
  • Test SSH while specifying the new port 
    ssh USER@HOSTNAME -p1234
  • Please use your USER and HOSTNAME and the new port
  • If unsuccessful, add the new SSH port to your firewalls and then retest.
  • If the SSH test on the new port is successful then you can reboot and log in to the server with new port.

 

by

How To Create a New User and Grant Permissions in MySQL

Access MariaDB Server

mysql -u root -p

Create new database

CREATE DATABASE bdhostidb;

Check whether the database created

SHOW DATABASES;




GRANT ALL PRIVILEGES ON 'sqI_bdhositit_co'.* TO 'sqI_bdhositit_co'@localhost;