tauri-apps / tauri-apps/tauri-docs
Caddy Self signed and system level trusted certificates not working in Tauri
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
Hi,
We have multiple apis running behind caddy for exposing https self certificates on local domain names like api.awesome-app.lan & app.awesome-app.lan for instance.
After calling caddy trust on ubuntu
- curl
https://app.awesome-app.lan=> 🟢 - chrome on
https://app.awesome-app.lan=> 🟢 - a rust process using
reqwestcrate callinghttps://api.awesome-app.lan=> 🟢 - tauri http plugin (yes
allowconfigured) onhttps://app.awesome-app.lan=> 🔴
I saw some issues here that might be related ... not sure, also it seems to be a discussed topic in the discord.
What would be the right way to go in order to make this work ? (and avoid activating the dangerous-settings feature in tauri plugin)
Thanks
EDIT : epiphany web browser on utunbu => 🟢
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Review the Tauri HTTP plugin's certificate behavior on Ubuntu, comparing the caddy trust results for curl, Chrome, reqwest, and the plugin; done should be a documented supported approach or a confirmed limitation that avoids dangerous-settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, ubuntu
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100