• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Authentication Error even when new token

    Support
    16
    44
    1679
    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.
    • D
      deepbluesee last edited by

      Same error today i Changed nothing
      Solution?

      1 Reply Last reply Reply Quote 1
      • F
        foz111 last edited by

        This was fixed but now seems to be broken again as the posts above suggest

        1 Reply Last reply Reply Quote 1
        • N
          nor1don last edited by

          We wait for Developers to fix the issue. I hope they fix it soon. It has been a life saver solution to me.

          1 Reply Last reply Reply Quote 0
          • T
            Toto last edited by

            @Robääääärrrtttt
            your help is very welcome again :-)

            Thank you in advance

            Best
            Toto

            1 Reply Last reply Reply Quote 0
            • Monocle
              Monocle last edited by

              Try it again now.

              I think I see the underlying issue and will need to put in a more permanent fix but it should be working now.

              Thanks, Robert

              Monocle: https://monoclecam.com
              Getting Started | Troubleshooting Guide | FAQ | Contact Support

              D S 2 Replies Last reply Reply Quote 1
              • D
                deepbluesee @Monocle last edited by

                @Monocle
                Yes works again without any problems
                Thanks

                1 Reply Last reply Reply Quote 0
                • S
                  SchmuFoo @Monocle last edited by

                  @Monocle Indeed after an daemon stop/start it is working again, Thank you very much

                  Monocle 1 Reply Last reply Reply Quote 0
                  • J
                    justincheger last edited by Monocle

                    I am still getting an error below, any help would be great

                    Windows Machine

                    2024-09-11T22:28:11.079Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:8555
                    [
                      '[PROXY SERVER ERROR]',
                      Error: listen EADDRINUSE: address already in use 0.0.0.0:8555
                          at Server.setupListenHandle [as _listen2] (node:net:1319:16)
                          at listenInCluster (node:net:1367:12)
                          at doListen (node:net:1505:7)
                          at processTicksAndRejections (node:internal/process/task_queues:84:21)
                          at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:65:3)
                          at Function.runMain (pkg/prelude/bootstrap.js:1848:13)
                          at node:internal/main/run_main_module:17:47 {
                        code: 'EADDRINUSE',
                        errno: -4091,
                        syscall: 'listen',
                        address: '0.0.0.0',
                        port: 8555
                      }
                    ]
                    2024-09-11T22:28:11.083Z [ERROR] [RTSP Server Error] listen EADDRINUSE: address already in use 0.0.0.0:8555
                    [
                      '[RTSP Server Error]',
                      'listen EADDRINUSE: address already in use 0.0.0.0:8555'
                    ]
                    2024-09-11T22:28:11.083Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:443
                    [
                      '[PROXY SERVER ERROR]',
                      Error: listen EADDRINUSE: address already in use 0.0.0.0:443
                          at Server.setupListenHandle [as _listen2] (node:net:1319:16)
                          at listenInCluster (node:net:1367:12)
                          at doListen (node:net:1505:7)
                          at processTicksAndRejections (node:internal/process/task_queues:84:21)
                          at process.runNextTicks [as _tickCallback] (node:internal/process/task_queues:65:3)
                          at Function.runMain (pkg/prelude/bootstrap.js:1848:13)
                          at node:internal/main/run_main_module:17:47 {
                        code: 'EADDRINUSE',
                        errno: -4091,
                        syscall: 'listen',
                        address: '0.0.0.0',
                        port: 443
                      }
                    ]
                    2024-09-11T22:28:11.084Z [ERROR] [RTSP Server Error] listen EADDRINUSE: address already in use 0.0.0.0:443
                    [
                      '[RTSP Server Error]',
                      'listen EADDRINUSE: address already in use 0.0.0.0:443'
                    ]
                    
                    1 Reply Last reply Reply Quote 0
                    • Monocle
                      Monocle @SchmuFoo last edited by Monocle

                      @justincheger

                      This is a different error.

                      [RTSP Server Error] listen EADDRINUSE: address already in use 0.0.0.0:8555
                      ...
                      [PROXY SERVER ERROR] Error: listen EADDRINUSE: address already in use 0.0.0.0:443
                      

                      This is telling us that you probably already have an (second) instance of Monocle Gateway running. Probably in the background as a Windows service. Basically ports 443 and 8555 are already being used and the new instance cannot bind to those ports.

                      Try using this command to stop the background service first:
                      monocle-gateway.exe --stop

                      See this page for additional details:
                      https://monoclecam.com/monocle-gateway/install/windows#windows-service

                      Thanks, Robert

                      Monocle: https://monoclecam.com
                      Getting Started | Troubleshooting Guide | FAQ | Contact Support

                      S 1 Reply Last reply Reply Quote -1
                      • S
                        SchmuFoo @Monocle last edited by

                        @Monocle I think this feedback was for @justincheger

                        Monocle 1 Reply Last reply Reply Quote 0
                        • Monocle
                          Monocle @SchmuFoo last edited by

                          @SchmuFoo

                          You are correct. I updated the post. Thanks, Robert

                          Monocle: https://monoclecam.com
                          Getting Started | Troubleshooting Guide | FAQ | Contact Support

                          D 1 Reply Last reply Reply Quote 0
                          • D
                            deepbluesee @Monocle last edited by

                            @Monocle
                            Today Same error again

                            1 Reply Last reply Reply Quote 0
                            • S
                              slime-uk last edited by slime-uk

                              Getting a 401 again today - anyone else? Thanks

                              Oct 01 09:15:54 pimonoclerp3 monocle-gateway[597]: [Monocle Connecting]

                              Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: Monocle API Authentication Error; invalid or missing token.
                              Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: 2024-10-01T08:15:55.115Z [ERROR] [Monocle Error] Unexpected server response: 401
                              Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
                              Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: [Monocle Disconnected]
                              Oct 01 09:15:55 pimonoclerp3 monocle-gateway[597]: [Monocle Reconnecting] … in 64 seconds (attempt #12)

                              S M A 3 Replies Last reply Reply Quote 2
                              • S
                                SchmuFoo @slime-uk last edited by

                                @slime-uk said in Authentication Error even when new token:

                                Getting a 401 again today - anyone else? Thanks

                                Indeed

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  McKinley @slime-uk last edited by

                                  @slime-uk @admin @Monocle

                                  Same auth/API token error - Disconnected from monocle server on 9/30

                                  Tried going to website+forums and received a cloudflare error saying possible load balancing is needed.

                                  • not sure if they are related

                                  Thank you

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mp101 @SchmuFoo last edited by

                                    @SchmuFoo yup started yesterday afternoon uk for me

                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      Anundertaker @slime-uk last edited by

                                      @slime-uk same here

                                      @admin @Monocle - thanks!

                                      1 Reply Last reply Reply Quote 0
                                      • V
                                        Vicore last edited by

                                        It looks like the same issues as before, if you log out of the skill in Alexa you can not log back in and get a “login failed” please contact support banner. I assume it is a cert that needs updating. @Monocle

                                        1 Reply Last reply Reply Quote 2
                                        • M
                                          memarkham303 last edited by

                                          @Monocle I’m in the same boat. Rats.

                                          Monocle 1 Reply Last reply Reply Quote 0
                                          • Monocle
                                            Monocle @memarkham303 last edited by

                                            @ALL

                                            Please try again. Not a certificate issue this time – just a temporary database server outage yesterday and one of the services that makeup the backend failed to reconnect. Added improved “reconnect” logic today so hopefully this issue will “self-heal” next time.

                                            (In some cases, you may have to restart your Monocle Gateway service.)

                                            Thanks, Robert

                                            Monocle: https://monoclecam.com
                                            Getting Started | Troubleshooting Guide | FAQ | Contact Support

                                            M A M 3 Replies Last reply Reply Quote 3
                                            • First post
                                              Last post
                                            Privacy Policy  |  Terms & Conditions

                                            © 2018 shadeBlue, LLC.