Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to specify https certificates #255

Closed
Razmo99 opened this issue Nov 16, 2023 · 1 comment · Fixed by #257
Closed

unable to specify https certificates #255

Razmo99 opened this issue Nov 16, 2023 · 1 comment · Fixed by #257

Comments

@Razmo99
Copy link

Razmo99 commented Nov 16, 2023

G'day Love the app,

Decided to enable Https on Nginx which I am running the Tachidesk server through. Was able to get the desktop version (windows )on Sorayomi working by installing the public crt in the certificate store no problem.

The android app doesn't appear to have any way to get it to trust a self signed certificate :(
I've installed my certificate within the CA Authority store on my Android. Chrome works for Tachideks webUI without a certificate error, Sorayomi atm just says check your internet connection , I'm confident this is a Cert trust issue

Are we able to allow the app to trust user certificates or add an option to specify a certificate for the https connection within the app

Cheers


Describe the bug
Unable to connect to a Tachidesk server that is using Https with Sorayomi

To Reproduce
Steps to reproduce the behavior:

  1. Connect to a https enabled Tachidesk server with a self signed certificate from an android device
  2. it will fail to connect

Expected behavior
Should be able to connect to a Tachidesk server using https

Device information (Server)

  • Tachidesk version: preview 0.70 r1424
  • Server Operating System: Ubuntu 20.04
  • Using Docker Compose

Device information (Client)

  • Client version: 12
  • Client Type: Mobile
  • Client Operating System: Android
  • Client Specifications: Samsung S10
@DattatreyaReddy
Copy link
Collaborator

DattatreyaReddy commented Nov 20, 2023

I'll try to fix this issue in the next release. I may be unable to test it so it will be directly released to Production. If you face this issue after the next release, Please raise the issue again.

Thank you,
Sorry for the late reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants