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 11.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.
    • bheplerB Offline
      bhepler Module Developer @AnyKey
      last edited by

      @AnyKey Heh. I’ve been there.
      First, you’ll need to be sure that the config.js file exists. A manual installation generally does not copy the sample file into the final destination, so you’ll need to do it yourself. From the MagicMirror folder, cp config/config.js.sample config/config.js should put the file in the proper place. At that point, it’s ready for editing.

      The Unix-like system that the Diskstation uses must have an editor of some form on there. If not nano, then VIM or VI. From the MagicMirror directory, you should be able to type nano config/config.js or vi config/config.js and open up the config file.

      Absolute worst case scenario: you can copy & paste the config.js contents from your desktop machine to the file via PuTTY. Have the config file open on your desktop, select all, copy to clipboard. In the PuTTY window, navigate to the MagicMirror/config folder and enter cat > config.js and then press enter. At this point, everything you type will be in the file… so just right-click with your mouse to paste the clipboard into the file. When it finishes, hit enter one more time and the ctrl+d (control D). That will save the contents.

      A 1 Reply Last reply Reply Quote 0
      • A Offline
        AnyKey @bhepler
        last edited by

        @bhepler The config.js didn’t existed after the install process, so I copied it, like you mentioned. The real stungle was to find an editor to open and edit the config file. Nano is not supported, that was the first (and only editor) editor I’ve tried. When I’m home, I will test your other suggestions.

        brobergB 1 Reply Last reply Reply Quote 0
        • brobergB Offline
          broberg Project Sponsor @AnyKey
          last edited by

          @AnyKey any text editor will be able to read .js files.

          1 Reply Last reply Reply Quote 0
          • yawnsY Offline
            yawns Moderator
            last edited by

            according to the synology wiki:

            ipkg update; ipkg install nano

            1 Reply Last reply Reply Quote 1
            • A Offline
              AnyKey
              last edited by

              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

              bheplerB A 2 Replies Last reply Reply Quote 0
              • bheplerB Offline
                bhepler Module Developer @AnyKey
                last edited by

                @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

                  @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