Skip to content

Uncaught (in promise) TypeError: e.response is undefined #958

Answered by niklasweimann
medoedoff asked this question in Q&A
Discussion options

You must be logged in to vote

Okay... After some testing it turned out that this error occurs when API_BASE_URL is not set properly.

For others who come to this issue:
I am using an nginx proxy which redirects all traffic from example.com/api/ to dtrack-server:8080/api/ and example.com/ to dtrack-frontend:8080 where dtrack-server and dtrack-frontend are docker containers within a network. For the frontend to work properly you need to set API_BASE_URL to https://example.com/. And you will need to wait until the dtrack-server is fully started otherwise you will also get the error described above.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@medoedoff
Comment options

@niklasweimann
Comment options

Answer selected by medoedoff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants