Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hey there,

    it seems that i’ve a similar problem. I’ve added my user groups which should be able to log in to my website for some early preperations. But only my root admin account is able to login. I’ll only see “Permission Access denied” in my Browser, followed by the lock icon switching to red color as soon as i entered my account details for my regular user accont.

    Running WordPress 4.7.1 and Maintenance Pro 3.3 on WordPress Network Mode.

    Thanks and have a nice day!

    Edit from 21-01-2017, 13:16: I have to add the fact that no user can login to my website after i’ve excluded user roles. Even my root admin account can’t login. As soon as i clear all user exclusions, my users can login successfully. I’ve also tried to add to reverse the user exclusions but this also leads to the result that no one of my team members can login.

    • This reply was modified 9 years, 4 months ago by aseth181012.
    • This reply was modified 9 years, 4 months ago by aseth181012.
    Thread Starter aseth181012

    (@aseth181012)

    Hey,

    looks like my Converse tries to connect to my Openfire server with External authentication. I’ve never configured my server to accept authentications at this way. I’ve changed my SASL mechs in my Openfire configuration, now everything works as expected.

    Thanks,
    Lucas

    Thread Starter aseth181012

    (@aseth181012)

    Hey there everyone,

    I can’t offer you any links to my website right now, because we’re working at the website… We’ve disabled the access to our website for every user. Only our admins can access the site at the moment. I’ve also created a ticket at the converse.js support. I think this is a bug in the Converse.js code itself.

    But i can offer you some Debug logs from my browser console while connecting to my Openfire Server:

    Warning: The “initialized” event has been deprecated and will be removed, please use “connected”. converse.nojquery.min.js:217:8116

    Could not restore session. Error message: _restore: no restoreable session. converse.nojquery.min.js:217:8116

    Status changed to: CONNECTING converse.nojquery.min.js:217:8116
    _throttledRequestHandler called with 1 requests converse.nojquery.min.js:217:8116

    request id 1.0 posting converse.nojquery.min.js:217:8116

    request id 1.0 state changed to 1 converse.nojquery.min.js:217:8116

    <body rid=”899624935″ to=”agoshan.com” xml:lang=”en” wait=”60″ hold=”1″ content=”text/xml; charset=utf-8″ ver=”1.6″ xmpp:version=”1.0″ xmlns:xmpp=”urn:xmpp:xbosh”/> converse.nojquery.min.js:217:8116

    request id 1.1 state changed to 2 converse.nojquery.min.js:217:8116

    request id 1.1 state changed to 3 converse.nojquery.min.js:217:8116

    request id 1.1 state changed to 4 converse.nojquery.min.js:217:8116

    removing request converse.nojquery.min.js:217:8116

    _throttledRequestHandler called with 0 requests converse.nojquery.min.js:217:8116

    request id 1 should now be removed converse.nojquery.min.js:217:8116

    request id 1.1 got 200 converse.nojquery.min.js:217:8116

    _connect_cb was called converse.nojquery.min.js:217:8116

    <body xmlns=”http://jabber.org/protocol/httpbind&#8221; xmlns:stream=”http://etherx.jabber.org/streams&#8221; from=”agoshan.com” authid=”q0jo19cdn” sid=”q0jo19cdn” secure=”true” requests=”2″ inactivity=”30″ polling=”5″ wait=”60″ hold=”1″ ack=”899624935″ maxpause=”300″ ver=”1.6″><stream:features><mechanisms xmlns=”urn:ietf:params:xml:ns:xmpp-sasl”><mechanism>PLAIN</mechanism><mechanism>SCRAM-SHA-1</mechanism><mechanism>EXTERNAL</mechanism></mechanisms><register xmlns=”http://jabber.org/features/iq-register”/><bind xmlns=”urn:ietf:params:xml:ns:xmpp-bind”/><session xmlns=”urn:ietf:params:xml:ns:xmpp-session”><optional/></session></stream:features></body> converse.nojquery.min.js:217:8116

    _throttledRequestHandler called with 0 requests converse.nojquery.min.js:217:8116

    _throttledRequestHandler called with 1 requests converse.nojquery.min.js:217:8116

    request id 2.0 posting converse.nojquery.min.js:217:8116

    request id 2.0 state changed to 1 converse.nojquery.min.js:217:8116

    <body rid=”899624936″ sid=”q0jo19cdn”><auth mechanism=”EXTERNAL”>YXNldGgxODEwMTJAYWdvc2hhbi5jb20=</auth></body> converse.nojquery.min.js:217:8116

    request id 2.1 state changed to 2 converse.nojquery.min.js:217:8116

    request id 2.1 state changed to 3 converse.nojquery.min.js:217:8116

    request id 2.1 state changed to 4 converse.nojquery.min.js:217:8116

    removing request converse.nojquery.min.js:217:8116
    _throttledRequestHandler called with 0 requests converse.nojquery.min.js:217:8116

    request id 2 should now be removed converse.nojquery.min.js:217:8116

    request id 2.1 got 200 converse.nojquery.min.js:217:8116

    _dataRecv called converse.nojquery.min.js:217:8116

    <body xmlns=”http://jabber.org/protocol/httpbind&#8221; ack=”899624936″><failure xmlns=”urn:ietf:params:xml:ns:xmpp-sasl”><not-authorized/></failure></body> converse.nojquery.min.js:217:8116

    Status changed to: AUTHFAIL converse.nojquery.min.js:217:8116

    Status changed to: DISCONNECTING converse.nojquery.min.js:217:8116

    Disconnect was called because: Authentication Failed converse.nojquery.min.js:217:8116

    _sendTerminate was called converse.nojquery.min.js:217:8116

    _throttledRequestHandler called with 1 requests converse.nojquery.min.js:217:8116

    request id 3.0 posting converse.nojquery.min.js:217:8116

    request id 3.0 state changed to 1 converse.nojquery.min.js:217:8116

    <body rid=”899624937″ sid=”q0jo19cdn” type=”terminate”/> converse.nojquery.min.js:217:8116

    request id 3.1 state changed to 2 converse.nojquery.min.js:217:8116

    request id 3.1 state changed to 3 converse.nojquery.min.js:217:8116

    request id 3.1 state changed to 4 converse.nojquery.min.js:217:8116

    removing request converse.nojquery.min.js:217:8116

    _throttledRequestHandler called with 0 requests converse.nojquery.min.js:217:8116

    request id 3 should now be removed converse.nojquery.min.js:217:8116

    request id 3.1 got 200 converse.nojquery.min.js:217:8116

    _dataRecv called converse.nojquery.min.js:217:8116

    <body xmlns=”http://jabber.org/protocol/httpbind&#8221; type=”terminate” ack=”899624937″/> converse.nojquery.min.js:217:8116

    _doDisconnect was called converse.nojquery.min.js:217:8116

    Status changed to: DISCONNECTED converse.nojquery.min.js:217:8116

    DISCONNECTED converse.nojquery.min.js:217:8116

    Thanks,

    Lucas

    • This reply was modified 9 years, 4 months ago by aseth181012.
    Thread Starter aseth181012

    (@aseth181012)

    Hey John,

    i was able to solve this error, however, not exactly with your solution.
    My problem was solved after i’ve added these two lines in my nginx configuration.

    proxy_buffers 16 16k;
    proxy_buffer_size 32k;

    Maybe it has something to do with Parallels Plesk, nginx works as a reverse proxy on my server. Anyways, everything works fine now!

    Thanks,
    Lucas

    • This reply was modified 9 years, 4 months ago by aseth181012.
    Thread Starter aseth181012

    (@aseth181012)

    Hey there everyone,

    so it seems that the problem isn’t Converse, it seems that Openfire 4.1.0 makes trouble. Since i’ve downgraded my Openfire server to the previous build due to an other serios problem, Converse could connect without any problems. I’ll also send on the problem to the developers of Openfire…

    Thanks anyway and have a happy new year,

    Lucas

    Thread Starter aseth181012

    (@aseth181012)

    Hey there,

    i’ve changed my bosh server to your recommended server, but i’m still not able to connect to my server. Any other suggestions?

    Thanks,

    Lucas

    Thread Starter aseth181012

    (@aseth181012)

    Hey John,

    well, it seems that the database problem has been solved. But the 502 error while logout still occurs. I found some new nginx error in my logs everytime i try to logout / reloading the logout page:

    2016-12-27 16:08:48 Error 93.196.139.236 8596#0: *2312 upstream sent too big header while reading response header from upstream nginx-error
    2016-12-27 16:13:04 Error 93.196.139.236 8596#0: *2450 upstream sent too big header while reading response header from upstream nginx-error
    2016-12-27 16:13:06 Error 93.196.139.236 8596#0: *2453 upstream sent too big header while reading response header from upstream nginx-error
    2016-12-27 16:13:08 Error 93.196.139.236 8596#0: *2455 upstream sent too big header while reading response header from upstream

    I’ve also tried to disable all plugins, like bbPress, BuddyPress, … But still 502 errors…

    Thanks,
    Lucas

    • This reply was modified 9 years, 5 months ago by aseth181012. Reason: Adding some additional details
Viewing 7 replies - 1 through 7 (of 7 total)