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

Authentication Error even when new token

Support
16
44
1.9k
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
    sheminasalam1 last edited by Sep 5, 2024, 7:14 AM

    I reinstalled my raspberry pi with the new bookworm OS today. After that I installed the arm 64 of this gateway. It installed without issues and also couldn’t see any errors with tail but now when I check I get the following error.

    I have checked the token file, it is there in etc/monocle also i deleted new token and added fresh but same error. help me what to do?

    S 1 Reply Last reply Sep 5, 2024, 7:25 AM Reply Quote 0
    • S
      sheminasalam1 @sheminasalam1 last edited by Sep 5, 2024, 7:25 AM

      @sheminasalam1

      This is the error

      Monocle API Authentication Error; invalid or missing token.
      
      1 Reply Last reply Reply Quote 0
      • R
        Rich last edited by Sep 5, 2024, 10:13 AM

        I am getting an error when trying to enable the Monocle skill via the Alexa app, this might be linked? @Monocle could you take a look, please?

        M 1 Reply Last reply Sep 5, 2024, 11:46 PM Reply Quote 2
        • F
          foz111 last edited by Sep 5, 2024, 11:50 AM

          Same problem here, this happened a while ago requires owner to fix from memory

          R 1 Reply Last reply Sep 5, 2024, 2:10 PM Reply Quote 0
          • R
            Rich @foz111 last edited by Sep 5, 2024, 2:10 PM

            @foz111 Yeah, an expired cert, IIRC?

            1 Reply Last reply Reply Quote 0
            • S
              SchmuFoo last edited by Sep 5, 2024, 6:13 PM

              Hi just came here to check if there are other users who are facing this API 401 Error out of nothing

              Sep 05 20:10:24 loxberry monocle-gateway[6382]: [RTSP Server Started]
              Sep 05 20:10:24 loxberry monocle-gateway[6382]: Monocle API Authentication Error; invalid or missing token.
              Sep 05 20:10:24 loxberry monocle-gateway[6382]: 2024-09-05T18:10:24.451Z [ERROR] [Monocle Error] Unexpected server response: 401
              Sep 05 20:10:24 loxberry monocle-gateway[6382]: [ '[Monocle Error]', 'Unexpected server response: 401' ]
              Sep 05 20:10:24 loxberry monocle-gateway[6382]: [Monocle Disconnected]
              Sep 05 20:10:24 loxberry monocle-gateway[6382]: [Monocle Reconnecting] ... in 5 seconds (attempt #1)
              
              
              1 Reply Last reply Reply Quote 1
              • M
                McKinley @Rich last edited by Sep 5, 2024, 11:46 PM

                @Rich, I am having the same issue with account linking with Amazon Alexa - was working just fine until sometime this morning.

                I checked my gateways logs - everything there seems fine - no api token error.

                1 Reply Last reply Reply Quote 0
                • P
                  pathfinder last edited by Sep 6, 2024, 3:48 AM

                  I am also receiving the “Monocle API Authentication Error; invalid or missing token.” error.

                  1 Reply Last reply Reply Quote 0
                  • Monocle
                    Monocle last edited by Sep 6, 2024, 1:36 PM

                    FYI … Working on this issue now and it should be resolved and working again later today!

                    Thanks, Robert

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

                    A 1 Reply Last reply Sep 10, 2024, 8:20 PM Reply Quote 2
                    • A
                      Anundertaker @Monocle last edited by Sep 10, 2024, 8:20 PM

                      @Monocle Hi Robert,

                      Just got “Monocle API Authentication Error; invalid or missing token.” recurring, as of about the last couple of hours.

                      Thank you for your help with this.

                      1 Reply Last reply Reply Quote 1
                      • N
                        nor1don last edited by Sep 10, 2024, 9:35 PM

                        I am having the same error… I changed token but still the same issue.

                        Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: 2024-09-10T21:27:03.441Z [ERROR] [Monocle Error] Unexpected server response: 401
                        Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
                        Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: [Monocle Disconnected]
                        Sep 11 00:27:03 raspberrypi monocle-gateway[11159]: [Monocle Reconnecting] … in 23 seconds (attempt #4)
                        Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [Monocle Connecting]
                        Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: Monocle API Authentication Error; invalid or missing token.
                        Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: 2024-09-10T21:27:26.909Z [ERROR] [Monocle Error] Unexpected server response: 401
                        Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
                        Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [Monocle Disconnected]
                        Sep 11 00:27:26 raspberrypi monocle-gateway[11159]: [Monocle Reconnecting] … in 25 seconds (attempt #5)

                        1 Reply Last reply Reply Quote 0
                        • J
                          justincheger last edited by Sep 11, 2024, 12:52 AM

                          I am getting the same error on windows.

                          [Monocle Connecting]
                          Monocle API Authentication Error; invalid or missing token.
                          2024-09-11T00:52:07.365Z [ERROR] [Monocle Error] Unexpected server response: 401
                          [ ‘[Monocle Error]’, ‘Unexpected server response: 401’ ]
                          [Monocle Disconnected]

                          1 Reply Last reply Reply Quote 1
                          • D
                            deepbluesee last edited by Sep 11, 2024, 1:21 PM

                            Same error today i Changed nothing
                            Solution?

                            1 Reply Last reply Reply Quote 1
                            • F
                              foz111 last edited by Sep 11, 2024, 1:52 PM

                              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 Sep 11, 2024, 2:43 PM

                                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 Sep 11, 2024, 3:05 PM

                                  @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 Sep 11, 2024, 3:59 PM

                                    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 Sep 11, 2024, 5:22 PM Reply Quote 1
                                    • D
                                      deepbluesee @Monocle last edited by Sep 11, 2024, 4:47 PM

                                      @Monocle
                                      Yes works again without any problems
                                      Thanks

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        SchmuFoo @Monocle last edited by Sep 11, 2024, 5:22 PM

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

                                        Monocle 1 Reply Last reply Sep 12, 2024, 2:43 AM Reply Quote 0
                                        • J
                                          justincheger last edited by Monocle Sep 12, 2024, 2:38 AM Sep 11, 2024, 10:29 PM

                                          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
                                          7 out of 44
                                          • First post
                                            7/44
                                            Last post
                                          Privacy Policy  |  Terms & Conditions

                                          © 2018 shadeBlue, LLC.