Troubleshooting

January 26, 2021

let’s tal

Introduction

This guide explains about the usage of trouble shooting tool(s) available to you while using Peerplug.

Peerplug product has simple promise “Any app should function the same way without Peerplug as it functions with Peerplug but faster”.

Using this promise we can troubleshoot any Peerplug-enabled application by temporary disabling Peerplug SDK for that specific device and the host app should function the same way while SDK is disabled as it does when the SDK is enabled. 

What disabling Peerplug SDK does?

Once Peerplug SDK is started. It establishes a communication with your private console, registers as “Provisioned peer” and receives various runtime configuration parameters.

Until the above has happened, Peerplug SDK will not interfere with the host application in any way. It will not intercept or analyze the application traffic and will keep trying to establish communication if the internet is temporary unavailable.

Peerplug console can deny provisioning, meaning that it actively instructs the SDK to disable itself and not affect anything (this what happens if you subscription has ran out). In this case, SDK will not try to re-provision and will silently stop until it is restarted. All the resources are freed and all internal threads are stopped.

Therefore, an SDK that has been provision-blocked has no effect on the host app.

Peerplug product has simple promise “Any app should function the same way without Peerplug as it functions with Peerplug but faster”.

Using this promise we can troubleshoot any Peerplug-enabled application by temporary disabling Peerplug SDK for that specific device and the host app should function the same way while SDK is disabled as it does when the SDK is enabled. 

How to use blocking for troubleshooting

It is possible to instruct the console to temporary disable the Peerplug SDK at specific IP address using Peerplug support section.

Once block on specific IP is enabled. Peerplug console will deny provisioning to any SDK instance trying to connect from that source IP.

If you have a doubt about Peerplug compatibility with your app. Once you have Peerplug-enabled your app you can temporary disable the SDK by adding the IP you are connecting from to the block-list.

Temporary blocking/disabling Peerplug SDK

Please login to your personal Peerplug console and switch to “Support” section of the console: 

Please check your public IP address. If you are connecting from the same Internet connection as the device you want to block, you may click “What is my IP ?” button and it will display your current public IP address. Otherwise please check the public IP address of the device you want to block-list.

Please type the IP address at the input field and click the block button. Console will inform you that the IP address you have entered is now blocked. It will now appear in the list of blocked IP addresses and you will see the block expiration timer.

Please try starting up a Peerplug enabled application. Once Peerplug SDK is started, it will be denied provision and you should see “Number of denied provisions” counter being increased by 1. This will allow you to make sure that you have entered the correct IP address and the Peerplug SDK has indeed been blocked:

Run your tests and ensure your application runs properly. If you see that your application is misbehaving, it is probably not Peerplug related.

If your block is about to expire, just copy paste the IP address and press the block button again it will reset the timer.

Expired entries are not auto removed but do not prevent SDK from provisioning.

Once your application is performing properly enable Peerplug SDK back by removing the block or let it expire.

If any misbehavior occurs only when Peerplug SDK is enabled then it is most likely that your Peerplug console is miss-configured and you should contact your Peerplug support agent to solve it.

Thank You for using Peerplug.