Skip to content

🐛 Cannot checkout order #471

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

Open
Gijsen opened this issue Mar 31, 2025 · 2 comments
Open

🐛 Cannot checkout order #471

Gijsen opened this issue Mar 31, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@Gijsen
Copy link

Gijsen commented Mar 31, 2025

Note

Please stick to the template and provide as much detail as possible to help us diagnose and fix the issue.
Low effort bug reports will be closed.

Describe the bug
Checkout for item results in a crash

To Reproduce
Create item. This happens on both paid and free items
Add item and press continue

Expected behavior
Get redirected to the order details window

Screenshots
This is the /checkout/{event_id}/{order_id}/details window:

Image

Logs
From the console we can see the following call that results in a error:
https://{url}/api/public/events/1/order/o_cxpdg93qj1jhn?include=event

This results in 403 Forbidden also visible in the docker logs
https://events-dev.pmsafed.be/api/public/events/1/order/o_cxpdg93qj1jhn?include=event

Desktop (please complete the following information):

  • OS: Windows
  • Browser Chrome

Hi.Events Version and platform
Docker running the v1.0.0-alpha.15

@Gijsen Gijsen added the bug Something isn't working label Mar 31, 2025
@Gijsen Gijsen changed the title 🐛 🐛 Cannot checkout order Mar 31, 2025
@daveearley
Copy link
Contributor

Hi @Gijsen,

Your session cookie is being rejected by the browser as the domain is set to localhost.

Try setting this env variable in your environment:

SESSION_DOMAIN=pmsafed.be

Image Image

@Gijsen
Copy link
Author

Gijsen commented Mar 31, 2025

Thank you !

this indeed was the issue, as this is behind a proxy.
Is it maybe important to add this to the Docker deployments?

If not set I suppose it gets the domain via the request itself? Would this also be solved when I added this in my nginx setup?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants