Cookies not being generated except on localhost #471
-
|
I'm very new to Javascript/web development, so this may be an obvious issue. I've set up LibreChat and can access it both from a localhost address and from the public IPv4 address. When I login using the localhost address, a cookie is created and saved to the browser, such that when I refresh the page, I am still logged in. However, when I log in using the public IPv4 address, a cookie is not created, and so if I refresh the page, I am forced to log in again. Is there some setting I am missing in one of the two .env files or elsewhere? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 13 replies
-
|
@itrase could be a couple things in your local environment. how are you accessing the address in your browser? are you using |
Beta Was this translation helpful? Give feedback.
-
|
and login state is persisted |
Beta Was this translation helpful? Give feedback.
-
|
Last thing, you would need to log in first for each endpoint. Your localhost cookies won't persist into the public IP address |
Beta Was this translation helpful? Give feedback.
-
|
We aren't using google login - this is a small internal test, so we don't really have the ability to stand up https. I've just been running the app by running "docker-compose up" on an EC2 instance and connecting from there (so no ngrok or anything else). As far as I know, chrome is not blocking 3rd party cookies - it's set to only block cookies in Incognito. |
Beta Was this translation helpful? Give feedback.
-
|
what is your node env in the ec2 instance? The cookies are set to secure in a production environment and this is probably what's happening. See this for more info: https://stackoverflow.com/questions/73752871/aws-ec2-instance-does-not-set-cookie-when-sent-by-node-server-running-inside-it You said you're using docker. the default NODE_ENV on the compose file is 'production' edit this line in your docker-compose.yml file |
Beta Was this translation helpful? Give feedback.
-
|
Yes, setting the NODE_ENV to development in the docker-compose.yml worked - thank you so much!! |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Thanks for reaching out and for trying out the project! Hope it serves your purposes |
Beta Was this translation helpful? Give feedback.
-
|
i want to leave it in production and enable ssl, is that the way to have cookies working? if so, where can i enable ssl, i have the certs |
Beta Was this translation helpful? Give feedback.
-
|
I haven't done this but my guess would be you need to edit api/server/index.js https://stackoverflow.com/questions/11744975/enabling-https-on-express-js |
Beta Was this translation helpful? Give feedback.
-
|
got it working just used nginx ssl proxy to fwd to localhost
…On Fri, Jul 14, 2023 at 3:14 PM Danny Avila ***@***.***> wrote:
I haven't done this but my guess would be you need to edit
api/server/index.js
https://stackoverflow.com/questions/11744975/enabling-https-on-express-js
—
Reply to this email directly, view it on GitHub
<#471 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APSAFWNAC5EPRL7FYFUDDSTXQEZ3RANCNFSM6AAAAAAZBAGRCE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
what is your node env in the ec2 instance? The cookies are set to secure in a production environment and this is probably what's happening. See this for more info: https://stackoverflow.com/questions/73752871/aws-ec2-instance-does-not-set-cookie-when-sent-by-node-server-running-inside-it
You said you're using docker. the default NODE_ENV on the compose file is 'production'
edit this line in your docker-compose.yml file
- NODE_ENV=productionto- NODE_ENV=development