• Resolved gld

    (@gld)


    Hi, having an issue presently with Launchkey authentication. I suspect it’s a server/ firewall issue however wanted to get your perspective:

    1. User attempts a login – correct
    2. Launchkey initiates an authentication – correct
    3. Authentication is given – correct
    4. WP seems to timeout waiting a response

    The WP error is as follows:
    —————–
    Proxy Error

    The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request POST /wp-login.php.

    Reason: Error reading from remote server
    —————–

    Any idea what might be going on? Thanks!

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

    (@aenglander)

    There are two important details that are required for an authorization response to be received by the LaunchKey WordPress plugin.

    1. Your LaunchKey app must be properly configured in the LaunchKey Dashboard. You must set the Callback URL item in the Configuration section of the General tab of you LaunchKey Application settings with the callback URL provided by the plugin during the setup wizard in the Add this Callback URL to your Application or in the plugin settings.
    2. The callback URL must be accessible from the LaunchKey servers in the iovation data centers. If you WordPress instance is behind a firewall and cannot be accessed via the Internet, you will not be able to use the LaunchKey plugin. If you are just test driving LaunchKey on your own computer, you can use a reverse proxy tool like Ngrok.

    Feel free to respond if this does not resolve your issue.

    Adam

    Thread Starter gld

    (@gld)

    Thanks Adam, that makes sense.

    The callback URL is set and is aligned but I believe the issue lies in the second point. For some reason the URL is accessible on the LAN but not from outside on the Internet. It’s therefore a networking/ firewall issue. I’ll look into it from here. Thanks so much!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Proxy Error’ is closed to new replies.