Read the statement by Michael Teeuw here.
Trouble with non-broken "broken" images
-
@jedilkeme in the console tab, you might see a 404 error, not found
in the elements tab you can see the actual html used. -
@sdetweil no 404 errors or anything else that pops out at me…
-
@jedilkeme and if you look at the html for the image, it is as you expected. and if you use that url.i a browser, the image is displayed?
-
@sdetweil ah, it wasn’t showing errors because I had it written to load at 5am… I set it to run in one minute, and I did receive a 404 for the images, permissions are all groovy but I noticed I can’t view the images from localhost:8080/path-to-images in the browser, but if I just put in the file path in the address bar I can see the images… then I ran npm start dev and I found an EADDRINUSE error. Stumped. Thanks your you assistance so far!
-
@jedilkeme said in Trouble with non-broken "broken" images:
I ran npm start dev and I found an EADDRINUSE error
pm2 already has an instance running… only one at a time please on the same port
pm2 status to see what pm2 manages
pm2 --help
to see all the things it CAN do
pm2 stop name or row number or all
pm2 stop allthen you can do the npm start …
when u are happy , then ctrl-q or ctrl-c to stop the npm start and pm2 start or restart row or name
then on reboot it will come back up…pm2’s JOB is to keep its managed apps running…
-
@jedilkeme path to images
http://localhost:8080is the MagicMirror folder
so files in a module would be
http://localhost:8080/modules/modulename/xxx.jpg (or whatever) -
@sdetweil that was my issue, I had assumed :8080/ what my main directory… fixed it. Thanks a bunch!
