jackmeat
Forum Replies Created
-
All good again today! Thank you @alinclamba and hopefully @jungle7 @kampenk35 had the same positive result.
Thanks again for the prompt attention to this issue
I am not sure if you were able to fix this or if something was done on Instagrams end, but my daily review just shared over to Instagram along with the other socials without issue. I have been following my usual routine including the push with Jetpack social, and just noticed that so thought I would let you all know.
I only post daily, so I will see what happens again 24 hours from now. Thank you!
I’ll try this again since my last message got deleted for some reason. I guess thanking the developers is a No-No. Seems like an odd reason to delete a message.
Thank you for escalating this. (I won’t point out that I am manually sharing for the time being so my workflow is unaffected nor that I’ll leave my website unchanged so I don’t make things more complicated. Oh, and that I hope this is fixed quickly since it is a great time saver. I don’t want to say any of those things since one of them got my comment moderated out)
Oh goodie, it is being held by automod again. “No action is needed on your part at this time, and you do not need to resubmit your message.” Wanna bet, you deleted my comment last time for no reason so yeah, I need to resubmit it.
I have the exact problem above as @jungle7. This began immediately after the wordpress 7.0 upgrade. I also shared the exact same image from the image url from my website to instagram to verify the image was not the issue. I also disconnected and reconnected instagram in jetpack social. still getting the “media could not be published because the media status is unknown:” error message. My workflow is completely unchanged over the past two years. this will effect my daily reviews (the last two failed) but here is todays if you need a reference. as was stated, everything on my end appears correct.
[ Link deleted, you can start your own topic if needed ]
@chrism245 Yes, whatever the problem was (and it sure looks like the Hostinger email was the issue) has been alleviated when I switched to your sending service. As I said, I was going to hit their limit soon anyways, so better to get ahead of it, rather than fight with this issue for a month or two, only to be forced to switch. Since that confrimation page issue is resolved, I am happy with using mailpoet to email out.
The mailpoet sending service appears to be working just fine, and I am happy with it. Thank you for following up.
Oh well, my long explanation vanished. change action, deactivate/reactivate triggered the send. not using smtp from hostinger, changed to mailpoet send service.
It was already set to action scheduler, and i was able to trigger it by changing off the action scheduler to the linux server side, deactivating, and reactivating and changing back and doing the same. But that is all a moot point since I have switched over to your send service. I didn’t want to wait a week and have another newsletter get stalled, and I also know that sooner or later, I was going to hit my hosts limit of 100 and decided to go with your send service. The previous confirmation issue is also resolved and it went out fine yesterday. I should have closed this ticket although I have no way of knowing what was going on.
@batthcouk Thank you for the updates. I didn’t remove, but I deactivated the plugin after changing from action scheduler to the server side linux cron. then switched back and deactivated/reactivated again and it triggered the send. I had also dug into the database and removed a couple of stalled entries which matched the times of the most recent post before the process above. Not sure which or all of it was the fix, but then the floodgates opened and I triggered my send frequency error from Hostinger, so that is now a me issue, not a Mailpoet stalling issue.
When I tried the immediately before all of the above last night, it just sat there as scheduled (not sent) the same as the scheduled one but i believe if I tried that now, it would be different. I wish you good luck and I appreciate the info. If I find the cause if this stall, since something you and I do must be matching, I’ll report back.
Forum: Plugins
In reply to: [Web Push Notifications - Webpushr] Vulnerability in the pluginI swear I seconded this a few days ago as well. Might be losing my mind.
- Issue Found February 2, 2026 10:29 pm Critical
Message sent to through that forum. Instead of wasting more time with a back and forth, why would you NOT just ask me those questions in email directly?
Anyways, look forward to potentially getting this resolved so I can go back to using confirmations instead of allowing everyone and their bot buddy to register.
As I said in my initial post “I have used troubleshooter and only that plugin and mailpoet, and installed a default theme as well, and I still get this for my confirmations.” In other words, I tested with NO other plugins active BUT yours.
Under my settings, both URL entries are https://jackmeat.com
- This reply was modified 6 months, 3 weeks ago by jackmeat.
As I said, I used YOUR webpage to guide the setup. Unless changing the text color screws this up, it is identical to yours. https://pasteboard.co/FQZ0RjuyCeBo.png
Yes, I mentioned other web clients such as Blue Mail give the net:err_file_not_found message, which is less info than the Outlook error. Gmail just negates the Confirm button from doing anything. So, yes I am confirming that other clients are giving the message, why are you asking redundant questions.
I was using only the shortcode as [activation_link]. It is on your premade confirmation page, so it was only being used on top of a button. Those instructions are exactly what I used in the first place, and I used the Enable visual subscription confirmation emails option with minimal changes whatsoever. THis is the error in Outlook, and other clients show net:err_file_not_found (which I assume is the same problem.)
https://pasteboard.co/4PQCRnyfQ1of.png
- This reply was modified 7 months, 1 week ago by jackmeat.
I replied a week ago. I am not using mailpoet’s forms anymore. No idea what is wrong with them.
I also cannot find that error you reported either. My form using cloudflare as a solution is working fine for the past week, so I see no need to turn back which is why I marked this as resolved a week ago.
I am using Cloudflare turnsitle with a self made form now that hooks into mailpoet.
