MagicMirror² v2.13.0 is available! For more information about this release, check out this topic.

Something went wrong displaying this web page error



  • Everything has been running well for a few months, a couple of weekends ago I noticed a message on the screen informing me that updates were available so I did a git pull in the MagicMirror folder then npm install.

    Everything seemed to have gone well, but after about 15 minutes the screen gives me a “Something went wrong displaying this web page error”. If I use VNC to login in and reload the page everything loads, and I can also load the MagicMirror from other computers on my network but it always goes back to the same error after a period of time.

    I’m using a Pi Zero if that helps with any suggestions.



  • @kellogg76 is pm2 used to start mirror app?

    if so, pm2 logs --lines=100
    might show the error

    if u have modules that have a package.json file, they also needed an npm install done in their folders too…

    my upgrade script handles all that
    see here https://github.com/sdetweil/MagicMirror_scripts



  • @sdetweil said in Something went wrong displaying this web page error:

    pm2 logs --lines=100

    Your updater script doesn’t work on a Pi Zero.

    I’ll try running npm install in the three non default module folders.

    Thanks



  • @kellogg76 >Your updater script doesn’t work on a Pi Zero.

    say what? i have tested on pi 0, 3, 4, odroid, jetson nano, and mac.
    a bunch of folks have tested on all kinds of pi’s…

    show me the log, ~/MagicMirror/installers/upgrade.log

    just for clarity the , updater doesn’t do anything by default except test the upgrade

    if u want it to DO the upgrade, u have to add the parm at the end ‘apply’

    from https://github.com/sdetweil/MagicMirror_scripts

    it should handle all the work… and give you a trial run of all that…
    
    only applying changes if u request them
    
    give it a try this works on Mac as well
    
    bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
    
    no changes are made to the local repo or the working copy
    
    if you WANT to actually apply the changes do
    
    bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply
    


  • @sdetweil said in Something went wrong displaying this web page error:

    ~/MagicMirror/installers/upgrade.log

    Apologies, when I ran

    curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh | bash
    

    I stopped reading after “Sorry, your Pi is not supported”, I just re-ran it and see the bit about Pi Zero’s.

    The install log is as follows

    Upgrade started - Fri Jan 24 13:47:22 AST 2020
    system is Linux raspberrypi 4.19.75+ #1270 Tue Sep 24 18:38:54 BST 2019 armv6l GNU/Linux
    the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
    doing test run = true
    
    saving custom.css
    remote name = origin
    upgrading from version 2.10.1 to 2.10.1
    fetching latest revisions
    git fetch rc=0
    current branch = master
    On branch master
    Your branch is up to date with 'origin/master'.
    
    Changes not staged for commit:
      (use "git add ..." to update what will be committed)
      (use "git checkout -- ..." to discard changes in working directory)
    
            modified:   vendor/package-lock.json
    
    Untracked files:
      (use "git add ..." to include in what will be committed)
    
            css/save_custom.css
    
    no changes added to commit (use "git add" and/or "git commit -a")
    there are 1 local files that are different than the master repo
    
       vendor/package-lock.json
    
    save/restore files selection = n
    restoring vendor/package-lock.json from repo
    skipping restore for vendor/package-lock.json, doing test run
    test merge result rc='' , if empty, no conflicts
    skipping merge, only test run
    
    processing dependency changes for active modules with package.json files
    processing for module MMM-BackgroundSlideshow please wait
    ----------------------------------
    skipped processing for MMM-BackgroundSlideshow, doing test run
    processing complete for module MMM-BackgroundSlideshow
    processing for module MMM-DarkSkyForecast please wait
    ----------------------------------
    skipped processing for MMM-DarkSkyForecast, doing test run
    processing complete for module MMM-DarkSkyForecast
    processing for module mmm-suncalc please wait
    ----------------------------------
    skipped processing for mmm-suncalc, doing test run
    processing complete for module mmm-suncalc
    restoring custom.css
    removing git alias
    Upgrade ended - Fri Jan 24 13:48:09 AST 2020
    

    It doesn’t appear there are any updates to apply as far as i can tell.



  • @kellogg76 said in Something went wrong displaying this web page error:

    doing test run = true

    which means you didn’t add

    apply
    

    to the end to actually DO the upgrade
    like this

    bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply
    

    upgrading from version 2.10.1 to 2.10.1

    correct

    u can do force instead of apply to redo the upgrade

    like this

    bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
    


  • @sdetweil

    I’ll give it a try with the force option.

    Thanks



  • @sdetweil

    Unfortunately it doesn’t seem to have made any difference.



  • Ok, we/I made a change to how the mirror app starts on pi 0 or other armv6l systems.

    But I introduced a bug. Download the fixed run-start.sh like this

    cd ~/MagicMirror
    curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/run-start.sh > run-start.sh
    

    Then start the mirror app again



  • @sdetweil
    Still the same error after doing the above and then rebooting.


Log in to reply