Server not notified

[twisted]

All of a sudden we are getting this error. Nothing changed on our end. I changed the numbers and names there for privacy.



This is a notification that for the transaction NUMBER, we were unable to notify your server at http://NAMEOFOURSITE.us2.list-manage.com/subscribe/ejunkie-ipn?u=NUMBER&id=NUMBER as we we received the error: HTTP Error 500



POST /subscribe/ejunkie-ipn?u=NUMBER&id=NUMBER HTTP/1.1



Pragma: no-cache



Accept: /



Host: NAMEOFSITE.us2.list-manage.com



Content-type: application/x-www-form-urlencoded



Content-Length: 1246



and a giant error message follows but i has customer data so i'm not postin git.

[twisted]

Mailchimp shows no api calls...

[beingwater]

I got this as well. I don't know what MailChimp has to do with anything. I don't use Mailchimp in my cart system. It has been running smoothluy for years . I believe there is some type of hack attack going on

[twisted]

Does e-junkie have a support # with some more realtime support?

[beingwater]

No only email and a message

[E-junkie_Ninja]

Our development team took a look into this problem and whatever the cause is, it is on MailChimp's end. For some reason their system is not responding to ours when we are sending order data to them after checkout is complete, which creates the error in our system which we then contact our users about. At this time we need to wait for MailChimp to repair the issue in their system.

[zenmagnets_com]

twistedDoes e-junkie have a support # with some more realtime support?

No, but mailchimp does. Current suggested workaround is to update the common notification URL. Go to your mailchimp account > extras > integrations > e-junkie tab

and re-copy the notifcation URL to your e-junkie account preferences.

[zenmagnets_com]

Looks like this workaround doesn't actually work. I'm still getting similar messages.



@E-junkieNinja, have you gotten in touch with mailchimp to try to figure out what's going on for your customers?

[E-junkie_Monster]

I've asked our development team to see if they can get in touch with MailChimp about the issue, since we've been getting a lot of back and forth between our mutual clients. Unfortunately, this isn't something we can fix or address or even assist with from this end. All our system does is send order data to an address that has been provided by MailChimp. If that address is incorrect or if they are unable to parse the data, we can't do anything about that from here.



All the order data is still being saved and the orders are being processed normally otherwise, so fortunately the buyer names and email addresses that aren't currently being recorded by MailChimp will still be saved in your transaction logs.

[zenmagnets_com]

Thanks. I've been in communication with MailChimp support too. As of right now, I'm still getting "server not notified" emails, despite customers being correctly added to the list.

[twisted]

www.ismercuryinretrograde.com

Apparently tomorrow all our tech problems will be resolved.

[beingwater]

Whew! That's it. Thanks for setting me straight. I forgot about Mercury

[zenmagnets_com]

Haha. What?!??

[E-junkie_Guru]

We've now heard back from MailChimp, who informed us that last week they were fending off a DDoS attack against their servers -- i.e., flooding their server with so much bogus traffic that it impeded their availability and responsiveness -- which would explain the error notifications you received:

http://status.mailchimp.com/