diff --git a/docs/content/mega.md b/docs/content/mega.md
index f3abf95fc..27882e342 100644
--- a/docs/content/mega.md
+++ b/docs/content/mega.md
@@ -107,6 +107,44 @@ Use `rclone dedupe` to fix duplicated files.
 
 ### Failure to log-in
 
+#### Object not found
+
+If you are connecting to your Mega remote for the first time, 
+to test access and syncronisation, you may receive an error such as 
+
+```
+Failed to create file system for "my-mega-remote:": 
+couldn't login: Object (typically, node or user) not found
+```
+
+The diagnostic steps often recommended in the [rclone forum](https://forum.rclone.org/search?q=mega)
+start with the **MEGAcmd** utility. Note that this refers to 
+the official C++ command from https://github.com/meganz/MEGAcmd 
+and not the go language built command from t3rm1n4l/megacmd 
+that is no longer maintained. 
+
+Follow the instructions for installing MEGAcmd and try accessing 
+your remote as they recommend. You can establish whether or not 
+you can log in using MEGAcmd, and obtain diagnostic information 
+to help you, and search or work with others in the forum. 
+
+```
+MEGA CMD> login me@example.com
+Password:
+Fetching nodes ...
+Loading transfers from local cache
+Login complete as me@example.com
+me@example.com:/$ 
+```
+
+Note that some have found issues with passwords containing special 
+characters. If you can not log on with rclone, but MEGAcmd logs on 
+just fine, then consider changing your password temporarily to 
+pure alphanumeric characters, in case that helps.
+
+
+#### Repeated commands blocks access
+
 Mega remotes seem to get blocked (reject logins) under "heavy use".
 We haven't worked out the exact blocking rules but it seems to be
 related to fast paced, successive rclone commands.