How to avoid "self signed certificate" error?

[k1tzu]

import fetch from 'isomorphic-fetch';

const httpLink = new HttpLink({
  fetch,
  uri: `https://localhost:3000/graphql`,
});

[rtymchyk]

This used to be fix-able with agent: new https.Agent({ rejectUnauthorized: false }), given to a network interface. Now I don't know.

[k1tzu]

process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; did the thing for me.

[rtymchyk]

For anyone wondering, you can also do:

const link = createHttpLink({
    fetchOptions: {
      agent: new https.Agent({ rejectUnauthorized: false }),
    },
})

[jbaxleyiii]

@rtymchyk would you be able to add this to the docs? And what use case does this solve? I'm not familiar with agent?

[rtymchyk]

@jbaxleyiii The use case it solves for me is connecting to my API node that has a self-signed SSL certificate on the dev environment. Requests from Apollo do not complete otherwise. I can add to docs if you think it's common enough.

[jbaxleyiii]

I'm not sure its common enough but I could imagine people getting stuck on it and hard to find. I'd love to see it as a recipe if you are open to it!

[zhaiduo]

@rtymchyk https module seems works only in NodeJs, How could it work in RN client?

When I try this on Android device (iOS device no problem), get the following error:

Error: While trying to resolve module https from file .../node_modules/https-agent/index.js, the package .../node_modules/https/package.json was successfully found. However, this package itself specifies a main module field that could not be resolved (.../node_modules/https/index.js. Indeed, none of these files exist:

[rtymchyk]

Sorry, I'm not familiar with RN and what's available there.

[zhaiduo]

It's Android 7.0's bug. facebook/react-native#17891

[dani-z]

With React Native you can't use https node module. Just speaking for myself the use case would be to test https connection in a react RN App locally, because iOS does not support anymore unsecured API calls.

[pedzed]

process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; did the thing for me.

Where did you put it?

[dsolivera]

process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; did the thing for me.

Where did you put it?

@pedzed add process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0'; in your you index.js file right after all the LaunchAPI & UserAPI constants. That should solve the problem.