# JSXC broken in Freedombox 20.4? **URL:** https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747 **Category:** Support **Created:** [March 21, 2020, 9:48am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747 "2020-03-21T09:48:27Z") **Posts on this page:** 13 **Page:** 1
### Author: ![homer77](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/homer77/32/283_2.png) [@homer77](https://discuss.freedombox.org/u/homer77) #### Post date: [March 21, 2020, 9:48am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/1 "2020-03-21T09:48:27Z")
**Problem Description** JSXC allows to login in but I just receive a broken UI (Screenshot) I guess that’s not what it should look like and actually the app is unusable. **Steps to Reproduce** 1. Install freedombox on armbian (debian buster) on odroidxu4 2. Install ejabberd on fresh box. 3. Open jsxc 4. Login **Expected Results** I expected a working chat client in my browser window **Actual results** An incomplete and unusable interface **Screenshot** JSXC looks like this. ![Bildschirmfoto von 2020-03-21 10-32-44](https://discuss.freedombox.org/uploads/default/original/1X/790d0198975e6a7728a8cab7666e4042d3c5dbfc.png) **Information** Debian GNU/Linux 10 (buster) and FreedomBox Version 20.4 - _Hardware_: odroid XU4 - _How did you install FreedomBox?_: ‘apt install freedombox’ ---
### Author: ![jvalleroy](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/jvalleroy/32/331_2.png) [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy) #### Post date: [March 22, 2020, 11:19am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/2 "2020-03-22T11:19:14Z")
I can reproduce this issue currently on Buster and on testing. For Buster, there are 2 resources that get 404: jsxc.css and dsa-webworker.js. For testing, it is just jsxc.css. I found this issue a few times in the tracker: - [https://salsa.debian.org/freedombox-team/plinth/issues/1297](https://salsa.debian.org/freedombox-team/plinth/issues/1297) - [https://salsa.debian.org/freedombox-team/plinth/issues/1221](https://salsa.debian.org/freedombox-team/plinth/issues/1221) - [https://salsa.debian.org/freedombox-team/plinth/issues/1180](https://salsa.debian.org/freedombox-team/plinth/issues/1180) Some more details are in this Debian bug report: - [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838183](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838183) Perhaps we can work around this bug by symlinking the jsxc.css file into /usr/share/javascript/jsxc. ---
### Author: ![homer77](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/homer77/32/283_2.png) [@homer77](https://discuss.freedombox.org/u/homer77) #### Post date: [March 23, 2020, 11:51pm UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/3 "2020-03-23T23:51:08Z")
I don’t think symlinking will do the job. ``` ``` The resources unter /usr/share/plinth/static/ lack totally the jsxc directory and while you could link jsxc.css I don’t know where to find jsxc-plinth.css. So that’s no easy job. I guess the package has to be repaired by someone with a deeper understanding of the where and whys of the dependencies. ---
### Author: ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil) #### Post date: [March 24, 2020, 12:25am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/4 "2020-03-24T00:25:23Z")
Please try running the following to fix the problem: ```auto sudo su - cd /usr/lib/python3/dist-packages/plinth/modules/jsxc/static/ ln -s /usr/share/libjs-jsxc/img/ mkdir libjs-jsxc cd libjs-jsxc ln -s /usr/share/libjs-jsxc/css/jsxc.css ln -s /usr/share/javascript/jsxc/lib ln -s /usr/share/libjs-jsxc/sound/ ``` I will submit a pull request to fix this. ---
### Author: ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil) #### Post date: [March 24, 2020, 12:29am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/5 "2020-03-24T00:29:06Z")
> [@homer77](#): > > The resources unter /usr/share/plinth/static/ lack totally the jsxc directory and while you could link jsxc.css There is special web server mapping that says `static//` will be mapped to `plinth/modules//static` so you will find that file in `/usr/lib/python3/plinth/modules/jsxc/static`. ---
### Author: ![homer77](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/homer77/32/283_2.png) [@homer77](https://discuss.freedombox.org/u/homer77) #### Post date: [March 24, 2020, 10:22am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/6 "2020-03-24T10:22:53Z")
It works like a charm! Great! Thank you very much for your help and expertise 😍 Maybe you can tell me also: The jsxc version is a little behind - which is of course normal for a stable OS but … It doesn’t support OMEMO yet while the current RC from [https://github.com/jsxc/jsxc](https://github.com/jsxc/jsxc) does. A great improvement if you ask me as most mobile clients do not support otr anymore. I guess exchanging the installed jsxc with the 4.0.0rc isn’t trivial? ---
### Author: ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil) #### Post date: [March 24, 2020, 10:08pm UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/7 "2020-03-24T22:08:22Z")
Merge request is now available and the problem should get fixed automatically in the next release 20.5.1 or 20.6. ---
### Author: ![jvalleroy](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/jvalleroy/32/331_2.png) [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy) #### Post date: [March 26, 2020, 10:12am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/8 "2020-03-26T10:12:41Z")
Updating JSXC to a newer version (even 3.3.2) requires new dependencies to be packaged for Debian. See the “blocking bugs” on [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812933](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812933). ---
### Author: ![homer77](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/homer77/32/283_2.png) [@homer77](https://discuss.freedombox.org/u/homer77) #### Post date: [March 26, 2020, 10:37am UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/9 "2020-03-26T10:37:39Z")
Thank you very much. I guess that will take some time until that, won’t it? ---
### Author: ![homer77](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/homer77/32/283_2.png) [@homer77](https://discuss.freedombox.org/u/homer77) #### Post date: [March 26, 2020, 4:18pm UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/10 "2020-03-26T16:18:20Z")
Maybe I should mention [Xep-363 and xep-359 support](https://discuss.freedombox.org/t/xep-363-and-xep-359-support/668/11) here as the problem is critical for jsxc to work. Even if it’s not a problem with jsxc code base … but with the bosh server of ejabberd. Or is it …? ---
### Author: ![homer77](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/homer77/32/283_2.png) [@homer77](https://discuss.freedombox.org/u/homer77) #### Post date: [March 31, 2020, 10:40pm UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/11 "2020-03-31T22:40:30Z")
I can’t find any hint how to fix **this BOSH problem.** Is here anyone who has mod\_bosh in ejabberd on _port 5443_ and `tls: true` and jsxc still working?! Even if I put tls on false - then I lose http\_upload. https:\:5443/bosh leads correctly to the **test-page of mod\_bosh** , so the bosh server obviously works. But if I start jsxc and type in the domain field the check outputs a failure > BOSH server NOT reachable or misconfigured. > > 502 Proxy Error Any hint welcome! ---
### Author: ![NickA](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/n/3ab097/32.png) [@NickA](https://discuss.freedombox.org/u/NickA) #### Post date: [November 9, 2020, 8:58pm UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/12 "2020-11-09T20:58:37Z")
@perken I have no idea why your non-JSXC clients can’t connect to your ejabberd, maybe check [https://wiki.debian.org/FreedomBox/Manual/ejabberd](https://wiki.debian.org/FreedomBox/Manual/ejabberd) and look for logs. ---
### Author: ![problema](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/problema/32/1527_2.png) [@problema](https://discuss.freedombox.org/u/problema) #### Post date: [August 21, 2025, 11:08pm UTC](https://discuss.freedombox.org/t/jsxc-broken-in-freedombox-20-4/747/13 "2025-08-21T23:08:48Z")
Years after this publication, I am dealing with the same situation in current FB version: I can log in and Bosh seems fine, but the JSXC interface is unusable, as seen in the previous picture. This happens both if I connect from WAN and from LAN. I tried the solution that you propose to correct links, but it has not worked (maybe I worsened it). The underlying cause of my problem is probably different. My server: **freedombox 25.9.3** (with **libjs-jsxc 3.4.4+dfsg-2** ) installed on x86-64 Debian Trixie.