-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Whoops!, it looks like the server returned an error. #1113
Comments
Is this the part where you resend ticket to the attendee? |
I have the error when creating the ticket but no logs even with debug mode enabled.
Test:
https://cineonu.unric.org/public/e/1/raise-the-bar
…________________________________
De : Zappie080011 ***@***.***>
Envoyé : vendredi 6 octobre 2023 18:14
À : Attendize/Attendize ***@***.***>
Cc : Philippe Chabot ***@***.***>; Author ***@***.***>
Objet : Re: [Attendize/Attendize] Whoops!, it looks like the server returned an error. (Issue #1113)
Vous ne recevez pas souvent de courriers de la part de ***@***.*** Découvrez pourquoi cela est important<https://aka.ms/LearnAboutSenderIdentification>
Is this the part where you resend ticket to the attendee?
—
Reply to this email directly, view it on GitHub<#1113 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXYISLWTXUVCITDFKRUIE6DX6AU55AVCNFSM6AAAAAA5O6TFVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGAZDGMZRGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
If you send tickets to attendees or getting errors in the checkout process configure your .env file specifically the "smtp" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sending Tickets generate errors.
Version 2.8.0
The text was updated successfully, but these errors were encountered: