Skip to content
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

🐛Error message "Something went wrong" during checkout #253

Open
cobalt-tendons opened this issue Oct 14, 2024 · 13 comments
Open

🐛Error message "Something went wrong" during checkout #253

cobalt-tendons opened this issue Oct 14, 2024 · 13 comments
Labels
bug Something isn't working

Comments

@cobalt-tendons
Copy link

Describe the bug
I have deployed on Render and everything works fine using the default project URL they assign automatically, e.g. hi-events-xxxx.onrender.com. I am able to manage events and checkout without any issues. However, I cannot complete the checkout when using a custom domain, e.g. rsvp.mydomain.com.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Hi-Events instance at rsvp.mydomain.com
  2. Add tickets to cart
  3. Click Continue button
  4. See error (screenshot attached)

Expected behavior
Expected to continue to the next step of the checkout process

Screenshots
Screenshot 2024-10-14 3 14 15 PM

Desktop (please complete the following information):

  • OS: Chrome OS
  • Browser: Chrome
  • Version: 126.0.6478.252

Smartphone (please complete the following information):

  • Device: iPhone12
  • OS: iOS 18
  • Browser: Stock Safari

Hi.Events Version and platform
Docker @ render.com

Logs
N/A

Additional context
N/A

@cobalt-tendons cobalt-tendons added the bug Something isn't working label Oct 14, 2024
@daveearley
Copy link
Contributor

Hi @cobalt-tendons,

From the screenshot it appears the API URL being used is still the default render URL. This may explain the error. In Render.com, what is the value for the VITE_API_URL_CLIENT env variable? It should be the custom domain, not the Render default domain.

@cobalt-tendons
Copy link
Author

Thanks @daveearley and sorry for the delay. The Environment page in Render didn't have a VITE_API_URL_CLIENT variable, so I added it =rsvp.mydomain.com, but it didn't help. Screenshots attached. I also hopped into the container, manually exported the variable and restarted the node app, still getting that 403.

env
devtools

@daveearley
Copy link
Contributor

It looks like the API URL still isn't correct. I'm not overly familiar with Render.com, so you may need to reach out to their support to see why the env variable isn't updating.

@f1dz
Copy link

f1dz commented Nov 1, 2024

It has also happened to me. The problem was we were using the same browser to log in as admin and to order the ticket.
Try a different browser or opening a new window on incognito/private solved the problem.

@daveearley
Copy link
Contributor

@f1dz Thanks for the additional information. Admins should be able to complete orders without issue. Do you see any errors in the logs when you encounter this error?

@f1dz
Copy link

f1dz commented Nov 1, 2024

@f1dz Thanks for the additional information. Admins should be able to complete orders without issue. Do you see any errors in the logs when you encounter this error?

Yes, I got the same error when I use the same browser as admin logged in. After using different browser, it went well. I use Safari for Admin and Chrome for attendee.

Additional information, I use docker all-in-one.

@Caseit18
Copy link

Also getting the 403 "Sorry, we could not verify your session. Please restart your order." (in the console)
The Header shows: GET http://10.139.50.19:8123/api/public/events/1/order/o_AjFOlsECqMNXz?include=

Self Hosted, All In One docker (to get a better understanding of the product).
I did try separate browsers than the admin one per @f1dz 's suggestion. Problem remains.

(my .env file)
VITE_FRONTEND_URL=http://10.139.50.19:8123
VITE_API_URL_CLIENT=http://10.139.50.19:8123/api
VITE_API_URL_SERVER=http://10.139.50.19:80/api
VITE_STRIPE_PUBLISHABLE_KEY=pk_test
LOG_CHANNEL=stderr
QUEUE_CONNECTION=sync
MAIL_MAILER=log
APP_DISABLE_REGISTRATION=true
APP_SAAS_MODE_ENABLED=false
APP_CDN_URL=http://10.139.50.19:8123/storage

Forgive the very noobish question, but shouldn't there be something after the = in my GET command?

@daveearley
Copy link
Contributor

Hi @Caseit18, the issue may be that you're using HTTP, rather than HTTPS. The checkout process relies on a secure cookie to track the customer's session. Some browsers will not allow a secure cookie to be set over HTTP.

@Caseit18
Copy link

Hi @Caseit18, the issue may be that you're using HTTP, rather than HTTPS. The checkout process relies on a secure cookie to track the customer's session. Some browsers will not allow a secure cookie to be set over HTTP.

I appreciate the feedback. I'm worried I'm taking this ticket off track.

I punched https in place of the http variables but it now generates an "ERR_SSL_PROTOCOL_ERROR" when trying to access.

VITE_FRONTEND_URL=https://10.139.50.19:8123
VITE_API_URL_CLIENT=https://10.139.50.19:8123/api
VITE_API_URL_SERVER=https://10.139.50.19:80/api
This feels funky given that the nginx inside of the container is doing 'normal' listening on port 80 (which is 'mapped' via docker from 8123). Is a cert even generated if you don't do the 'local development' path of deployment?

@daveearley
Copy link
Contributor

daveearley commented Nov 22, 2024

@Caseit18 No, we don't provide any SSL certs other than the local development cert. You'll have to handle that yourself.

@ravibhoraniya
Copy link

ravibhoraniya commented Jan 1, 2025

Hi, I tried without Docker and got the same error. Please check my environment variable.

Front Build
VITE_API_URL_CLIENT=http://localhost:8000
VITE_API_URL_SERVER=http://localhost:8000

VITE_FRONTEND_URL=http://localhost:5678

Backend
APP_URL=http://localhost
APP_PORT=8000
APP_FRONTEND_URL=http://localhost:5678

@daveearley
Copy link
Contributor

@ravibhoraniya With the limited information you've provided it's difficult to determine the issue. Have you followed the instructions in this guide?

@ravibhoraniya
Copy link

Hello @daveearley, I would like to inform you that I have followed the same steps and configured the .env file accordingly; however, I am still encountering this issue. I have attempted this process four times.

here data:
Screenshot 2025-01-02 at 4 44 11 PM

VITE_API_URL_CLIENT: 'https://event.iwebinfotech.com',
VITE_API_URL_SERVER: 'https://event.iwebinfotech.com',
VITE_FRONTEND_URL: 'http://localhost:3002',
NODE_PORT: '3002'

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

5 participants