1. Home
  2. Troubleshooting
  3. Error performing TLS handshake: An unexpected TLS packet was received
MagicMirror² v2.14.0 is available! For more information about this release, check out this topic.

Error performing TLS handshake: An unexpected TLS packet was received

  • K

    Hi all,
    I am trying to set Magic Mirror 2 up on my Pi Zero W following Emmanuel Contreras’s guide found here http://emmanuelcontreras.com/how-to/how-to-create-a-magic-mirror-2-with-pi-zero-w/. I followed the instructions up until making the two start scripts, where I deviated slightly and used midori instead of chromium as in this guide https://www.magicmirrorcentral.com/magic-mirror-raspberry-pi-zero/. When I restart my Pi, Midori opens but gives me a “Error- https://localhost:8080 Error performing TLS handshake: An unexpected TLS packet was received” message. Does anyone have a solution to this? I don’t seem to be getting any errors in the console, and accessing the Mirror from my PC’s web browser opens it correctly, so it is an issue with Midori.

    0 S 1 Reply
  • K

    @sdetweil Ahh, that did it. Reverted the run-start.sh script and switched to Graphical auto-login mode and that did the trick. Thank you for your help!

    0 S 1 Reply
  • S

    @Keudn I don’t know. But I would try the updated installer.

    See here
    https://forum.magicmirror.builders/topic/10171/anyone-want-to-try-updated-installer

    0 K 1 Reply
  • K

    @sdetweil I’m not sure how to use it, do I just run the command?

    0 S 1 Reply
  • S

    @Keudn rename the MagicMirror folder to something else and then run the command.

    it will do all the work…
    (this is just an updated version of the same command in the MM readme and on the github site)

    it will prompt if u want to use pm2 to autostart at boot
    and ask if u want to turn off screen saver

    0 K 1 Reply
  • K

    @sdetweil I renamed the old Magic Mirror folder and ran the command. It seemed to install correctly, but when it boots I get a “Please create a config file” message even though I copied the one I had from the old folder over and installed the modules again. I am also still getting the Midori error first, so it seems like the previous install is still trying to start.

    0 S 1 Reply
  • S

    @Keudn do a
    pm2 status
    Command. Check the paths and commands

    My setup starts chrome for the browser on pi 0.

    For the config, run

    npm check:config

    From the MagicMirror folder.

    If that is ok
    Then do npm start to see any node_helper errors

    0 K 1 Reply
  • K

    @sdetweil pm2 status gives me two ids, MagicMirror and mmstart. I’m assuming MagicMirror is the one your script creates. When I try and run pm2 stop I just get “Process not found” error and can’t actually disable it.

    Running npm check:config doesn’t seem to be a valid command as it gives me a usage list and asks if I meant “config”.

    Doing npm start gives this output

    $ npm start

> magicmirror@2.10.0-develop start /home/pi/MagicMirror
> ./run-start.sh

0 [LOG] Starting MagicMirror: v2.10.0-develop
0 [LOG] Loading config ...
[21:27:45.455] [ERROR]  WARNING! Could not validate config file. Starting with default configuration. Please correct syntax errors at or above this line: /home/pi/MagicMirror/config/config.js:87
*               {
^

SyntaxError: Unexpected token *
    at Module._compile (internal/modules/cjs/loader.js:721:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at loadConfig (/home/pi/MagicMirror/js/app.js:67:12)
    at App.start (/home/pi/MagicMirror/js/app.js:208:3)
    at Object. (/home/pi/MagicMirror/serveronly/index.js:2:5)
[21:27:45.484] [LOG] Loading module helpers ...
[21:27:45.825] [LOG] Initializing new module helper ...
[21:27:45.836] [LOG] Module helper loaded: updatenotification
[21:27:45.853] [LOG] No helper found for module: helloworld.
0 [LOG] All module helpers loaded.
[21:27:45.871] [LOG] Starting server on port 8080 ...
0 [LOG] Server started ...
0 [LOG] Connecting socket for: updatenotification
0 [LOG] Sockets connected & modules started ...
0 [LOG]
Ready to go! Please point your browser to: http://localhost:8080
Starting chromium browser now, have patience, it takes a minute
[21:27:46.284] [ERROR]  { Error: listen EADDRINUSE: address already in use 127.0.0.1:8080
    at Server.setupListenHandle [as _listen2] (net.js:1279:14)
    at listenInCluster (net.js:1327:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1460:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 8080 }
Created new window in existing browser session.
    0 S 1 Reply
  • S

    @Keudn pm2 stop 0 or 1 ( or use there name)
    pm2 delete 0 or 1

    Edit the config and fix line 86 with that *

    0 K 1 Reply
  • K

    @sdetweil Got the mmstart process deleted, but now the mirror hangs at the booting up screen with the command line on the top. I can access it correctly from a browser on another computer, so it looks like it just isn’t opening a web browser locally on the Pi.

    0 S 1 Reply
  • S

    @Keudn the new run-start.sh script is waiting for the server process to say its ready
    then it starts the browser

    u should be able to test it

    ~/MagicMirror
bash -x run-start.sh

    starts mm in serveronly mode (on pi 0)

    loops reading console output, waiting for the message
    “point\ your\ browser”
    then launches chromium-browser

    but if that message doesn’t come… it will be hung…

    so, try

    ~/MagicMirror
node serveronly

    should look like this (with your module list)

    ~/MagicMirror$ node serveronly
[23:31:31.854] [LOG]    Starting MagicMirror: v2.10.0-develop
[23:31:31.865] [LOG]    Loading config ...
[23:31:31.871] [LOG]    Loading module helpers ...
[23:31:31.874] [LOG]    No helper found for module: alert.
[23:31:31.925] [LOG]    Initializing new module helper ...
[23:31:31.925] [LOG]    Module helper loaded: updatenotification
[23:31:31.927] [LOG]    No helper found for module: clock.
[23:31:31.928] [LOG]    No helper found for module: currentweather.
[23:31:31.929] [LOG]    No helper found for module: weatherforecast.
[23:31:32.508] [LOG]    Initializing new module helper ...
[23:31:32.509] [LOG]    Module helper loaded: newsfeed
[23:31:32.759] [LOG]    Initializing new module helper ...
[23:31:32.760] [LOG]    Module helper loaded: MMM-CalendarExt2
[23:31:32.771] [LOG]    handler helper in init
[23:31:32.772] [LOG]    Module helper loaded: ImageService
[23:31:34.273] [LOG]    scheduler helper in init
[23:31:34.273] [LOG]    Module helper loaded: ImageScheduler
[23:31:34.274] [LOG]    All module helpers loaded.
[23:31:34.275] [LOG]    Starting server on port 8080 ...
[23:31:34.281] [INFO]   You're using a full whitelist configuration to allow for all IPs
[23:31:34.288] [LOG]    Server started ...
[23:31:34.289] [LOG]    Connecting socket for: updatenotification
[23:31:34.290] [LOG]    Connecting socket for: newsfeed
[23:31:34.290] [LOG]    Starting module: newsfeed
[23:31:34.291] [LOG]    Connecting socket for: MMM-CalendarExt2
[23:31:34.291] [LOG]    Connecting socket for: ImageService
[23:31:34.292] [LOG]    handler helper in start
[23:31:34.292] [LOG]    Connecting socket for: ImageScheduler
[23:31:34.293] [LOG]    scheduler helper in start
[23:31:34.293] [LOG]    Sockets connected & modules started ...
[23:31:34.293] [LOG]
Ready to go! Please point your browser to: http://localhost:8080
    0 K 1 Reply
Log in to reply
 
Enjoying MagicMirror? Please consider a donation!