When i shift my vue frontend to a public domain, I can not login anymore. I get an log error "WebSocket connection to ... failed". The logs from the backend are okay. In the dashboard a new token is shown, but the frontend did not recieve this. I use vue behinde Traefik with the cors middleware. Do I have to add more options to Traefik?

hey @derbernd does the sign in request succeed? And if you do doesSessionExist after sign in, does that return true?

The request succeed:

com.supertokens {t: "2023-05-16T08:48:03.006Z", message: "doesSessionExist: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.007Z", message: "FrontToken.getTokenInfo: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.007Z", message: "getFrontToken: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.007Z", message: "getLocalSessionState: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.008Z", message: "getFrontTokenFromCookie: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.009Z", message: "getLocalSessionState: returning NOT_EXISTS since frontToken was cleared but lastAccessTokenUpdate exists", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.009Z", message: "getFrontToken: Returning because sIRTFrontend != EXISTS", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.009Z", message: "getLocalSessionState: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.009Z", message: "getFrontTokenFromCookie: called", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.010Z", message: "getLocalSessionState: returning NOT_EXISTS since frontToken was cleared but lastAccessTokenUpdate exists", supertokens-website-ver: "16.0.9"}
logger.js:31 com.supertokens {t: "2023-05-16T08:48:03.010Z", message: "doesSessionExist: access token does not exist locally", supertokens-website-ver: "16.0.9"}

Can I see the response headers of the sign in request?

I found the problem. It's correlated to the browser. It did't work, if I use brave on Linux. Brave on Mac works. Firefox on Linux works.

hmm. That's really strange. Is it a browser bug?

I don't know.

can i see the sign in response headers as shown on google chrome?

access-control-allow-credentials: true access-control-allow-headers: * access-control-allow-methods: * access-control-allow-origin: https://app.******** access-control-expose-headers: * cache-control: max-age=31536000,immutable content-length: 3510 content-type: application/javascript date: Wed, 17 May 2023 06:08:43 GMT etag: W/"db6-EsiQVU2KF6b5jaIfwkicg2RAq9U" vary: Origi

so no session tokens sent to the client?

from "Supertokens.tsx" i get:

:authority: app.****
:method: GET
:path: /src/components/auth/Supertokens.tsx
:scheme: https
accept: */*
accept-encoding: gzip, deflate, br
accept-language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7
cookie: st-last-access-token-update=1684133063262; ph_phc_fmJsC .....
if-none-match: W/"6aa-2CUYKKz1DdURJM45NztxNra7TrM"
origin: https://app.*****
referer: https://app.beta.******
sec-ch-ua: "Brave";v="111", "Not(A:Brand";v="8", "Chromium";v="111"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Linux"
sec-fetch-dest: script
sec-fetch-mode: cors
sec-fetch-site: same-origin
sec-gpc: 1
user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36

im not sure i understand whats doing on.

Where can I get these?

so when the user signs in from the browser, the browser makes an API cal to the backend. WHat is the response headers of that API call?

I don't know what I have changed, but now i works. I did not work on the login section of my app. Excuse my questions.

hm. Okay. If this error happens again, please feel free to reach out.

Okay, Thank you