Skip to main content

Plugins::Base.process! -> StandardError: private_plugin

Your new plugin's screen won't generate. After turning on debug logs, your private plugin generates errors about marionette or a TCP connection.

Mario avatar
Written by Mario
Updated over 2 weeks ago

Your private plugin isn't generating a screen, even when using Force Refresh. So, you troubleshoot by turning on debug logs for your plugin. Everything looks good, until after Generating Screen Now you see an error message!

Here are two possible errors you may be seeing (with your plugin id):

  • Plugins::Base.process! -> StandardError: private_plugin 179259 Failed to open TCP connection to 127.0.0.1:4446 (Connection refused - connect(2) for "127.0.0.1" port 4446)

  • Plugins::Base.process! -> StandardError: private_plugin 179259 Failed to decode response from marionette

What Does it Mean?

Our screen rendering workers are unable to access a URL specified within your plugin markup, most commonly an image src.

I Don't See a Problem in Markup Preview

Two reasons:

  1. Preview renders in your browser, not our worker boxes, and your browser is much more forgiving with issues than the headless browsers we use to render screens.

  2. You may have an issue with data (e.g. Your Variables) that is being hidden from you because of data-overflow or simply being scrolled beyond the screen, like a prblem with item 15 in an RSS feed, while the preview can only fit the first 5.

How Do I Fix It?

First, find the problem. If you have dynamic URLs, such as from Liquid logic, replace them with a known-good URL placeholder, then Force Refresh. If the errors do not show up and the screen is properly rendered, you have pinpointed the source of the problem. Now the hard part, you have to figure out why and how to catch it.

If using a Liquid loop, use the filters offset and limit to find exactly what iteration is causing a problem, then dig, dig, dig. Good luck!

Did this answer your question?