You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the app locally using any nox commands - but most importantly, using nox -s "fides_env(test)" or fides deploy, there is a FIDES_PRIVACY_CENTER__FIDES_API_URL config var we default to http://localhost:8080/api/v1
This works fine for client-side calls from the browser (both Privacy Center client and the Fides.js client), but these fail when the same call is attempted from the server since it tries to connect to localhost from within the privacy-center docker container.
Should perform all the server-side initialization and return a fides.js bundle with geolocation and experience prefetched 👍
Environment
Version: 2.17.0rc1
Additional context
We might need to support an optional FIDES_PRIVACY_CENTER__SERVER_SIDE_FIDES_API_URL (or similar) to workaround this, as I can't think of a nicer way to get the client & server to agree on the API location when they are technically on different networks.
The text was updated successfully, but these errors were encountered:
Bug Description
When running the app locally using any
nox
commands - but most importantly, usingnox -s "fides_env(test)"
orfides deploy
, there is aFIDES_PRIVACY_CENTER__FIDES_API_URL
config var we default tohttp://localhost:8080/api/v1
This works fine for client-side calls from the browser (both Privacy Center client and the Fides.js client), but these fail when the same call is attempted from the server since it tries to connect to
localhost
from within theprivacy-center
docker container.Steps to Reproduce
nox -s "fides_env(test)"
Internal Server Error
Expected behavior
Should perform all the server-side initialization and return a
fides.js
bundle withgeolocation
andexperience
prefetched 👍Environment
Additional context
We might need to support an optional
FIDES_PRIVACY_CENTER__SERVER_SIDE_FIDES_API_URL
(or similar) to workaround this, as I can't think of a nicer way to get the client & server to agree on the API location when they are technically on different networks.The text was updated successfully, but these errors were encountered: