Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author 2FAS

    (@2fas)

    Hi,

    We’re sorry you’re experiencing problems with our plugin. We’d like to ask you to do three steps in order to find the cause of this problem. Could you:

    1. Put Pusher.logToConsole = true; in the magic-password/assets/js/pusher-events.js file just after if ( sessionId.length ) { (line 69).
    2. Clear browser cache.
    3. Open JavaScript console, go to plugin’s settings page and take a screenshot of the console?

    This will give us important information about the problem.

    If you have any difficulties with these steps, don’t hesitate to ask.

    [ Signature moderated ]

    • This reply was modified 7 years, 2 months ago by Jan Dembowski.
    Thread Starter codeagency

    (@7grafix)

    OK done

    This is what I get:

    JQMIGRATE: Migrate is installed, version 1.4.1
    pusher.min.js:8 Pusher : State changed : initialized -> connecting
    pusher.min.js:8 Pusher : Connecting : {“transport”:”ws”,”url”:”wss://ws.pusherapp.com:443/app/9e2d2476a82fec3240c6?protocol=7&client=js&version=4.0.0&flash=false”}
    pusher.min.js:8 Pusher : State changed : connecting -> connected with new socket ID 217279.51918854
    /wp-admin/admin.php?page=magic-password-settings&mpwd-action=authenticate-channel Failed to load resource: the server responded with a status of 403 ()
    pusher.min.js:8 Pusher : Couldn’t get auth info from your webapp : 403
    warn @ pusher.min.js:8
    pusher.min.js:8 Pusher : Couldn’t get auth info from your webapp : 403

    Plugin Author 2FAS

    (@2fas)

    Thank you. We’d like to ask you to do one more thing. Can you check what response /wp-admin/admin.php?page=magic-password-settings&mpwd-action=authenticate-channel return?

    Thread Starter codeagency

    (@7grafix)

    It also returns similar error as below:

    error something went wrong with authenticating channel.
    Basically, it’s a 403 error.

    https://drive.google.com/file/d/0B3E0HcdrCbPTZW43V2hIMV9oZTA/view?usp=sharing

    Plugin Author 2FAS

    (@2fas)

    There are several reasons why 403 response status occurs. We’ll do plugin update and make error handling more verbose as soon as we can.

    We’re sorry for any inconvenience.

    Plugin Author 2FAS

    (@2fas)

    We’ve just released a new plugin version with bug fixes. We recommend to do an update. If problem still occurs, please let us know.

    [ Signature moderated ]

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘server error occured’ is closed to new replies.