iotcreators.com web
    • Login
    • Search
    • forum.iotcreators.com
    • docs.iotcreators.com
    • Tags
    • Popular
    • Recent
    • Register

    Could not get any response

    Archive
    3
    10
    5285
    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.
    • E
      Elfred Nieuwamerongen van last edited by

      Trying to register my endpoint with Postman, but get this response
      Could not get any response
      There was an error connecting to %7B%7Bbase_url_cdp%7D%7D/impact/m2m/endpoints.
      Why this might have happened:
      The server couldn’t send a response:
      Ensure that the backend is working properly
      Self-signed SSL certificates are being blocked:
      Fix this by turning off ‘SSL certificate verification’ in Settings > General
      Proxy configured incorrectly
      Ensure that proxy is configured correctly in Settings > Proxy
      Request timeout:
      Change request timeout in Settings > General

      Checked the response of the endpoint with a HTTP client and it give an solid 200 response

      Which user-id and password do I have to give. Which group-name?

      A 1 Reply Last reply Reply Quote 0
      • A
        Andre Rodenburg @Elfred Nieuwamerongen van last edited by

        Hi Elfred.

        @elfred-nieuwamerongen-van said in Could not get any response:

        Which user-id and password do I have to give. Which group-name?

        Have you received the login from @Rowan-Schaaf ?

        1 Reply Last reply Reply Quote 0
        • E
          Elfred Nieuwamerongen van last edited by

          Yes I did. Of course, those are the ones.
          Further investigation brought me to the face that no SIM cards are registered on my account. I did sent an e-mail to migrate, but is that in proces, or didn’t it get through, wrong SIM’s? Appreciate your help
          Elfred

          1 Reply Last reply Reply Quote 0
          • afzal_m
            afzal_m iotcreators.com team last edited by

            Hi! I can confirm that your simcards are not the problem.

            Please have a check in Postman (right top) if the correct environment is selecties and also try to check if it helps when you switch on/off the ssl verification settings in Postman.

            1 Reply Last reply Reply Quote 0
            • E
              Elfred Nieuwamerongen van last edited by

              Unfortunately, same story here after switching ssl on and off.
              Right top of postman says: IOT Application TMNL Early Access program

              Body of Register Endpoint:
              { “additionalParams”: {
              “adaptationLayerName”:“{{adaptationLayerName}}”
              },
              “address”: “”,
              “groupName”: “{{group_name}}”,
              “identifier”: “”,
              “protocol”: “HTTP”,
              “serialNumber”: “{{DeviceId}}”
              }

              Any thoughts what to try next:
              Thanks

              1 Reply Last reply Reply Quote 0
              • E
                Elfred Nieuwamerongen van last edited by

                Ok, Need to have sk0002 in the top of Postman.
                Got other messages now, so we’re heading the right way

                A 1 Reply Last reply Reply Quote 0
                • A
                  Andre Rodenburg @Elfred Nieuwamerongen van last edited by

                  @elfred-nieuwamerongen-van said in Could not get any response:

                  Ok, Need to have sk0002 in the top of Postman.

                  This is very important yes, otherwise it will not work at all.

                  It should look like this:
                  alt text

                  1 Reply Last reply Reply Quote 0
                  • E
                    Elfred Nieuwamerongen van last edited by

                    Yes, thank you,
                    Message to get the registration working. The last error was because the content-type was not set to Json
                    Now troubleshooting why my device gives an error while sending a message.

                    A 1 Reply Last reply Reply Quote 0
                    • E
                      Elfred Nieuwamerongen van last edited by

                      It’s working, thanks for the support
                      Elfred

                      1 Reply Last reply Reply Quote 2
                      • A
                        Andre Rodenburg @Elfred Nieuwamerongen van last edited by

                        @elfred-nieuwamerongen-van You can enable extended error reporting with the command AT+CMEE=1.

                        1 Reply Last reply Reply Quote 1
                        • 1 / 1
                        • First post
                          Last post