As the title says, the IP8M-2496EB-40MM was working awesome until recently when I attempt to navigate to the web UI it just shows a completely white blank page. I've tried clearing cache, deleting certs, etc. but still nothing. This also happens with the IP2M-841B. This has also happened before on another camera I had from amcrest, but I don't remember the model and I've since thrown that camera away for this same problem.
This is ridiculous. I've only had this camera for a couple months, and this is the third amcrest camera I've had this happen on.
IP8M-2496EB-40MM - Web UI started displaying blank page
-
- Posts: 3
- Joined: Sun Dec 27, 2020 2:42 pm
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
Hello and Welcome to the Forum
Sadly not sure I understand what is going on. Can you take a Snap shot of the screens and upload them..
Other then that The next guess would be that you might have made some changes in the camera and they need to be Reset because of the changes that were made if you don't know how to change back out of the issue spot..
ON the 841 the LED is also a BUTTON just press and hold it while you have power to the camera, Once the camera starts to Reset this can take 30 to 45secs on some cameras I can't remember to be honest how long it takes for the 841 it has been some time and a Few other cameras between since I last Reset one.. You will know because it will have the LED go out and the camera will start to move in it start up check mode.. Once you are done and if you have setup the camera and the feed is back I would Reset the 2496.. I am not sure about that camera,, But there is going to be a Button or an area on the MB to make it reset.. If no button is present you will have to short out a couple of pins that will have Reset next to them so you know they are the right ones.. If not I could try and look it up in a manual or see if there is a Video on Amcrest youtube Channel
Sadly not sure I understand what is going on. Can you take a Snap shot of the screens and upload them..
Other then that The next guess would be that you might have made some changes in the camera and they need to be Reset because of the changes that were made if you don't know how to change back out of the issue spot..
ON the 841 the LED is also a BUTTON just press and hold it while you have power to the camera, Once the camera starts to Reset this can take 30 to 45secs on some cameras I can't remember to be honest how long it takes for the 841 it has been some time and a Few other cameras between since I last Reset one.. You will know because it will have the LED go out and the camera will start to move in it start up check mode.. Once you are done and if you have setup the camera and the feed is back I would Reset the 2496.. I am not sure about that camera,, But there is going to be a Button or an area on the MB to make it reset.. If no button is present you will have to short out a couple of pins that will have Reset next to them so you know they are the right ones.. If not I could try and look it up in a manual or see if there is a Video on Amcrest youtube Channel
Be Safe.
-
- Posts: 3
- Joined: Sun Dec 27, 2020 2:42 pm
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
When I navigate to the IP address in my browser, the web page that is displayed is just a blank, white web page. The camera has been working fine over the past few months, but suddenly stopped working and just displays a white page. The RTSP stream is still streaming video, but the web UI on the camera isn't working so I can no longer configure the camera. The camera is mounted up high, so I'd like to see if there's another way to fix this than having to remove the camera to do a reset.Revo2Maxx wrote: ↑Sun Dec 27, 2020 5:52 pm Hello and Welcome to the Forum
Sadly not sure I understand what is going on. Can you take a Snap shot of the screens and upload them..
Other then that The next guess would be that you might have made some changes in the camera and they need to be Reset because of the changes that were made if you don't know how to change back out of the issue spot..
ON the 841 the LED is also a BUTTON just press and hold it while you have power to the camera, Once the camera starts to Reset this can take 30 to 45secs on some cameras I can't remember to be honest how long it takes for the 841 it has been some time and a Few other cameras between since I last Reset one.. You will know because it will have the LED go out and the camera will start to move in it start up check mode.. Once you are done and if you have setup the camera and the feed is back I would Reset the 2496.. I am not sure about that camera,, But there is going to be a Button or an area on the MB to make it reset.. If no button is present you will have to short out a couple of pins that will have Reset next to them so you know they are the right ones.. If not I could try and look it up in a manual or see if there is a Video on Amcrest youtube Channel
Below is what the screenshot of the web page looks like when I navigate to the IP address in my browser:
![Image](%5Battachment=0%5DScreenshot_2020-12-28%20Screenshot.png%5B/attachment%5D)
- Attachments
-
- Screenshot_2020-12-28 Screenshot.png (8.65 KiB) Viewed 23383 times
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
Sadly I don't know if it isn't displaying even the WebUI portion of of the screen then there is something wrong with your browser.. I would try to clear cache or do something to clean out the history of the page.. Maybe if you don't have IP config I would try and DL that and use the IP portion to change the IP address in IPCONFIG to see if it will load in a different IP..
So say right now you have your ip setup for 10.1.120.111 for the camera, I would setup the camera to 10.1.120.120 and then try and access the WebUI on a different IP
Other then that.. 841 PRess and hold button and do a Config at Wifi right there no need to take it down but is the first camera I would do a reset on if there is no change doing a IP change..
So say right now you have your ip setup for 10.1.120.111 for the camera, I would setup the camera to 10.1.120.120 and then try and access the WebUI on a different IP
Other then that.. 841 PRess and hold button and do a Config at Wifi right there no need to take it down but is the first camera I would do a reset on if there is no change doing a IP change..
Be Safe.
-
- Posts: 3
- Joined: Sun Dec 27, 2020 2:42 pm
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
I already mentioned in my original post that I've tried clearing the cache, deleting history, using a different browser, deleting certificates, etc. It's not my browser - it's the camera. When I navigate to the IP address of the camera, it does not display an error, it just displays a blank page. The camera isn't serving the web page files like it's supposed to.Revo2Maxx wrote: ↑Mon Dec 28, 2020 11:46 pm Sadly I don't know if it isn't displaying even the WebUI portion of of the screen then there is something wrong with your browser.. I would try to clear cache or do something to clean out the history of the page.. Maybe if you don't have IP config I would try and DL that and use the IP portion to change the IP address in IPCONFIG to see if it will load in a different IP..
So say right now you have your ip setup for 10.1.120.111 for the camera, I would setup the camera to 10.1.120.120 and then try and access the WebUI on a different IP
Other then that.. 841 PRess and hold button and do a Config at Wifi right there no need to take it down but is the first camera I would do a reset on if there is no change doing a IP change..
I don't understand what you mean when you say:
When I first set up the camera I was able to login to the web UI and statically assign an IP address. I can't change the IP of the camera without being able to access the web UI.Maybe if you don't have IP config I would try and DL that and use the IP portion to change the IP address in IPCONFIG to see if it will load in a different IP..
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
You can access the IP using as I said IP config is a tool that is on your CD that comes with the camera and or by DL from Amcrest Website you can find it here... https://support.amcrest.com/hc/en-us/ar ... g-Software
I understand that you said you had, I was just saying that maybe doing it again and this time delete all cache if you choose not to as a way to keep some data that you feel is important.. I have in the past had to clear more then once..
Sadly 2 other things that can happen.. 1 You can Do a Reset as I said.. This will bring back all the things to factory incase things became corrupt some how... Doing a Reset is the Fix of all things
2 DL and install the FW for the camera again.. I don't know how it couldn't be related to your browser when your saying that the issue is for 2 cameras it would make no since that your 2 cameras would stop working at the same time unless something in the computer has caused an error and this again makes me wonder what the issue could be related for 2 different type of cameras that are going to use different plugins... It might be that you have your Plugins turned off.. If the 2 cameras are being used on Chrome, then try Edge or IE even though IE keeps popping up that it is outdated I still use it for cameras that need it and can even use for cameras that can't use it because they are Chrome based just don't give me picture but would load the page again I am trying to get an idea of the pages loading you already said it won't load
What FW are loaded in the cameras? FW before 2019 or 2020 based FW?
I understand that you said you had, I was just saying that maybe doing it again and this time delete all cache if you choose not to as a way to keep some data that you feel is important.. I have in the past had to clear more then once..
Sadly 2 other things that can happen.. 1 You can Do a Reset as I said.. This will bring back all the things to factory incase things became corrupt some how... Doing a Reset is the Fix of all things
2 DL and install the FW for the camera again.. I don't know how it couldn't be related to your browser when your saying that the issue is for 2 cameras it would make no since that your 2 cameras would stop working at the same time unless something in the computer has caused an error and this again makes me wonder what the issue could be related for 2 different type of cameras that are going to use different plugins... It might be that you have your Plugins turned off.. If the 2 cameras are being used on Chrome, then try Edge or IE even though IE keeps popping up that it is outdated I still use it for cameras that need it and can even use for cameras that can't use it because they are Chrome based just don't give me picture but would load the page again I am trying to get an idea of the pages loading you already said it won't load
What FW are loaded in the cameras? FW before 2019 or 2020 based FW?
Be Safe.
-
- Posts: 1
- Joined: Fri Jul 02, 2021 10:32 am
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
There appears to be a bug in the firmware that does not properly reference the internal CSS and JavaScript pages. If you trace the HTTP conversation you'll see that the GETs for "/js/merge.js" and "/css/merge.css" fail with a 404 (not found) error (trace after the jump). Maybe someday our dreams will come true and Amcrest will fix the firmware load.
Mike
12:20:50.918441 IP Browser.51247 > Doorbell.80: Flags [S], seq 2473268772, win 65535, options [mss 8960,nop,wscale 8,nop,nop,sackOK], length 0
12:20:50.918481 IP Browser.51248 > Doorbell.80: Flags [S], seq 1040465456, win 65535, options [mss 8960,nop,wscale 8,nop,nop,sackOK], length 0
12:20:50.927233 IP Doorbell.80 > Browser.51247: Flags [S.], seq 553246320, ack 2473268773, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
12:20:50.927261 IP Doorbell.80 > Browser.51248: Flags [S.], seq 2666843614, ack 1040465457, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
12:20:50.933493 IP Browser.51247 > Doorbell.80: Flags [.], ack 1, win 1024, length 0
12:20:50.933517 IP Browser.51247 > Doorbell.80: Flags [P.], seq 1:354, ack 1, win 1024, length 353: HTTP: GET / HTTP/1.1
12:20:50.933536 IP Browser.51248 > Doorbell.80: Flags [.], ack 1, win 1024, length 0
12:20:50.957262 IP Doorbell.80 > Browser.51247: Flags [.], ack 354, win 490, length 0
12:20:50.960927 IP Doorbell.80 > Browser.51247: Flags [P.], seq 1:366, ack 354, win 490, length 365: HTTP: HTTP/1.1 304 not modified
12:20:50.960951 IP Doorbell.80 > Browser.51247: Flags [F.], seq 366, ack 354, win 490, length 0
12:20:50.968853 IP Browser.51247 > Doorbell.80: Flags [.], ack 366, win 1022, length 0
12:20:50.968877 IP Browser.51247 > Doorbell.80: Flags [.], ack 367, win 1022, length 0
12:20:50.968896 IP Browser.51247 > Doorbell.80: Flags [F.], seq 354, ack 367, win 1022, length 0
>>> FAIL!! <<<
12:20:50.968918 IP Browser.51248 > Doorbell.80: Flags [P.], seq 1:281, ack 1, win 1024, length 280: HTTP: GET /css/merge.css HTTP/1.1
12:20:50.968970 IP Browser.51249 > Doorbell.80: Flags [S], seq 2381475726, win 65535, options [mss 8960,nop,wscale 8,nop,nop,sackOK], length 0
12:20:50.989502 IP Doorbell.80 > Browser.51247: Flags [.], ack 355, win 490, length 0
12:20:50.989528 IP Doorbell.80 > Browser.51248: Flags [.], ack 281, win 490, length 0
12:20:50.989548 IP Doorbell.80 > Browser.51249: Flags [S.], seq 3516705722, ack 2381475727, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
12:20:50.991111 IP Doorbell.80 > Browser.51248: Flags [P.], seq 1:278, ack 281, win 490, length 277: HTTP: HTTP/1.1 404 Not Found
12:20:50.991137 IP Doorbell.80 > Browser.51248: Flags [F.], seq 278, ack 281, win 490, length 0
12:20:50.992109 IP Browser.51249 > Doorbell.80: Flags [.], ack 1, win 1024, length 0
>>> FAIL!! <<<
12:20:50.992131 IP Browser.51249 > Doorbell.80: Flags [P.], seq 1:299, ack 1, win 1024, length 298: HTTP: GET /js/merge.js HTTP/1.1
12:20:50.999271 IP Doorbell.80 > Browser.51249: Flags [.], ack 299, win 490, length 0
12:20:50.999296 IP Doorbell.80 > Browser.51249: Flags [P.], seq 1:278, ack 299, win 490, length 277: HTTP: HTTP/1.1 404 Not Found
12:20:50.999316 IP Doorbell.80 > Browser.51249: Flags [F.], seq 278, ack 299, win 490, length 0
12:20:51.008004 IP Browser.51248 > Doorbell.80: Flags [.], ack 278, win 1022, length 0
12:20:51.008027 IP Browser.51248 > Doorbell.80: Flags [F.], seq 281, ack 278, win 1022, length 0
12:20:51.008046 IP Browser.51248 > Doorbell.80: Flags [.], ack 279, win 1022, length 0
12:20:51.011847 IP Browser.51249 > Doorbell.80: Flags [.], ack 278, win 1022, length 0
12:20:51.011871 IP Browser.51249 > Doorbell.80: Flags [F.], seq 299, ack 278, win 1022, length 0
12:20:51.011890 IP Browser.51249 > Doorbell.80: Flags [.], ack 279, win 1022, length 0
12:20:51.042024 IP Doorbell.80 > Browser.51248: Flags [.], ack 282, win 490, length 0
12:20:51.042047 IP Doorbell.80 > Browser.51249: Flags [.], ack 300, win 490, length 0
Mike
12:20:50.918441 IP Browser.51247 > Doorbell.80: Flags [S], seq 2473268772, win 65535, options [mss 8960,nop,wscale 8,nop,nop,sackOK], length 0
12:20:50.918481 IP Browser.51248 > Doorbell.80: Flags [S], seq 1040465456, win 65535, options [mss 8960,nop,wscale 8,nop,nop,sackOK], length 0
12:20:50.927233 IP Doorbell.80 > Browser.51247: Flags [S.], seq 553246320, ack 2473268773, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
12:20:50.927261 IP Doorbell.80 > Browser.51248: Flags [S.], seq 2666843614, ack 1040465457, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
12:20:50.933493 IP Browser.51247 > Doorbell.80: Flags [.], ack 1, win 1024, length 0
12:20:50.933517 IP Browser.51247 > Doorbell.80: Flags [P.], seq 1:354, ack 1, win 1024, length 353: HTTP: GET / HTTP/1.1
12:20:50.933536 IP Browser.51248 > Doorbell.80: Flags [.], ack 1, win 1024, length 0
12:20:50.957262 IP Doorbell.80 > Browser.51247: Flags [.], ack 354, win 490, length 0
12:20:50.960927 IP Doorbell.80 > Browser.51247: Flags [P.], seq 1:366, ack 354, win 490, length 365: HTTP: HTTP/1.1 304 not modified
12:20:50.960951 IP Doorbell.80 > Browser.51247: Flags [F.], seq 366, ack 354, win 490, length 0
12:20:50.968853 IP Browser.51247 > Doorbell.80: Flags [.], ack 366, win 1022, length 0
12:20:50.968877 IP Browser.51247 > Doorbell.80: Flags [.], ack 367, win 1022, length 0
12:20:50.968896 IP Browser.51247 > Doorbell.80: Flags [F.], seq 354, ack 367, win 1022, length 0
>>> FAIL!! <<<
12:20:50.968918 IP Browser.51248 > Doorbell.80: Flags [P.], seq 1:281, ack 1, win 1024, length 280: HTTP: GET /css/merge.css HTTP/1.1
12:20:50.968970 IP Browser.51249 > Doorbell.80: Flags [S], seq 2381475726, win 65535, options [mss 8960,nop,wscale 8,nop,nop,sackOK], length 0
12:20:50.989502 IP Doorbell.80 > Browser.51247: Flags [.], ack 355, win 490, length 0
12:20:50.989528 IP Doorbell.80 > Browser.51248: Flags [.], ack 281, win 490, length 0
12:20:50.989548 IP Doorbell.80 > Browser.51249: Flags [S.], seq 3516705722, ack 2381475727, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 5], length 0
12:20:50.991111 IP Doorbell.80 > Browser.51248: Flags [P.], seq 1:278, ack 281, win 490, length 277: HTTP: HTTP/1.1 404 Not Found
12:20:50.991137 IP Doorbell.80 > Browser.51248: Flags [F.], seq 278, ack 281, win 490, length 0
12:20:50.992109 IP Browser.51249 > Doorbell.80: Flags [.], ack 1, win 1024, length 0
>>> FAIL!! <<<
12:20:50.992131 IP Browser.51249 > Doorbell.80: Flags [P.], seq 1:299, ack 1, win 1024, length 298: HTTP: GET /js/merge.js HTTP/1.1
12:20:50.999271 IP Doorbell.80 > Browser.51249: Flags [.], ack 299, win 490, length 0
12:20:50.999296 IP Doorbell.80 > Browser.51249: Flags [P.], seq 1:278, ack 299, win 490, length 277: HTTP: HTTP/1.1 404 Not Found
12:20:50.999316 IP Doorbell.80 > Browser.51249: Flags [F.], seq 278, ack 299, win 490, length 0
12:20:51.008004 IP Browser.51248 > Doorbell.80: Flags [.], ack 278, win 1022, length 0
12:20:51.008027 IP Browser.51248 > Doorbell.80: Flags [F.], seq 281, ack 278, win 1022, length 0
12:20:51.008046 IP Browser.51248 > Doorbell.80: Flags [.], ack 279, win 1022, length 0
12:20:51.011847 IP Browser.51249 > Doorbell.80: Flags [.], ack 278, win 1022, length 0
12:20:51.011871 IP Browser.51249 > Doorbell.80: Flags [F.], seq 299, ack 278, win 1022, length 0
12:20:51.011890 IP Browser.51249 > Doorbell.80: Flags [.], ack 279, win 1022, length 0
12:20:51.042024 IP Doorbell.80 > Browser.51248: Flags [.], ack 282, win 490, length 0
12:20:51.042047 IP Doorbell.80 > Browser.51249: Flags [.], ack 300, win 490, length 0
-
- Posts: 6
- Joined: Thu Jun 30, 2022 10:40 am
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
I can confirm the missing "merge.js" and "merge.css" also affects Doorbell AD410. App says firmware is up to date.
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
I too am having this same issue with the Amcrest AD410. The browser network tools clearly show that the camera isn't serving the merge.css or merge.js files.
Re: IP8M-2496EB-40MM - Web UI started displaying blank page
I can confirm that two years later, the AD410 still has nonfunctional web UI on all major browsers (Chrome-based browsers, Safari, and Firefox). This is the latest firmware available.
This severely breaks the functionality of this camera. Please make fixing this a top priority.
This severely breaks the functionality of this camera. Please make fixing this a top priority.