Integration with self hosted instance results in 404
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
As far as I know there is currently no way to use your own Jitsi server/instance in this extension.
The only reason why I'm using Jitsi is so that I can self host it and provide the best confidentiality to my customers compared to other private and proprietary solutions such as Microsoft Teams.
Therefore, I've got my own Jitsi server that is hosted in my home and ciphered using TLS (HTTPS). It would be nice to integrate it in this app, rather than using default Jitsi servers, otherwise Jitsi has no point to me.
Thank you!
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
The issue names no files or tests; start by locating the integration entry point and tracing how the default Jitsi server is selected. The work is done when a self-hosted HTTPS Jitsi instance can be configured and used without the reported 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100