HTTP code: 502 Bad Gateway

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Peter J. Herrel

    (@donutz)

    11 years, 7 months ago

    Thanks for reporting @leejosepho. I’m not sure the error you’re getting is caused by the AWLD for WP plugin, or the awld.js script, as that website is not listed among the resources. Could you maybe explain why you think this has to do with the plugin?

    Thread Starter leejosepho

    (@leejosepho)

    11 years, 7 months ago

    Could you maybe explain why you think this has to do with the plugin?

    It actually seems to me that the problem is at some server the plugin might be trying to access, and I am definitely not presuming to know the plugin is the actual problem. Knowing virtually nothing at all about a 502 error, I just though posting here might help in some kind of overall way along the line of conveying or relaying this matter to whoever would want to know about it since I do not know exactly what else to do.

    Having hopefully accomplished something like that even inadvertently, I will mark this thread as resolved while thanking you for a great plugin!

    Thread Starter leejosepho

    (@leejosepho)

    11 years, 7 months ago

    Ah, please forgive me here. I have just realized the error I am receiving has nothing whatsoever to do with this plugin.

    ** leaves red-faced **

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘HTTP code: 502 Bad Gateway’ is closed to new replies.