-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something went wrong with the subscription. #1157
Comments
Yes, looks like there is a problem with the email newsletter! |
@cerebrumbr thank you for reporting the issue. Internal reference: MAGETWO-36266 |
Hi @cerebrumbr, we've fixed this issue and its fix is available in 0.74.0-beta8. Could you check it? |
Hello @vpelipenko - Perfect now, good job. |
Sorry to reopen this issue. I am on Community release 2.0.4, and I am receiving the same issue as this original post. Is there any new fix to this? Below is an image of the error. |
I also am having the same issue on Community 2.0.5. |
Hi, How have you resolved this problem ? Please, I have this problem with Magento 2.0.7? |
I installed Magento 2.1 in a domain www.craftallure.com Then configured magento SMTP with following credential Then after doing these steps but finding error: Step 1: Open this URL: https://www.craftallure.com/ Step 2: Fill any email address in subscription form footer and click subscribe. Step 3: Then this error will be visible in red error note. Is there anyone got any proper update on it? `This is exception error message I copied here. It might can give some light [2017-01-07 20:47:11] main.CRITICAL: Exception message: Could not open socket Any update will be highly helpful. |
…ore Mode is enabled #1157 - Merge Pull Request magento-engcom/magento2ce#1157 from RomaKis/magento2ce:7822 - Merged commits: 1. a49f524 2. e4353ad
…ProductIdsBySourceItemIds-class-use-nventoryApi Removed InventoryCache dependency on Inventory
When try registrer email newsletter subscription.
Return this alert ...
Something went wrong with the subscription.
The text was updated successfully, but these errors were encountered: