• Hello

    i tried several times to install your plugin, but i end up with “502 Bad Gateway nginx/1.2.6” each time.

    i tried it with WP 3.8 and 3.8.1., i also tried to deactivate all plugins (including W3 total cache) before installing your plugin. no matter what i do i still get “502 Bad Gateway” after i activate your plugin.

    if i deactivate your plugin and clear cache everything works fine again

    any clues?

    best regards and thanks in advance!

Viewing 7 replies - 1 through 7 (of 7 total)
  • Anonymous User 9782929

    (@anonymized-9782929)

    Hi there,

    I really have no clue on this one. Sorry I couldn’t help! Couldn’t really find much on the google either.

    Can you successfully activate the plugin? or is the error when you have to put in your name and email address?

    Thread Starter muen AT

    (@muen-at)

    Hi

    yes, on the back end everything works fine – i can install, activate and work with the plugin (enter email and so on). no problems here.

    the problem is in front end – as soon as i activate the plugin, the whole web page goes down with error “502 Bad Gateway”.

    at the beginning i thought the W3 total cache could be causing the problem. so i tried to clear cache or even disable the plugin altogether before installing your plugin. nothing happenden. i still get the same error message. only if i deactivate your plugin the web page works fine again.

    Anonymous User 9782929

    (@anonymized-9782929)

    Hm… really not sure what may be causing this. My best guess would be some sort of PHP memory limit… Sorry I can’t be more helpful.

    Might it be worth asking the hosts about this? Sounds like something on the server is falling over.

    Anonymous User 9782929

    (@anonymized-9782929)

    Could be. Like I said, I’m not really sure.

    If the error’s only there when Lively is active, seems like it is Lively.

    If you’d like, inviite me ([email protected]) to the WP Admin area and I’ll have a better look.

    Thread Starter muen AT

    (@muen-at)

    1. yes, the error only occurs with Lively active
    2. i just got reply from my host – they automatically kill the connection because with Lively active it consumes too much CPU time (over 15 CPU seconds per connection).

    pls kindly look into your plugin to optimize resource usage.

    Anonymous User 9782929

    (@anonymized-9782929)

    Thanks for the feedback. I’m not sure what would be so heavy on the CPU usage, but I’ll look at optimizing things in a future release. Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘502 Bad Gateway after plugin install’ is closed to new replies.