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.

    Problems with calender and Nextcloud

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    44 Posts 6 Posters 20.1k Views 6 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.
    • S Offline
      sdetweil @Pakmann
      last edited by

      @Pakmann just do wget nextcloud-url

      Sam

      How to add modules

      learning how to use browser developers window for css changes

      1 Reply Last reply Reply Quote 0
      • P Offline
        Pakmann
        last edited by

        looks like the direction to find the root cause is good.

        Get following response:

        GnuTLS: A TLS fatal alert has been received.
        GnuTLS: received alert [70]: Error in protocol version
        

        Now i remember, a few months ago i configure the nginx to TLS1.3. Maybe its not compatible with MM ?

        S 1 Reply Last reply Reply Quote 0
        • S Offline
          sdetweil @Pakmann
          last edited by

          @Pakmann wget is not MM, and it also fails

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • P Offline
            Pakmann
            last edited by

            hmm… each other devices are running:

            Phone, Tablet or try to download the ICS directly in a desktop browser. Should be sometink on the PI ?

            S 1 Reply Last reply Reply Quote 0
            • S Offline
              sdetweil @Pakmann
              last edited by

              @Pakmann where did u configure tls3? may have to do the same on pi

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              1 Reply Last reply Reply Quote 0
              • P Offline
                Pakmann
                last edited by

                nextcloud is hostet on a separate pi. here the nginx is configured for TLS1.3

                MM is on another PI.

                S 1 Reply Last reply Reply Quote 0
                • S Offline
                  sdetweil @Pakmann
                  last edited by

                  @Pakmann so the nginx system is the gateway… all things must speak tls3…
                  so you now need to config MM pi to peak tls3

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

                  P 1 Reply Last reply Reply Quote 0
                  • P Offline
                    Pakmann @sdetweil
                    last edited by

                    @sdetweil
                    Today i solved the problem regarding TLS1.3 connection. Wget is working fine and i can download the ICS data.
                    On MM side i have the same issue like before. No data is shown in calender. When i start the MM its still the same error message :-(

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      sdetweil @Pakmann
                      last edited by

                      @Pakmann looks like you will have to add a parameter to the launcher to enable tls 1.3

                      https://developer.ibm.com/blogs/migrating-to-tls13-in-nodejs/

                      my adding this to the script starting MM (either mm.sh or run-start.sh)

                      Enable TLS1.3 using CLI options
                      With Node.js 11.x or 10.x, you can use the --tls-max-v1.3 CLI option to enable TLS1.3 by default. It can be provided directly on the command line, or set in the environment with NODE_OPTIONS=–tls-max-v1.3. The option can also be specified to Node.js 12.x, even though its already the default.

                      export NODE_OPTIONS=--tls-max-v1.3
                      

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

                      P 1 Reply Last reply Reply Quote 0
                      • P Offline
                        Pakmann @sdetweil
                        last edited by Pakmann

                        @sdetweil
                        for a first try i set the option directly via termine and start MM. Same result like before - i got an error message for SSL.

                        pi@MagicMirror:~/MagicMirror $ NODE_OPTIONS=–tls-max-v1.3
                        pi@MagicMirror:~/MagicMirror $ npm start
                        

                        Anythink wrong here ? Any idea how i can check if the option was accepted correctly?

                        On buster stable nodejs 10.17.0 is availble. But i found the binaries for v12. Obviously after an update i have other problems :D Therefore its better with v10 so far

                        S 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 5
                        • 3 / 5
                        • 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