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

    Monocle Gateway throws Proxy error at startup on Win2012R2 Server [SOLVED]

    Support
    3
    39
    2922
    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.
    • spicymikey
      spicymikey last edited by

      If I figure out the root cause I will post it here for you and others.

      I actually don’t normally use the local IP. I just did that for testing. The goal is to be able to monitor the property from anywhere, not just inside the house.

      I just made a $50 donation on your home page as a thanks for staying with me on this one. Thanks again!

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

        @spicymikey

        Thank you for your generous support!

        Here are some other threads on support for Monocle Gateway across multiple homes (remote locations)

        • https://forum.monoclecam.com/topic/238/remote-alexa-fire-devices
        • https://forum.monoclecam.com/topic/232/can-monocle-gateway-work-from-a-2nd-house-with-appropriate-firewall-port-s-opened/6

        If you want to access camera’s via Alexa from remote locations, basically, you will want to use the public IP you had mentioned and allow Monocle Gateway to host on port 443 on that public IP. See my previous post in this thread for more details.

        Thanks, Robert

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

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

          Hey Robert,

          I have a followup issue I wanted to report. Maybe I should open another thread, but the camera fails to stream sometimes. it’s more than once in awhile. Pretty much 1 in 3. I can’t attach a text file. It says I don’t have enough privileges. I don’t want to just dump it in the post. Too much text but I have it here if you need it.

          The only thing I can say is that when it fails, the “end point” throws a 401 and “unauthorized”. The debugger is showing the IP address of the Echo Show 5, but not certain if that is the endpoint throwing the error. See below

          2019-07-27T16:24:20.675Z [DEBUG] [10.1.0.11:45270 <SyTnclcGH>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=1> (session=undefined)
          2019-07-27T16:24:20.679Z [TRACE] [10.1.0.11:45270 <SyTnclcGH>] [ENDPOINT RESPONSE] <-- [HEADERS] {
          “cseq”: “1”,
          “date”: “Sat, Jul 27 2019 16:24:16 GMT”,

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

            @spicymikey

            See if you can upload the log now. I adjusted some forum permissions.

            Thank, Robert

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

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

              @Monocle said in Monocle Gateway throws Proxy error at startup on Win2012R2 Server [SOLVED]:

              @spicymikey

              See if you can upload the log now. I adjusted some forum permissions.

              Thank, Robert

              Same error. “You do not have permissions for this action”

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

                @spicymikey

                Well, the settings look correct … maybe try logging out then back in. I’m too familiar with the forum admin yet so it could still be an issue on my side.

                Thanks, Robert

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

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

                  Here’s the log…

                  [0_1564258669283_EchoShow5_Reolink420_Success followed by failure.txt](Uploading 100%)

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

                    @Monocle
                    By the way, I think I understand what is happening, although not why it’s happening. The closing process is not resulting in a clean termination of everything. Maybe a connection is being left open, etc. The failures are occuring when I try to say “show camera” again right after closing it. Something i was doing a lot trying to test things. But if I wait 5 minutes, it seems to show the camera again reliably.

                    If this is a bug on the Amazon side then not much we can do about it, but if its a flaw in Monocle, hope that is a clue to help track it down.

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

                      @spicymikey
                      I don’t think the upload made it. If it won’t work, then you could also use Pastebin, I have used that service before then just copy the link to the forum thread:
                      https://pastebin.com/

                      Thanks, Robert

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

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

                        @spicymikey said in Monocle Gateway throws Proxy error at startup on Win2012R2 Server [SOLVED]:

                        @Monocle
                        By the way, I think I understand what is happening, although not why it’s happening. The closing process is not resulting in a clean termination of everything. Maybe a connection is being left open, etc. The failures are occuring when I try to say “show camera” again right after closing it. Something i was doing a lot trying to test things. But if I wait 5 minutes, it seems to show the camera again reliably.

                        If this is a bug on the Amazon side then not much we can do about it, but if its a flaw in Monocle, hope that is a clue to help track it down.

                        I have seen some camera’s behave this way. Are you using @tunnel or @proxy for this camera? @proxy will try to leave the connection open for a few minutes just in case a new request comes in for the stream.

                        Thanks, Robert

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

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

                          @Monocle
                          I’ve tried it with @proxy-tcp, and without it. I’m ALWAYS using @tunnel per the documentation on the website. I can mess around with different combos and see what happens

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

                            @spicymikey

                            If using one of the @proxy tags, then you can also combine that with @hangup to forcefully disconnect immediately with the Alexa device disconnects the TCP socket. However, @hangup has no impact on @tunnel connections.

                            I noticed on another thread you mentioned this was a Reolink camera. I have seen that behavior before on Reolink cameras. It could simply be some bug or issue with the camera itself. But yes, it only manifests when making back to back connections and seems to work fine under normal use when your only periodically ask for the stream.

                            Thanks, Robert

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

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

                              @Monocle said in Monocle Gateway throws Proxy error at startup on Win2012R2 Server [SOLVED]:

                              @spicymikey

                              If using one of the @proxy tags, then you can also combine that with @hangup to forcefully disconnect immediately with the Alexa device disconnects the TCP socket. However, @hangup has no impact on @tunnel connections.

                              I noticed on another thread you mentioned this was a Reolink camera. I have seen that behavior before on Reolink cameras. It could simply be some bug or issue with the camera itself. But yes, it only manifests when making back to back connections and seems to work fine under normal use when your only periodically ask for the stream.

                              Thanks, Robert

                              Thanks for the advice. I think adding the @hangup solved it. Is that documented anywhere? First I’ve heard about @hangup, but I may have missed it.

                              For me with the Echo Show 5, a Reolink RLC420, and the Monocle Gateway, changing to these tags worked to eliminate the problem. A few combinations worked, but the most minimalistic combo is what I will stay with

                              FROM: @ntpnow, @tunnel, @proxy-tcp

                              TO: @hangup, @proxy

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

                                @spicymikey

                                RE: @ntpnow, @tunnel, @proxy-tcp
                                You can only use one of these at a time: @tunnel, @proxy or @proxy-tcp. If you include multiple, I think @tunnel will win and other will be ignored.

                                FYI:
                                If your camera manufacture is set to “Reolink” then @ntpnow is not needed. We shove that tag at runtime automatically for Reolinks as they all seem to require it.

                                Is that documented anywhere? First I’ve heard about @hangup, but I may have missed it.

                                @hangup may not be documented yet, its one of the newer tags and only used in a handful of cases.

                                Thanks, Robert

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

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

                                  Thanks Robert. I have been testing it on and off for 30 minutes and its working like a charm. I know I thought this yesterday, but I think we got this now. If I discover anything else I’ll post something

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sasq last edited by

                                    For anyone else having the same Proxy Error starting on Windows Servers, i found that 443 was also being used by IIS. Stopping and disabling the “World Wide Web Publishing Service” service freed the port and allowed monocle gateway to run. Appreciate this may not be an option for everyone.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Privacy Policy  |  Terms & Conditions

                                    © 2018 shadeBlue, LLC.