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
Was trying to find solution for few days. This is when running the development or production build(dist). I am using apache server.
I tried to follow some webpack.config output similar issue but couldn't find the right solution.
Hope to get some help here. Thanks.
Uncaught (in promise) Error: Error retrieving auth token
at ChatContainer.js:206
IBMPlexSans-Regular-Latin1.woff2:1 Failed to load resource: the server responded with a status of 404 (Not Found)
/api/session:1 Failed to load resource: the server responded with a status of 404 (Not Found)
192.168.64.2/:1 Uncaught (in promise) SyntaxError: Unexpected token < in JSON at position 0
IBMPlexSans-Regular-Latin1.woff:1 Failed to load resource: the server responded with a status of 404 (Not Found)
IBMPlexSans-Regular-Latin2.woff2:1 Failed to load resource: the server responded with a status of 404 (Not Found)
IBMPlexSans-Regular-Latin2.woff:1 Failed to load resource: the server responded with a status of 404 (Not Found)
IBMPlexSans-Regular-Latin3.woff2:1 Failed to load resource: the server responded with a status of 404 (Not Found)
IBMPlexSans-Regular-Latin3.woff:1 Failed to load resource: the server responded with a status of 404 (Not Found)
IBMPlexSans-Regular-Pi.woff2:1 Failed to load resource: the server responded with a status of 404 (Not Found)
IBMPlexSans-Regular-Pi.woff:1 Failed to load resource: the server responded with a status of 404 (Not Found)
Regards,
Jayson
The text was updated successfully, but these errors were encountered:
Hello!
Was trying to find solution for few days. This is when running the development or production build(dist). I am using apache server.
I tried to follow some webpack.config output similar issue but couldn't find the right solution.
Hope to get some help here. Thanks.
Regards,
Jayson
The text was updated successfully, but these errors were encountered: