Navigation

    Home
    All Categories
    • KEEN Trail Camera
    • Top #ReolinkCaptures Awards
    • Announcements and News
    • Wishlist
    • #ReolinkTrial
    • Discussion About Products
    • Reolink Captures
    • Reolink Client & APP
    #ReolinkTrial
    Reolink Captures
    Log in to post
    Guest
    • Guest
    • Register
    • Login

    Learn More

    Reolink updates Learn More

    Meet Reolink at IFA 2024! Learn More

    Reolink Q&A Learn More

    api.cgi seems crashed on Reolink Duo Floodlight WiFi v2

    Discussion About Products
    2
    4
    53
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • user_969250755113203_969250755113203
      user_969250755113203 last edited by

      This is the hard wired version of the Reolink Duo Floodlight WiFi v2 and my second camera after exchanging the first one for the same problem. I have HTTP enabled and the web interface loads fine. When I try to login, I get a 502 Bad Gateway (see attached).

      Same issue using curl directly:

      $ curl -v -H 'Content-Type: application/json' http://192.168.50.14/cgi-bin/api.cgi?cmd=Logi
      n --data-raw '[{"cmd":"Login","action":0,"param":{"Version":1}}]'
      *  Trying 192.168.50.14:80...
      * Connected to 192.168.50.14 (192.168.50.14) port 80 (#0)
      > POST /cgi-bin/api.cgi?cmd=Login HTTP/1.1
      > Host: 192.168.50.14
      > User-Agent: curl/7.81.0
      > Accept: */*
      > Content-Type: application/json
      > Content-Length: 50
      >
      * Mark bundle as not supporting multiuse
      < HTTP/1.1 502 Bad Gateway
      < Date: Tue, 01 Jul 2025 11:40:10 GMT
      < Content-Type: text/html
      < Content-Length: 166
      < Connection: keep-alive
      <
      <html>
      <head><title>502 Bad Gateway</title></head>
      <body bgcolor="white">
      <center><h1>502 Bad Gateway</h1></center>
      <hr><center>nginx</center>
      </body>
      </html>


      This is right after initial setup and with HTTP enabled - same issue with HTTPS. I've tried hard reset and various other settings. Any have the same issue on this model?

      I checked and there is no firmware listed on Reolink for this Hardware No: IPC_NT7NA58MP

      Build No: build 2412101858
      Firmware Version: v3.0.0.4410_2412101858

      Reply Quote
      Share
      • Share this Post
      • Facebook
      • Twitter
      • copy the link
        Copied!
      0
        • joseph_1979
          Joseph Global Moderator @user_969250755113203 last edited by

          @user_969250755113203_969250755113203 And if you try this command what do you get?

          curl -s -k -X POST -H "Content-Type : application/json" -d "[{\"cmd\":\"GetAbility\",\"param\":{\"User\":{\"userName\":\"admin\"}}}]" "https://192.168.50.14/cgi-bin/api.cgi?cmd=GetAbility&user=admin&password=#PASSWORD"

          Change #PASSWORD with your password.

          Reply Quote
          Share
          • Share this Post
          • Facebook
          • Twitter
          • copy the link
            Copied!
          0
          • user_969250755113203_969250755113203
            user_969250755113203 @Joseph last edited by

            @joseph_1979 It is the same response unfortunately. It doesn't seem like this backend service is up. Also, I can only reply once per day for some reason.

            $ curl -v -s -k -X POST -H "Content-Type : application/json" -d "[{\"cmd\":\"GetAbility\",\"param\":{\"User\":{\"userName\":\"admin\"}}}]" "http://192.168.50.14/cgi-bin/api.cgi?cmd=GetAbility&user=admin&password=***REMOVED***"
            *   Trying 192.168.50.14:80...
            * Connected to 192.168.50.14 (192.168.50.14) port 80 (#0)
            > POST /cgi-bin/api.cgi?cmd=GetAbility&user=admin&password=***REMOVED*** HTTP/1.1
            > Host: 192.168.50.14
            > User-Agent: curl/7.81.0
            > Accept: */*
            > Content-Type : application/json
            > Content-Length: 60
            > Content-Type: application/x-www-form-urlencoded
            >
            * Mark bundle as not supporting multiuse
            < HTTP/1.1 502 Bad Gateway
            < Date: Wed, 02 Jul 2025 17:46:49 GMT
            < Content-Type: text/html
            < Content-Length: 166
            < Connection: keep-alive
            <
            <html>
            <head><title>502 Bad Gateway</title></head>
            <body bgcolor="white">
            <center><h1>502 Bad Gateway</h1></center>
            <hr><center>nginx</center>
            </body>
            </html>
            * Connection #0 to host 192.168.50.14 left intact
            
            
            
            Reply Quote
            Share
            • Share this Post
            • Facebook
            • Twitter
            • copy the link
              Copied!
            0
            View 1 replies
          • First post
            Last post
          All Categories
          Announcements and News Reolink Client & APP Discussion About Products #ReolinkTrial Reolink Captures Wishlist KEEN Trail Camera
          Never miss Reolink hot deals, news, and updates tailored for you.

          Thanks for your subscription!

          Please enter a valid email address.

          Oops… Something went wrong. Please try again later.

          You are already subscribed to this email list. :)

          Submission failed. Please try again later.

          Reolink Store|Support|About Us|Privacy Policy|Terms and Conditions

          Copyright 2025 © Reolink All Rights Reserved.

          Welcome Back!

          Hi there! Join the Commnunity to get all the latest news, tips and more!

          Join Now