Login Issue for own deployment

Help
1

Hello dear Specklers,

for our deployment, we have OpenID Connect via Azure AD as SSO for the Server. This also works for the majority of colleagues … somehow one colleague runs into issues.

Scenario as following

  • We cleaned up the Browser History of Firefox to have a cleanslate … including cookies
  • She opens our Speckle Server Address
  • Registers for the first time with AzureAD SSO
  • Account is created and she has the onboarding screen
  • she verifies her account
  • logs out
  • We have this error page
    MicrosoftTeams-image (29)
    MicrosoftTeams-image (29)1916×916 63.4 KB

She is able to login/logout via Microsoft Edge without any issues. Is there something simple we have missed?

Thanks :slight_smile:

Best,
Alex

2

Hi @AlexHofbeck

Hopefully we can help you get this resolved!
To confirm, this is just an issue on FireFox browser only?
Does this only occur immediately after registration? Or is she able to refresh FireFox and login?

When she logs in via Microsoft Edge, does she have to repeat the registration process there or is the user set up correctly?

Can you confirm which version of the server is running?

Are you able to gather the information in the browser console when this occurs?

Thanks

Iain

3

Hi Iain,
thanks for your support :slight_smile:

→ For the Microsoft Edge it works stable …

→ Does not even work with refresh … also not by deleting the Browser history. When we are creating her account new, it works only at the first login

→ user is set up correctly (at least it shows up on the admin overview page)

The server version during our tests was the last 2.14.7. We updated to 2.15 briefly before lunch. New version results in the same issue.

Here is the text of the console … I have replaced our server URL with arbitrary naming:

Das Cookie "mp_acd87c5a50b56df91a795e999812a3a4_mixpanel" verfügt über keinen gültigen Wert für das "SameSite"-Attribut. Bald werden Cookies ohne das "SameSite"-Attribut oder mit einem ungültigen Wert dafür als "Lax" behandelt. Dadurch wird das Cookie nicht länger an Kontexte gesendet, die zu einem Drittanbieter gehören. Falls Ihre Anwendung das Cookie in diesen Kontexten benötigt, fügen Sie bitte das Attribut "SameSite=None" zu ihm hinzu. Weitere Informationen zum "SameSite"-Attribut finden Sie unter https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite. index-3fb3419d.js:34:2777

Einige Cookies verwenden das empfohlene "SameSite"-Attribut inkorrekt. 5 

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Die Verbindung zu wss://servername.com/graphql wurde unterbrochen, während die Seite geladen wurde. index-3fb3419d.js:908:34822

GETwss://servername.com/graphql 

Firefox kann keine Verbindung zu dem Server unter wss://servername.com/graphql aufbauen. index-3fb3419d.js:908:34822

Best,
Alex

4

Hi Alex,

From the messages it appears that they have WebSockets blocked in FireFox.

Does this user have similar console messages in Edge?
Do other users with Firefox also see the same console errors?

If they don’t see these messages, this may be the cause of the issue for this user. Websockets might be blocked by a setting in the Firefox browser itself, or an extension (like an AdBlocker). Would you be able to enable WebSockets in Firefox and try to login?

Iain

1 Like
5

I also have the websocket issue on my machine with Edge

index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908
index-3fb3419d.js:908  WebSocket connection to 'wss://servername.com/graphql' failed: Error during WebSocket handshake: Unexpected response code: 400
e.connect @ index-3fb3419d.js:908
(anonymous) @ index-3fb3419d.js:908

so basically everything except of the mixpanel cookie line

but don’t have issues with the access.

Her Edge Browser also does not show anything about the mixpanel … only the websockets

6

@AlexHofbeck - if your environment is working despite the websocket error, then we can ignore that as a ‘red herring’.

Do you have logs from the server? You may be able to filter the logs by the user ID (which can be found at url /profile when the user is logged in ). We may be able to determine if this is a server related problem.

Iain

1 Like
7

I don’t know if there is something interesting here … I have modified our servername and client-ip

{“level”:“info”,“time”:“2023-07-26T07:57:07.251Z”,“req”:{“id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“method”:“POST”,“path”:“/graphql”,“headers”:{“connection”:“upgrade”,“host”:“speckle-server:3000”,“content-length”:“387”,“x-forwarded-proto”:“https”,“sec-ch-ua”:“"Not/A)Brand";v="99", "Microsoft Edge";v="115", "Chromium";v="115"”,“apollographql-client-name”:“web”,“sec-ch-ua-mobile”:“?0”,“user-agent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.183”,“content-type”:“application/json”,“accept”:“/”,“apollographql-client-version”:“unknown”,“sec-ch-ua-platform”:“"Windows"”,“origin”:“https://servername.com”,“sec-fetch-site”:“same-origin”,“sec-fetch-mode”:“cors”,“sec-fetch-dest”:“empty”,“referer”:“https://servername.com/profile",“accept-encoding”:"gzip, deflate, br”,“accept-language”:“de,de-DE;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6”,“x-request-id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“x-speckle-client-ip”:“Client-IP”}},“authContext”:{“auth”:true,“userId”:“ddafae1cd7”,“role”:“server:user”,“scopes”:[“streams:read”,“streams:write”,“profile:read”,“profile:email”,“profile:delete”,“users:read”,“server:stats”,“users:email”,“server:setup”,“tokens:read”,“tokens:write”,“apps:read”,“apps:write”,“users:invite”]},“req”:{“id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“method”:“POST”,“headers”:{“connection”:“upgrade”,“host”:“speckle-server:3000”,“content-length”:“387”,“x-forwarded-proto”:“https”,“sec-ch-ua”:“"Not/A)Brand";v="99", "Microsoft Edge";v="115", "Chromium";v="115"”,“apollographql-client-name”:“web”,“sec-ch-ua-mobile”:“?0”,“user-agent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.183”,“content-type”:“application/json”,“accept”:“/”,“apollographql-client-version”:“unknown”,“sec-ch-ua-platform”:“"Windows"”,“origin”:“https://servername.com”,“sec-fetch-site”:“same-origin”,“sec-fetch-mode”:“cors”,“sec-fetch-dest”:“empty”,“referer”:“https://servername.com/profile",“accept-encoding”:"gzip, deflate, br”,“accept-language”:“de,de-DE;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6”,“x-request-id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“x-speckle-client-ip”:“Client-IP”}},“authContext”:{“auth”:true,“userId”:“ddafae1cd7”,“role”:“server:user”,“scopes”:[“streams:read”,“streams:write”,“profile:read”,“profile:email”,“profile:delete”,“users:read”,“server:stats”,“users:email”,“server:setup”,“tokens:read”,“tokens:write”,“apps:read”,“apps:write”,“users:invite”]},“component”:“graphql”,“graphql_operation_kind”:“mutation”,“graphql_query”:“mutation UpdateUserNotificationPreferences($preferences: JSONObject!) {\n userNotificationPreferencesUpdate(preferences: $preferences)\n}\n”,“graphql_variables”:{“preferences”:{“activityDigest”:{“email”:“[REDACTED]”},“mentionedInComment”:{“email”:“[REDACTED]”},“newStreamAccessRequest”:{“email”:“[REDACTED]”},“streamAccessRequestApproved”:{“email”:“[REDACTED]”}}},“graphql_operation_value”:“GQL mutation userNotificationPreferencesUpdate”,“grqphql_operation_name”:“GQL userNotificationPreferencesUpdate”,“actionName”:“mutation userNotificationPreferencesUpdate”,“msg”:“graphql response”}
{“level”:“info”,“time”:“2023-07-26T07:57:07.251Z”,“req”:{“id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“method”:“POST”,“path”:“/graphql”,“headers”:{“connection”:“upgrade”,“host”:“speckle-server:3000”,“content-length”:“387”,“x-forwarded-proto”:“https”,“sec-ch-ua”:“"Not/A)Brand";v="99", "Microsoft Edge";v="115", "Chromium";v="115"”,“apollographql-client-name”:“web”,“sec-ch-ua-mobile”:“?0”,“user-agent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.183”,“content-type”:“application/json”,“accept”:“/”,“apollographql-client-version”:“unknown”,“sec-ch-ua-platform”:“"Windows"”,“origin”:“https://servername.com”,“sec-fetch-site”:“same-origin”,“sec-fetch-mode”:“cors”,“sec-fetch-dest”:“empty”,“referer”:“https://servername.com/profile",“accept-encoding”:"gzip, deflate, br”,“accept-language”:“de,de-DE;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6”,“x-request-id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“x-speckle-client-ip”:“Client-IP”}},“res”:{“statusCode”:200,“headers”:{“x-request-id”:“cdd8ccd6-a723-472d-9877-23dc3c6a8c71”,“access-control-allow-origin”:“*”,“x-ratelimit-remaining”:47,“content-type”:“application/json; charset=utf-8”,“content-length”:“52”,“etag”:“W/"34-5UqF7y41lG/5a/xKi9pkoTT9y0w"”}},“responseTime”:114,“msg”:“request completed”}