502 Bad Gateway after activating a custom built plugin

Support
,
1

What issue or error are you experiencing?

I’m getting a 502 error when trying to activate one of my custom built plugins.

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

All you’d need to do is clone a custom plugin from github, and then activate it.

When I deactivate the plugin in Adminer (by deleting the active_plugins row in wp_options) Everything seems to work.

If I install a plugin from WordPress directly, and activate it, I don’t get any issues.

System Details

  • Local Version:
    Version 9.0.2+6676

  • Operating System (OS) and OS version:
    MacOS 14.4.1

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-lightning.log (35.1 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hi, @criosgtma.

Have you tried enabling WordPress PHP error logging via wp-config.php then seeing what the error is when you activate the plugin?

Plugins installed from GitHub sometimes need additional setup steps (like composer install) before you can activate them — the bundled version on WP.org will ship with any dependencies already bundled. Checking PHP error logs should confirm this or help you to narrow it down to other issues.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.