client_id
signaltech opened this issue · comments
successfully deployed the server
on local PC client_id is generated after login
but when deployed on VPS the client_id is empty plus modified settings don't seem to be saved
Are you trying to use it via IP address?
If so HTTPS cookies are not allowed, hence we recommend using it with domain
both with IP and with domain pointing to the IP
@lakhansamani any solution?
While accessing the app in browser pls use domain that will help
@lakhansamani Yeah I am using domain is there a HTTPS requirement(using domain but no SSL installed in the server so just HTTP)
HTTP should be fine however do u see errors in network request. Somehow it is not allowed to set cookies and that is creating problems
@lakhansamani in the inspection console there is this error
Environment-Q72GB73P.js:1 Uncaught (in promise) TypeError: Cannot read properties of null (reading '_env')
at Environment-Q72GB73P.js:1:33481
at Generator.next ()
at a (chunk-I2F2WLKQ.js:1:1222)
@signaltech can you try the latest version
Thanks
@lakhansamani sorry I didn't respond. today I pulled the new changes and clean build but the error remains.
thank you
upon testing on firefox here is the console output(not shown in chrome)
users
Some cookies are misusing the recommended “SameSite“ attribute 2
Cookie “authorizer-admin” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite graphql
Cookie “authorizer-admin” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite graphql
Cookie “authorizer-admin” has been rejected because a non-HTTPS cookie can’t be set as “secure”. graphql
Cookie “authorizer-admin” has been rejected because a non-HTTPS cookie can’t be set as “secure”.
install SSL certificate now it is working with HTTPS. thank you