Skip to content

axios: https request produce error with SSL #30

Open

Description

@VladislavAkulich

I've got the error when I executed tests, which used this client on Jenkins environment.

Error: write EPROTO 140597680499200:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../../vendor/node/deps/openssl/openssl/ssl/s23_clnt.c:797:

at axios.then.catch (/home/jenkins/workspace/test_e2e/<project-name>/test/node_modules/reportportal-client/lib/rest.js:27:23)
at <anonymous>:null:null

It look like the following issues with axios package: axios/axios#1680

Activity

  1. DzmitryHumianiuk commented on Mar 27, 2019

    @DzmitryHumianiuk
    Member

    @VladislavAkulich are you sure assigning it to me? )

  2. removed their assignment
    on Mar 27, 2019
  3. pinned this issue on Mar 27, 2019
  4. removed their assignment
    on Mar 27, 2019
  5. avarabyeu commented on Mar 27, 2019

    @avarabyeu
    Member
  6. BorisOsipov commented on Mar 27, 2019

    @BorisOsipov
    Contributor

    Have you tried to google smth before submiting issue?
    https://stackoverflow.com/a/50781170

    It works perfecly for EPAM production instance, my local setup and EPAM rp demo... So maybe issue in your server setup then?

  7. avarabyeu commented on Mar 27, 2019

    @avarabyeu
    Member

    @BorisOsipov @DzmitryHumianiuk @VladislavAkulich
    axios/axios#658 (comment)

    Guys, if mentioned in issue's commit is the case, moving to axios is a big mistake and the change must be reverted.
    What do you think?

  8. BorisOsipov commented on Mar 27, 2019

    @BorisOsipov
    Contributor
    1. restler(previous http client) doesn't support work under proxy at all see Proxy setting danwrong/restler#176 So reverting won't help
    2. Issue closed with explanation "I think the problem is that the proxy you're configuring is an HTTP server, not HTTPS." So, configure you env correctly.
    3. I don't care. I've already made fork for my projects to avoid dependencies from this repo
  9. DzmitryHumianiuk commented on Apr 5, 2019

    @DzmitryHumianiuk
    Member
  10. navisayslisten commented on May 29, 2019

    @navisayslisten

    Not resolved for me. I get this error when setting up an https url to Report Portal.

    Error: Request failed with status code 404: {"timestamp":1559165140583,"status":404,"error":"Not Found","message":"No message available","path":"/api/v1/myproject/user"}
        at axios.then.catch (C:\dev\myproject\node_modules\reportportal-js-client\lib\rest.js:27:23)
        at <anonymous>
        at process._tickDomainCallback (internal/process/next_tick.js:228:7)
    

    The funny thing is, Report Portal still gets the test results. The error makes me think it didn't work at all.

  11. BorisOsipov commented on May 30, 2019

    @BorisOsipov
    Contributor

    @navisayslisten your problem aren't related to https. You ran into issue that has been fixed by b64e919

  12. DzmitryHumianiuk commented on May 30, 2019

    @DzmitryHumianiuk
    Member

    @BorisOsipov fix is not yet released, right?

  13. BorisOsipov commented on May 31, 2019

    @BorisOsipov
    Contributor
  14. Viacheslav-Romanov commented on Jul 18, 2019

    @Viacheslav-Romanov

    Guys, please elevate the proxy parameter from the axios client to the reportportal client's configuration as it causes integration issues for those behind proxy servers.

  15. xadvfh commented on Nov 23, 2020

    @xadvfh

    @BorisOsipov I'm seeing a similar issue. In my case, we have a certificate issued by our corporate CA.

  16. mudit94 commented on Aug 1, 2023

    @mudit94

    I am unable to use certificate in report portal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions