Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs

    smartConnect error

    General Discussion
    11
    33
    142
    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.
    • A
      admin @G25453 last edited by

      HI @G25453 @G25453 @garry07396 @pashriva @rishi @SawanKumar We have reported this issue we will update this soon.

      rishi 1 Reply Last reply Reply Quote 0
      • K
        kkt237 last edited by

        Issue is while fetching the public ip from https://bot.whatismyipaddress.com in SmartAPIRequestHandler.class

        Find a way to override or hard code your public ip for now.

        V G 2 Replies Last reply Reply Quote 0
        • V
          vvbchandrasekhar @rishi last edited by

          @admin tell your tech team to update the SSL certificate.

          @rishi Yes, I am having the same issue. This is due to the angel broking SSL certificate expiry date. NotAfter: Tue Aug 24 05:29:59 IST 2021

          Turning on ssl logs helped.

          Here is the stack trace
          Caused by: java.security.cert.CertificateExpiredException: NotAfter: Tue Aug 24 05:29:59 IST 2021
          at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:277)
          at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:677)
          at sun.security.provider.certpath.BasicChecker.verifyValidity(BasicChecker.java:190)
          at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144)
          at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
          ... 39 more}

          K 1 Reply Last reply Reply Quote 0
          • V
            vvbchandrasekhar @kkt237 last edited by

            @kkt237 i don't think this is the issue. please refer to ssl logs.

            K 1 Reply Last reply Reply Quote 0
            • K
              kkt237 @vvbchandrasekhar last edited by

              @vvbchandrasekhar I checked the certificate. Its valid till 31jan 2022.

              1 Reply Last reply Reply Quote 0
              • K
                kkt237 last edited by

                Expired cert is from https://bot.whatismyipaddress.com/ not from smart connect api.

                1 Reply Last reply Reply Quote 0
                • K
                  kkt237 @vvbchandrasekhar last edited by

                  @vvbchandrasekhar https://bot.whatismyipaddress.com/ has expired cert and that's why its failing.

                  V 1 Reply Last reply Reply Quote 0
                  • V
                    vvbchandrasekhar @kkt237 last edited by

                    @kkt237 got it. i tried -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true
                    but still they are not working. did you try something similar?

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kkt237 @vvbchandrasekhar last edited by

                      @vvbchandrasekhar It will not work as the ssl issue is thrown/checked with in the class file.

                      Did you import smartapi-java as a jar or as a source?

                      I tried importing the source and corrected the client code where it fetches the public ip.

                      V 1 Reply Last reply Reply Quote 0
                      • V
                        vvbchandrasekhar @kkt237 last edited by

                        @kkt237 did it work? I also checked out the code now of smart-connect-api from their github. will try to make changes to it if you think it helped you.

                        K 1 Reply Last reply Reply Quote 0
                        • G
                          G25453 @kkt237 last edited by

                          @kkt237 Hardcoding the public ip works.
                          String clientPublicIP = "10.21.13.45";
                          A temporary workaround for the moment

                          G 1 Reply Last reply Reply Quote 0
                          • G
                            garry07396 @G25453 last edited by

                            @G25453 i changed it to https://checkip.amazonaws.com/

                            K 1 Reply Last reply Reply Quote 0
                            • K
                              kkt237 @garry07396 last edited by

                              @garry07396 Yes. There are many as such. Good you found one from aws.

                              1 Reply Last reply Reply Quote 0
                              • K
                                kkt237 @vvbchandrasekhar last edited by

                                @vvbchandrasekhar It worked for me. Look at @garry07396 comment. You can use that url too

                                V 1 Reply Last reply Reply Quote 0
                                • V
                                  vvbchandrasekhar @kkt237 last edited by

                                  @kkt237 @garry07396 thanks a lot. will try in the interim.

                                  @admin please provide an ETA for the new jar.

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    admin @vvbchandrasekhar last edited by

                                    HI @vvbchandrasekhar Our team is working on it on priority once fixed we will update here.

                                    1 Reply Last reply Reply Quote 0
                                    • rishi
                                      rishi @admin last edited by

                                      @admin When can we expect the problem to be resolved. This is the second day without any trade 😞

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        admin @rishi last edited by admin

                                        HI @rishi This issue has been resolved kindly update us if you face any other issue.

                                        rishi 1 Reply Last reply Reply Quote 0
                                        • rishi
                                          rishi @admin last edited by

                                          @admin I am still facing the same error.

                                          rishi 1 Reply Last reply Reply Quote 0
                                          • rishi
                                            rishi @rishi last edited by

                                            @rishi As mentioned by garry I changed the url to
                                            https://checkip.amazonaws.com/
                                            and it works.

                                            rishi punit 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post