Back

Property 'setSelfSigned' does not exist on type 'Client'.

  • 0
  • Self Hosted
  • React Native
LeanderM
6 Nov, 2024, 20:16

I cannot figure out how to use setSelfSigned(true) with my React Native client... it simply doesn't exist on any client. Tried the web client as well in a different app.

TL;DR
- Developer running Appwrite in Docker on Macbook - Unable to access files in bucket from React Native client on same Wi-Fi network - Facing certificate validation issue with self-signed certificate - Propose using HTTP instead of HTTPS or looking into handling self-signed certificates in React Native - Mentions `setSelfSigned` only available on server-side SDKs like `node-appwrite` - Unable to find equivalent method in React Native client or web client - Solution: Consider using HTTP instead of HTTPS or research React Native libraries for handling self-signed certificates
Kenny
6 Nov, 2024, 20:28

I believe setSelfSigned in only avaliable on server side sdks like node-appwrite

LeanderM
6 Nov, 2024, 20:42

Hm. Appwrite is running in docker on my Macbook. I cannot access any files in my bucket from my client React Native app. Client is on the same Wi-Fi network.

For example a file url like https://192.168.2.15/v1/storage/buckets/audio/files/......etc

Will give me "java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Steven
6 Nov, 2024, 23:57

i suggest either use HTTP instead of HTTPS or google how to handle self-signed certificates in react native

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more