-
Notifications
You must be signed in to change notification settings - Fork 4
Error messages
A list of error messages the bot can output
If the error message you received is not shown here or the solutions do not work for you, please open up a issue here
The bot was unable to create necessary files during first time setup.
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.
Some file(s) were not present upon the completion of first time setup, although they should exist.
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.
The session information could not be saved to ./cookies/session.json
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.
Instagram thinks that we are a bot, and they are correct on that, kudos to them.
Solution: Login to the Instagram account on a web browser or the Instagram app on your phone. Afterwards, you will see a verification menu pop up. Follow the instructions there and reboot this bot.
There is support for the bot to automatically bypass the verification, but the API Library being used has a bug regarding that feature. When the bug is fixed on their end, I will enable the module on this bot.
The bot was unable to move the image from /assets/images/approved to /assets/images/uploaded
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.
Instagram has rejected our image upload for an unknown reason
Solution: Open up a issue here
The bot was unable to move the image from /assets/images/approved to /assets/images/error
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.
/assets/images/approved is empty. This means that there are no more images for the bot to upload to Instagram. Fret not, it will download more from Reddit when the posts it is monitoring gets taken over by a new one.
Solution: Is the bot posting frequency too high? Modify setInterval(chooseInstaPhoto, 1.5e+6);, changing 1.5e+6 to something less frequent.
1.5e+6 is in milliseconds, roughly translating to one post every 25 minutes
There was a problem with determining the size of the image being uploaded to Instagram
Solution: Reboot the bot and try again
The image has an aspect ratio that is not accepted by Instagram.
Solution: Crop & Resize the image so that it fits Instagram's Image upload requirements, or upload a different Image
The bot was unable to move the image from /assets/images/approved to /assets/images/error
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.
The bot was unable to update insta_password in config.json with the new password you gave it, when the old one failed.
Solution: Restart the bot. If that does not work, ensure that node is being ran with permissions to create directories.
If you are on Linux, is the bot running in the root folder? If so, run it somewhere else.