mainigautam / instagram_backup_manager

This Is A Simple Web Based Application which makes your Instagram Backup Data readable to a great extent. Call it "Instagram Backup Manager" or "Instagram Backup Data Viewer"

This Branch is For Latest Backups Format, Looking for Ways to access older backups? Have a Look Here

Instagram Backup Manager / Instagram Backup Data Viewer

A Simple web application makes your Instagram Account Backup Data Accessible to a great extent .

Pre-Requisite

You must have internet connection (to install dependencies) and You Must have node.js installed on your pc , I have provided links and methods for those below.

Advance users can use git clone to clone the repo and use suitable terminal commands for batch files.

You can delete the client folder it is for open source sharing purposes only , App can work without it too.

How to Setup

Windows Users

Download Node.js

Linux Users

sudo apt-get upgrade && sudo apt-get install nodejs

MacOS

Download Node.js

Setup

[*] It's Pretty Easy just click on "Code Button" (The One in Green Colour) then --> "Download Zip" to download code.

[*] After Downloading , Extract the zip file

[*] Now go to server folder and run (double click) setup.bat to install all the dependencies.

[*] After Setup is Done, open/run/double-click run.bat in the same folder.

[*] Then Open Your Browser and type http://localhost:8081/ to access the application

Features

• Display Profile Data With Images
• Stories Archive (Pics and Videos)
• Direct Messages With Likes ,TimeStamps , Reactions and Media Exchanged
• Instagram Desktop UI Clone
• Followers and Following Number and Lists.
• Just Upload Backup Zip and Explore you backup data

Todo:

• Upload Screenshots
• Consume More Data from Backups
• Improvements in UI
• Add Chat-Wise Media Browser
• Add Lazy-Loading to Optimize Rendering
• In-page browser frame to Link to Instagram External Links.

Known Bugs

• Lengthy Chats can cause app to hang and Load in longer timings
• Tell More If You Find

Note

Instagram Has put many limitations in the backup version of your accounts it dosen't provide the likes and comments information so i cannot do anything about the stuff instagram itself dosen't provide

For Reels Shared in DMs You'll see a Reel Icon only as Instagram hasn't provided the backup with that data yet.(11/04/2022)

Backups Dated Before March 2021 may vary in layout from those of 2022 and Different Branch of application to be used for same

Feel Free To Give Pull Requests and Comment Feature Requests.

Screenshots

Thanks To Makers Of

Node.js React.js Concurrently Nodemon Express.js Del Multer Facebook(LLC)

instagram_backup_manager's Issues

I cant see the direct messages due to an error

I cant see the direct messages due to an error on client/src/components/Messages.js line85 [TypeError: Cannot read property 'length' of undefined]

[Fixed-27012021][CONFIRMED] Direct message parse error for backups taken in 2021

When I click on the Direct button the server tries to parse the messages JSon file but after some time I get the following error:

[1] SyntaxError: Unexpected end of JSON input
[1]     at JSON.parse (<anonymous>)
[1]     at C:\Users\Labtop\Documents\GitHub\instagram_backup_manager\server\api\routes\messages.js:12:23
[1]     at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)

What is causing this issue? Any help is appreciated.

Instagram Backup Manager not rendering stories, reels and profile pictures.

Hi, the tool works great for messages but I can't view my stories and reels. It's all empty placeholders.

Could not proxy request /upload

Ive no idea of coding etc. i just wanted to read my Instagram backups in a simple way.
I followed every step and managed to get to the point where i can upload my .zip file.
First when i tried to upload it said "Proxy error: Could not proxy request /upload from localhost:3000 to http://localhost:9000/.
[2] See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNREFUSED )".
After googling a bit i found out to change the local host from 9000 to 3000 in the package.json (idk if this was right).
Now it uploads but at some point (mostly 32%) it stops and the cmd says "Proxy error: Could not proxy request /upload from localhost:3000 to http://localhost:3000/.
[2] See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNRESET)."

Maybe im just dumb but i really want to see my Instagram Backup file and sorry if bothering with "noob" questions^^

friends images can be grabbed if the links are still vailed.

this an html file generated from the zip file using a tool a friend provided a year ago and it shows the images with no problem.... ( note the file is generated a long time ago)

"it dosen't provide the likes, comments and the pictures sent by your friends and i cannot do anything about the stuff instagram itself dosen't provide"

why are you saying this ?

while the same image in your tool

edit : tested the tool again and it shows image not available looks like it used to download the images from the links first but the links have Expiration date i think.

after uploading file is just stops

also as per you previous answers i can't find this " %IGBM_DIR%/server/data/" directory

Problems with dependencies

I am trying to run this utility (arch linux) but I get an dependency erronpm WARN [email protected] No repository field.

audited 54 packages in 0.932s

3 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

[email protected] dep /home/daniel/Desktop/IG/igbm
concurrently "npm run server-dep " "npm run client-dep "

[1]
[1] > [email protected] client-dep /home/daniel/Desktop/IG/igbm
[1] > cd client && npm install
[1]
[0]
[0] > [email protected] server-dep /home/daniel/Desktop/IG/igbm
[0] > cd server && npm install
[0]
[0] npm WARN [email protected] No description
[0] npm WARN [email protected] No repository field.
[0] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
[0] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[0]
[0] audited 173 packages in 1.429s
[0]
[0] 8 packages are looking for funding
[0] run npm fund for details
[0]
[0] found 0 vulnerabilities
[0]
[0] npm run server-dep exited with code 0
[1] npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
[1] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[1] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[1] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[1] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/watchpack-chokidar2/node_modules/fsevents):
[1] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[1]
[1] audited 1635 packages in 11.887s
[1]
[1] 66 packages are looking for funding
[1] run npm fund for details
[1]
[1] found 1 high severity vulnerability
[1] run npm audit fix to fix them, or npm audit for details
[1] npm run client-dep exited with code 0

I have tried to install manually the typescript component

npm install typescript
npm WARN [email protected] No repository field.

• [email protected]
  added 1 package from 1 contributor and audited 55 packages in 14.405s

3 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

But I get the same error..

DM threads with specific type of folder name are not parsed

Hi,

So I downloaded my data and when I was trying to access a specific person's DM I realized it wasn't being parsed by your tool. I tried to find out the reason for that and I found something though I'm not sure if it's the actual reason for such behavior.

Look here 👇🏻

This is the one which is not shown in your tool. I think because it does not have any username part in it's folder name like this one 👇🏻 for example

Please share your thoughts on this and also how I can view such chats from your tool.
PS: I've not edited a single thing in the backup. Everything is as it was downloaded. Also, this is the only folder with such naming.

Thanks a loads!

After uploading the zip file the app gets stuck in the insta logo

Issues building the project?

I do not see a 'build' script within the /server/package.json, and have been unsuccessful in finding a node command to do so.
Could you tell me how you are able to recompile and rebuild the project.

I'd like to extend the client/component/Messages2.json to include more information from messages, however I am not able to see my changes without rebuilding the static routes in the /server.

Thanks, any insight would be appreciated, your project is just what I was looking for.
-Justin

[Confirmed]Large DMs are not displayed completely

Hi again,

Ok so the DMs are getting loaded but I noticed one problem that if the number of chats are huge, all of them are not getting loaded. For example I have a conversation which has roughly 10,000+ messages in it. The messages JSON is split into multiple files (6 in my case) and currently IGBM is loading only one of these 6 JSON files. I think it's coded to parse only the first JSON it finds per DM.

This is the folder structure of one of the DM threads:

And IGBM only loads the content from message_1.json.
Chronological order of messages is from message_6.json -> message_1.json, so IGBM loads only the latest messages from the backup. Previous messages are skipped.

I think one work around can be to manually merge all JSON files into one JSON file and then load this modified backup into IGBM. What do you think about this?

PS: Merging files is not a big deal for me but I thought I should let you know about the bugs.

Thanks for the wonderful repo.
Cheers!

Run file not working, it get stuck after opening the explorer

this is the code when it get stucked :-
`
C:\Users\HP\Downloads\instagram_backup_manager-igbm-1.0\instagram_backup_manager-igbm-1.0>npm start

[email protected] start
concurrently - kill-others "npm run server" "npm run client"

[0] '-' is not recognized as an internal or external command,
[0] operable program or batch file.
[0]  - kill-others exited with code 1
[2]
[2] > [email protected] client
[2] > cd client && npm start
[2]
[1]
[1] > [email protected] server
[1] > cd server && npm start
[1]
[2]
[2] > [email protected] start
[2] > react-scripts start
[2]
[1]
[1] > [email protected] start
[1] > nodemon server.js
[1]
[1] [nodemon] 2.0.4
[1] [nodemon] to restart at any time, enter rs
[1] [nodemon] watching path(s): .
[1] [nodemon] watching extensions: js,mjs,json
[1] [nodemon] starting node server.js
[1] Server is Up And Running , We are Serving Files Now!
[2] i ｢wds｣: Project is running at http://192.168.1.9/
[2] i ｢wds｣: webpack output is served from
[2] i ｢wds｣: Content not from webpack is served from C:\Users\HP\Downloads\instagram_backup_manager-igbm-1.0\instagram_backup_manager-igbm-1.0\client\public
[2] i ｢wds｣: 404s will fallback to /
[2] Starting the development server...
[2]
[2] Browserslist: caniuse-lite is outdated. Please run:
[2] npx browserslist@latest --update-db
[2] Compiled successfully!
[2]
[2] You can now view igbm in the browser.
[2]
[2] Local: http://localhost:3000
[2] On Your Network: http://192.168.1.9:3000
[2]
[2] Note that the development build is not optimized.
[2] To create a production build, use npm run build.
[2]
[1] C:\Users\HP\Downloads\instagram_backup_manager-igbm-1.0\instagram_backup_manager-igbm-1.0\server\api\routes\profile.js:8
[1] throw err;
[1] ^
[1]
[1] [Error: ENOENT: no such file or directory, open 'C:\Users\HP\Downloads\instagram_backup_manager-igbm-1.0\instagram_backup_manager-igbm-1.0\data\profile.json'] {
[1] errno: -4058,
[1] code: 'ENOENT',
[1] syscall: 'open',
[1] path: 'C:\Users\HP\Downloads\instagram_backup_manager-igbm-1.0\instagram_backup_manager-igbm-1.0\data\profile.json'
[1] }
[2] Proxy error: Could not proxy request /connections from localhost:3000 to http://localhost:9000/.
[2] See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNRESET).
[2]
[2] Proxy error: Could not proxy request /profile from localhost:3000 to http://localhost:9000/.
[2] See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNRESET).
[2]
[1] [nodemon] app crashed - waiting for file changes before starting...
[2] Proxy error: Could not proxy request /media from localhost:3000 to http://localhost:9000/.
[2] See https://nodejs.org/api/errors.html#errors_common_system_errors for more information (ECONNREFUSED).
[2]

`

Error running the app

After run 'npm start' it doesn't start and I get an error:

"no s'ha trobat l'ordre" means command not found

(~/Desktop/IG/igbm)─(7 files, 40Kb)─> npm start

[email protected] start /home/daniel/Desktop/IG/igbm
concurrently - kill-others "npm run server" "npm run client"

sh: concurrently - kill-others: no s'ha trobat l'ordre
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! [email protected] start: concurrently - kill-others "npm run server" "npm run client"
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/daniel/.npm/_logs/2020-10-07T19_34_49_169Z-debug.log

2020-10-07T19_34_49_169Z-debug.log

Log attached

Module not found: Can't resolve './Reels'

Hi,

I cloned your repo and ran the setup.bat file, everything was fine. But, when I ran run.bat after a while I get the Module not found: Can't resolve './Reels' error

I've attached 2 screenshots, one of PowerShell and other of browser tab which is opened automatically.
PowerShell

Browser (http://localhost:3000/)

PS: This repo used to work around 10 days ago, I think the error is because of some changes that were committed to the repo later on.

Please share your thoughts on this.
Thanks!