"This content is blocked" on non-default port
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
NextCloud 28
Docker-Based Jitsi
Is it possible to work on non-standard port with Jitsi?
I can go there with port 45138 while using native login via browser. But when I try to connect with NextCloud via NextCloud Jitsi App it says that "this content is blocked".
Certificates are correctly obtained from Let's Encrypt.
From traffic analysis perspective there is no any traffic initiated from NextCloud to Jitsi.
UPD:
NextCloud config:
Topology:
*Hosts - content of hosts file
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
Start by reproducing the Nextcloud Jitsi App connection with the Docker-based Jitsi instance on port 45138, using the Nextcloud configuration and hosts-file setup shown in the issue. Inspect the browser's "this content is blocked" failure and compare it with a standard-port setup. Done means the app can open the Jitsi meeting on the non-default port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100