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

GUI disappeared after upgrade JSXC from 3.2.1 to 3.3.0 #615

Closed
ADZVL opened this issue Aug 31, 2017 · 7 comments
Closed

GUI disappeared after upgrade JSXC from 3.2.1 to 3.3.0 #615

ADZVL opened this issue Aug 31, 2017 · 7 comments
Assignees
Labels

Comments

@ADZVL
Copy link

ADZVL commented Aug 31, 2017

Expected behavior

Stable operation as in version 3.2.1

Actual behavior

I currently can not make use of JSXC because it is not displayed in Nextcloud despite being enabled

Steps to reproduce the behavior

1.Upgrade from Nextcloud or manually
If I return to version 3.2.1. Everything works perfectly, but I'm interested in using this new version

Environment

  • JSXC version: JavaScript XMPP Chat 3.3.0
  • Host system and version: Nextcloud 12.0.2 (stable)
  • Server SO: Ubuntu 16.04 LTS
  • Browser vendor and version: Firefox 55(Linux) or chrome 58(Android 5.0.2)
  • Any browser plugins enabled? No
  • XMPP server vendor and version: Ejabberd 16.01
  • Is your XMPP server working with other clients as expected? Yes

Logs

Javascript

consolecompleteweb

JSXC

webconsoledebugcomplete

XMPP

This happens when I log in, in version 3.2.1 I had no problems authenticating:

2017-08-31 15:48:05.664 [info] <0.466.0>@ejabberd_listener:accept:333 (#Port<0.12978>) Accepted connection ::FFFF:127.0.0.1:45570 -> ::FFFF:127.0.0.1:5280
2017-08-31 15:48:05.664 [info] <0.1622.0>@ejabberd_http:init:158 started: {gen_tcp,#Port<0.12978>}
2017-08-31 15:48:06.152 [info] <0.466.0>@ejabberd_listener:accept:333 (#Port<0.12979>) Accepted connection ::FFFF:127.0.0.1:45574 -> ::FFFF:127.0.0.1:5280
2017-08-31 15:48:06.153 [info] <0.1625.0>@ejabberd_http:init:158 started: {gen_tcp,#Port<0.12979>}
2017-08-31 15:48:06.295 [info] <0.1624.0>@ejabberd_c2s:wait_for_feature_request:767 ({socket_state,ejabberd_http_bind,{http_bind,<0.1623.0>,{{172,19,17,208},45570}},ejabberd_http_bind}) Failed authentication for user@domain.com from 172.19.17.208
2017-08-31 15:48:17.662 [info] <0.1620.0>@ejabberd_http_bind:handle_info:507 Session timeout. Closing the HTTP bind session: <<"c2734624223287a840be1af775a13870749f18e5">>
2017-08-31 15:48:36.296 [info] <0.1623.0>@ejabberd_http_bind:handle_info:507 Session timeout. Closing the HTTP bind session: <<"4bbcaadc3377ffbec185ca40ec98ae19cb58e017">>

Similarly XCAUTH worked well in 3.2.1, now show this:

2017-08-31 15:48:06,160 DEBUG: Receive operation auth
2017-08-31 15:48:06,161 DEBUG: auth(user, domain.com, ...)
2017-08-31 15:48:06,161 DEBUG: Token has expired
2017-08-31 15:48:06,161 DEBUG: Token has expired
2017-08-31 15:48:06,162 INFO: Resetting dropped connection: domain.com
2017-08-31 15:48:06,294 DEBUG: "POST /apps/ojsxc/ajax/externalApi.php HTTP/1.1" 200 19
2017-08-31 15:48:06,295 INFO: FAILURE: Could not authenticate user user@domain.com: noauth

Host

{"reqId":"iGERJyEpoz5ZKICKwrDt","level":2,"time":"2017-08-31T20:47:47+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"vPHjcQSE6IXCsTPefkcm","level":2,"time":"2017-08-31T20:48:06+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"1T8ZsBzrfQKq8HnXOTAm","level":2,"time":"2017-08-31T21:01:42+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"hps7K2jjF6L9wsm9BWhI","level":2,"time":"2017-08-31T21:02:22+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"LLNbBdVY95hdU41156vg","level":2,"time":"2017-08-31T21:02:41+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"zAznC9XtaItu9NrvoMGK","level":2,"time":"2017-08-31T21:02:47+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"B4c8tkKhVHEZmAmaG8HH","level":2,"time":"2017-08-31T21:24:53+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}
{"reqId":"FwcDF1dn0mrqsFGuOJMI","level":2,"time":"2017-08-31T21:24:56+00:00","remoteAddr":"172.19.17.208","user":"--","app":"core","method":"POST","url":"\/apps\/ojsxc\/ajax\/externalApi.php","message":"Login failed: 'user' (Remote IP: '172.19.17.208')","userAgent":"python-requests\/2.9.1","version":"12.0.2.0"}

I want to clarify that despite the authentication errors, I can log in to NextCloud but I can not use JSXC. Basically because it does not appear.

@sualko
Copy link
Member

sualko commented Sep 1, 2017

Can you try it again, after you executed jsxc.deleteAllData() in your javascript console?

@ADZVL
Copy link
Author

ADZVL commented Sep 1, 2017

Thank you very much now it works perfectly :)
After running that line, the first login I made had the same behavior but from then on it worked correctly.

@ADZVL ADZVL closed this as completed Sep 1, 2017
@MarcelWaldvogel
Copy link
Contributor

@sualko Could you venture a guess which variable might have caused the problem? And how to prevent others from running into the same problem while upgrading?

@sualko
Copy link
Member

sualko commented Sep 13, 2017

Could you venture a guess which variable might have caused the problem?

Currently not, but as there is a second reporter now, I will try to investigate this further.

@sualko sualko added the bug label Sep 13, 2017
@sualko sualko self-assigned this Sep 13, 2017
@sualko
Copy link
Member

sualko commented Sep 14, 2017

I tried to rebuild your issue by installation v3.2.1 and updating to v3.3.0, but I was not able to reproduce the issue. Can someone recreate the above situation and give a hint?

@sualko
Copy link
Member

sualko commented Sep 14, 2017

@AlesAlitis can you provide a log from a failing (one which doesn't start the ui) jsxc instance?

@MarcelWaldvogel
Copy link
Contributor

@sualko: @DanScharon may know someone who still has the problem. Please PM him.

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

No branches or pull requests

3 participants