• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

MagicMirror Servermode on Synology DS

Scheduled Pinned Locked Moved Tutorials
servermodesynologydiskstationwebserver
14 Posts 6 Posters 10.8k Views 7 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Y Offline
    yawns Moderator
    last edited by May 17, 2017, 2:12 PM

    according to the synology wiki:

    ipkg update; ipkg install nano

    1 Reply Last reply Reply Quote 1
    • A Offline
      AnyKey
      last edited by May 17, 2017, 5:13 PM

      Ok, i managed to edit the config.js file to a full whitelist with nano. To install nano I had to do

      sudo apt-get update
      sudo apt-get install nano
      

      After that, I run “node serveronly” in the MagicMirror folder and I got the following log:

      root@synology_gitlab:/home/git/gitlab/MagicMirror# node serveronly              
      Starting MagicMirror: v2.1.1                                                    
      Loading config ...                                                              
      Loading module helpers ...                                                      
      No helper found for module: alert.                                              
      Initializing new module helper ...                                              
      Module helper loaded: updatenotification                                        
      No helper found for module: clock.                                              
      Initializing new module helper ...                                              
      Module helper loaded: calendar                                                  
      No helper found for module: compliments.                                        
      No helper found for module: currentweather.                                     
      No helper found for module: weatherforecast.                                    
      Initializing new module helper ...                                              
      Module helper loaded: newsfeed                                                  
      All module helpers loaded.                                                      
      Starting server on port 8080 ...                                                
      Starting server op port 8080 ...                                                
      You're using a full whitelist configuration to allow for all IPs   
      Server started ...                                                              
      Connecting socket for: updatenotification                                       
      Connecting socket for: calendar                                                 
      Starting node helper for: calendar                                              
      Connecting socket for: newsfeed                                                 
      Starting module: newsfeed                                                       
      Sockets connected & modules started ...                                         
                                                                                      
      Ready to go! Please point your browser to: http://localhost:8080                
      Whoops! There was an uncaught exception...                                      
      { Error: listen EADDRINUSE :::8080                                              
          at Object.exports._errnoException (util.js:1033:11)                         
          at exports._exceptionWithHostPort (util.js:1056:20)                         
          at Server._listen2 (net.js:1270:14)                                         
          at listen (net.js:1306:10)                                                  
          at Server.listen (net.js:1397:7)                                            
          at new Server (/home/git/gitlab/MagicMirror/js/server.js:27:9)              
          at /home/git/gitlab/MagicMirror/js/app.js:219:18                            
          at loadNextModule (/home/git/gitlab/MagicMirror/js/app.js:168:5)            
          at /home/git/gitlab/MagicMirror/js/app.js:163:6                             
          at Class.loaded (/home/git/gitlab/MagicMirror/modules/node_modules/node_help
      er/index.js:19:3)                                                               
        code: 'EADDRINUSE',
        errno: 'EADDRINUSE',                                                          
        syscall: 'listen',                                                            
        address: '::',                                                                
        port: 8080 }                                                                  
      MagicMirror will not quit, but it might be a good idea to check why this happene
      d. Maybe no internet connection?                                                
      If you think this really is an issue, please open an issue on GitHub: https://gi
      thub.com/MichMich/MagicMirror/issues 
      

      But I don’t get a connection when opening “http://localhost:8080”.

      At this point, I come to the conclusion, that it will be much easier and less stressful to run the MM Server on my Pi3 (managed to install and configure it at work in three hours less). Besides that, the ressources need for running a MM container seems to be very high, working with ne Synology while running MM is a pain in the ***.

      From my point of view this topic can be closed. I’d like to thank everybody who participated and wanted to help me! You guys rock :-)
      sincerely yours Andre

      B A 2 Replies Last reply May 17, 2017, 6:07 PM Reply Quote 0
      • B Offline
        bhepler Module Developer @AnyKey
        last edited by May 17, 2017, 6:07 PM

        @AnyKey said in MagicMirror Servermode on Synology DS:

        EADDRINUSE

        This usually means that you already have the MagicMirror running and you have attempted to start the server again. You’ll need to kill that process before starting it up.
        Try ps ax | grep node and if you see the line 9589 pts/1 Sl+ 0:03 node serveronly or something similar, then the Mirror is already running.
        sudo kill -9 9589 (or whatever the process number listed is) will stop it.

        I’m sorry this has been so frustrating. You’re almost there.

        1 Reply Last reply Reply Quote 0
        • A Offline
          andreas-becker @AnyKey
          last edited by Jul 2, 2017, 12:28 PM

          @AnyKey try to change the port which is used by Magicmirror. The Diskstation seems to use port 8080 for something else.

          1 Reply Last reply Reply Quote 1
          • 1
          • 2
          • 2 / 2
          • First post
            Last post
          Enjoying MagicMirror? Please consider a donation!
          MagicMirror created by Michael Teeuw.
          Forum managed by Sam, technical setup by Karsten.
          This forum is using NodeBB as its core | Contributors
          Contact | Privacy Policy