Michael Adams (mdawaffe)

Oops. Forgot to click the subscribe checkbox. Ignore this comment ??

I apologize for the hassle.

First, a couple practical things that can help:
1 – Jetpack Contact Form and Akismet work together. If you don’t already have Akismet installed, I recommend it. It should reduce both comment spam and feedback spam.
2 – You can delete more than 20 things at a time. If you go to the Feedbacks page, then click “Screen Options” in the upper right corner, you’ll see a form where you can specify how many items to show on a page. The default is 20, but you can put in whatever you want.

And yes, trashing/deleting feedbacks should remove the entries from wp_posts and the corresponding entries from wp_postmeta.

Now that those practical concerns are out of the way, on to the real problem: why did this happen in the first place.

https://www.fencepost.net/contact/ has a Jetpack Contact Form in it. I can tell because the source of that page mentions “grunion” (the name of the old plugin that was turned in to Jetpack Contact Forms). Also, you can see a jetpack/modules/contact-form/css/grunion.css stylsheet loaded on that page.

I see that you are using the latest version of Jetpack. Are you also using the latest version of Contact Form 7? There used to be an incompatibility between the two plugins, which has since been fixed. It’s possible, though, that you’ll need to edit your page’s contact form.

If you edit that page (https://www.fencepost.net/contact/), what is the shortcode you see? If you want to use Contact Form 7, the shortcode should say “[contact-form-7”. If you want to use Jetpack Contact Forms, it should say “[contact-form”. (That unfortunate similarity was the source of the incompatibility I mentioned above.)

Manually editing Jetpack Contact Form shortcodes is a pain. If you want to use them, I suggest clicking the Contact Form editing icon in your editor as seen in the first screenshot at https://jetpack.me/support/contact-form/

Manually editing Contact Form 7’s shortcodes is also a pain ?? If you want to use them, I suggest going to your admin -> Contact and copying the shortcode from the form you want to use (or creating a new one).

Also, you can disable Jetpack Contact Forms entirely by going to your admin -> Jetpack. Then find the Contact Form box and click its “Learn More” button. A “Deactivate” button will appear next to the Learn More button. Click Deactivate. (Yes, we know this is a really dumb process ?? We’re going to make it much simpler in a future release.)

Again, I’m sorry about all this pain and annoyance.

Thanks for the feedback. Jetpack now includes Publicize ??

https://jetpack.me/support/publicize/

Enjoy!

Is the problem still happening?

Those are almost certainly our Jetpack Servers communicating with your site.

We don’t have access to (and do not want access to) your account’s password, so Jetpack uses it’s own OAuth-based authentication layer to interact with your site.

When you combine how most XML-RPC endpoints work with how WordPress handles authentication, though, it turns out that, even though Jetpack uses it’s own OAuth-based authentication, we still have to send a username and password with the request. The Jetpack plugin tells WordPress to completely ignore that username and password, but we still have to send it to get things in WordPress working correctly.

So we send a username of “username” and a password of “password”. That’s what your logs are showing.

We could send something else to make it more obvious what’s happening like a username of “jetpack”, for example. These aren’t real log in attempts, though, they just use some of the same WordPress hooks as log in attempts do, which is why the Simple Login Log plugin thinks they are log in attempts.

It’s not clear to me if “Failed” means the OAuth-based authentication Jetpack uses actually failed or if Simple Login Log just doesn’t understand what to make of these requests.

You’re welcome. I’m glad you got it (mostly ;)) working.

Jetpack does fallback to HTTP during registration, but it only does so when it sees certain error messages. Your proxy must be responding with an error message Jetpack doesn’t recognize.

Honestly, though, this sounds like a misconfigured proxy.

I strongly encourage you to talk to your network administrators about opening up HTTPS requests. Unless they want to be able to snoop on all of your traffic, I can’t think of a reason why HTTPS should be blocked.

Also, editing the Jetpack files means you’ll have to keep editing them every time you updated Jetpack, which would be a pain. Instead of editing jetpack.php, you can add the following to your wp-config.php.

defined( 'JETPACK_CLIENT__HTTPS', 'NEVER' );

A warning to you and others that read this thread. Do not do this . HTTPS is better. Work with your host and/or network administrators to get HTTPS working correctly instead.

If this is the only thing that makes Jetpack work, then there is either a problem with your host/network or a bug in Jetpack. Please report the problem to us https://jetpack.me/support/ (bottom of the page) so we can fix Jetpack if the problem lies there.

Thanks ?? We implemented your fallback idea in https://plugins.trac.www.ads-software.com/changeset/588184

Correct. Jetpack subscription emails are not sent from your site. They are sent from our Jetpack servers at WordPress.com. So your plugins aren’t able to change the emails.

We understand customization is important for many people, but it isn’t something we currently are able to offer.

Currently, Jetpack only makes your admin images, Gravatars, images hosted on WordPress.com, and LaTeX (niche!) images retina. Jetpack currently doesn’t retinize images hosted on your own site.

I know that’s not the answer you’re looking for ?? Sorry for the hassle.

What is the issue you’re experiencing?

I’m not familiar with that plugin, but Jetpack Subscription emails are actually sent from our Jetpack servers at WordPress.com. There is not currently any way to customize them.

We’re working on adding a few more options to customize the text, but we don’t currently have any plans for customizing the style/look/feel.

Also, the Jetpack Comments feature isn’t currently compatible with other subscriptions plugins, so to use another subscriptions plugin, not only would you have to turn off the Jetpack Subscriptions feature, you would also need to turn off the Jetpack Comments feature. We’d like to make Jetpack Comments more extensible, but it’s a little limited at the moment.

To turn off a Jetpack feature:
1. Go to your admin → Jetpack
2. Click the “Learn More” button on the feature you want to turn off.
3. A “Deactivate” button will appear next to that “Learn More” button.
4. Click the “Deactivate” button.

Sorry for the hassle ??

What is the URL in the browser window that gets a 502?

Do you have access to your PHP error logs? If so, what do they show when you get the 502 error?

Thanks for letting us know about the problem.

This has been fixed in the in-development version of Jetpack: https://plugins.trac.www.ads-software.com/changeset/587005

I’m not sure when the next bug fix release will be, but my guess is sometime next week.

Note that the error would not be visible to your visitors if you had your PHP ini’s display_errors set to false. display_errors should never be set to true on a production server.

https://php.net/manual/en/errorfunc.configuration.php#ini.display-errors

Thanks for letting us know about the problem.

This has been fixed in the in-development version of Jetpack: https://plugins.trac.www.ads-software.com/changeset/586791

I’m not sure when the next bug fix release will be, but my guess is sometime next week.