summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorPliable Pixels <pliablepixels@gmail.com>2020-02-07 10:21:35 -0500
committerPliable Pixels <pliablepixels@gmail.com>2020-02-07 10:21:35 -0500
commit38724fe8719d35bc1b4a7e0bd371bfcb58debab7 (patch)
tree059413595bb32b42d7acd36f6158b07f13d51d58 /docs
parent1d8cfb927b4d082d02f42c77830501145a7451ea (diff)
mention that you should test APIs on the target device
Diffstat (limited to 'docs')
-rw-r--r--docs/guides/validating-api.rst4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/guides/validating-api.rst b/docs/guides/validating-api.rst
index 16a85ecc..a2ca59c3 100644
--- a/docs/guides/validating-api.rst
+++ b/docs/guides/validating-api.rst
@@ -10,10 +10,12 @@ Please make sure you go through this before you wonder why zmNinja is not workin
Make sure ZM APIs are working:
''''''''''''''''''''''''''''''
-(Note - nginx users, if you are facing API issues, please see if `this
+**Note 1**: nginx users, if you are facing API issues, please see if `this
page <https://github.com/pliablepixels/zmNinja/wiki/How-to-configure-APIs-with-nginx>`__
helps)
+**Note 2**: It is **important** that you run the API tests from the device you plan to use zmNinja with. Very often, I've seen folks doing API tests on the same server ZM is running on and then face issues (mostly due to network connectivity) when using zmNinja because it is running on a different device. So, I'd recommend you open a chrome browser on the device you plan to use zmNinja on (desktop or mobile) and then run these tests.
+
- Step 1: Open up a browser
- Step 2: Log into ZM
- Step 3: Open another tab in the same browser (**IMPORTANT**: Has to