It's B

Author: Bunty ( Site Admin )

  • How to setup Stripe test account on MemberPress

    MemberPress forces to have a valid account to connect with stripe which is great for the LIVE site.

    But when it comes to testing payment using a test account, then also MemberPress forces to have a valid account.

    But there is a workaround to setup test account without an account which has not all the data filled in the Sandbox account.

    When you open your MemberPress -> Settings -> Payments tab, the URL will end up like:

    /wp-admin/admin.php?page=memberpress-options#mepr-integration

    Then change it manually to /wp-admin/admin.php?page=memberpress-options&display-keys and click back to the Payments tab.

    You’ll see the fields where you’ll be able to add the keys manually. Copy/paste them from your Stripe and then go to Stripe DashBoard -> Developers -> Webhooks and click “Add Endpoint” button: https://prntscr.com/rsgtw9

    Then paste the Webhook URL from MemberPress and add these events: https://prntscr.com/rsguc1

    Save everything and you should have the manual test connection completed.

    If you use any caching plugin, don’t forget to set it as explained in How to Set Up Popular Caching Plugins with MemberPress? and you should be good to go. 🙂

     

    That’s it

  • Fix – ERROR 2006 (HY000) while importing database in MySQL

    While importing big database in MySQL, you might get the error as shown below:

    ERROR 2006 (HY000) at line 3387 in file: 'path_to_the_db_dump.sql': MySQL server has gone away

    Step 1:

    Open a terminal and find a config file for MySQL by command locate my.cnf.

    You will get the list of files. Open your responsible file.

    If you don’t know the responsible file then open all the files ;). There is no harm to add our solution in all the related config file.

    Step 2:

    Add following line to my.cnf file.

    max_allowed_packet=64M

    Restart your MySQL using below command.

    sudo service mysql restart 
OR
brew services restart mysql

    That’s it!!!!

  • Fix – upstream sent too big header while reading response header from upstream in Nginx

    For this fix please visit below link.

    https://bhargavb.wordpress.com/2020/02/28/fix-404-error-on-nginx/

  • Fix – ERROR 1031 Table storage engine for ‘table_name’ doesn’t have this option

    Sometimes you get the below error while importing the database.

    ERROR 1031 (HY000) at line 5643 in file: '/Users/username/Downloads/database.sql': Table storage engine for 'table_name' doesn't have this option

    Now let’s fix this.

    Step – 1

    Open your sql file in your favourite editor and go to SQL query of that table.

    You will see ROW_FORMAT=FIXED at the last of the query and remove that.

    Step – 2

    Save your file and try to import the database. This should fix the error.

     

    That’s it

  • Fix 404 error on nginx

    Fix 404 error on nginx

    Sometimes you get unexpected 404 error from Nginx server. And I am going to tell you how I fixed the issue.

    You can fix that easily by the following steps:

    Step 1 (Debugging):

    You first need to find out the reason. For that, you can the first login to your server via ssh and check the error log for Nginx server.

    Open the following file: /var/log/nginx/error.log and check the latest errors.

    In my case I was having the following error:

    2020/02/28 08:19:02 [error] 17627#17627: *14299 upstream sent too big header while reading response header from upstream, client: 172.31.4.43, server: yoursite.com, request: "GET /wp-login.php?action=switch_to_user&user_id=2928&nr=1&_wpnonce=9085bda773&redirect_to=https%3A%2F%yoursite.co%2Fmembers%2Fdesigner-buddyboss%2F HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.1-fpm.sock:", host: "yoursite.co", referrer: "https://yoursite.co/members/designer-buddyboss/"

    Step 2 (Solution):

    After exploring on google I found this solution which worked for me. We need to add the following lines into the Nginx config file:

    client_max_body_size 128m;
fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;

    Now the following file could be responsible for your site:

    Check if this file available /etc/nginx/sites-enabled/your_site.conf ( This was the responsible file in my case )

    OR

    /etc/nginx/sites-available/your_site.conf

    OR

    /etc/nginx/sites-available/nginx.conf

    Open one of the files.

    Step 3 (Apply Solution):

    Now add those 3 lines into the config file like this

    After adding this restart Nginx server by the following command:

    sudo service nginx restart

    That’s it!!!!