Mixed Content Warning Chrome
The solution to the issue of environment variables defaulting back to http instead of https was to flush the cookies/cache in the browser.
This solution was generated by AI, if you think it's wrong, please report it.
sofl_
2 months ago
Hi, self-hosting plunk with docker compose.
I can spin up the instance completely fine but I keep running into this issue.
I have triple checked all my environment variables, API_URI, APP_URI to all include https:// in front instead of http: but it keeps defaulting back to http.
any call I make will be blocked by the mixed content error due to using http.
sofl_
2 months ago
The website itself is definitely being served over https as when I open it, it's in a https:// domain
driaug
2 months ago
Have you tried to recreate the deployment but with the environment variables ready to go. Plunk's front-end uses a Next.js app so we need to rewrite the variables with a script (https://github.com/useplunk/plunk/blob/main/deployment/replace-variables.sh). It is possible that the value is now stuck on http even though your env looks to be https.
driaug
2 months ago
I believe I had this same issue in the past and resolved it by completely deleting the deployment and recreating a new one with the right env variables
sofl_
2 months ago
I tried this one by looking through a github comment but this didn't work for me
sofl_
2 months ago
Idk why i didn't try incognito but it looks like it was being cached
driaug
2 months ago
Are you using a docker deployment or completely self-hostign the code?
sofl_
2 months ago
in the browser level
sofl_
2 months ago
so it works all good now after flushing cookies/cache twice (not sure why it didn't work the first time)
driaug
2 months ago
That is really interesting
driaug
2 months ago
I will save this conversation to our Pile. In case someone else bumps into it