-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Images from local cloud cannot be loaded #11
Comments
Maybe this can be solved with proxy setting, i will make PR of this @YuqiHuai (If it's CORS related 😆 ) |
@DOMINICQQQ What does console says when this happens? You can see the logs from developer tools of your browser. |
@KOREAN139 These two errors are the main ones. |
@DOMINICQQQ Did you download the assets from google drive as written in |
@DOMINICQQQ I just made a PR #12, can you check out the PR version and share the results? |
Hi! Not sure why this would happen ... Don't think it is related to CORS because this didn't happen before and I've talked with a few others previously ... Try to look at the following:
|
Hi. It looks like things are set up correctly. I cannot figure out why this is happening to you. Something about the server is wrong, but then I cannot explain why the front end shows any data at all. Can we schedule some time over the weekend to do a Zoom 1-on-1 meeting so I can look at your system and determine what is going on? |
Hi, when are you free this weekend, we can see what's going on, if it's not a hassle for you. |
To verify server container can access the asset files (maps, plugins, and previews), run
and verify In this project, the assets directory is mounted to a location in the Line 11 in 4746da1
Some Docker permission issues prevented this mounting to be done thus causing |
The issues was resolved. For some reason Docker could not mount directories in the Desktop directory, which caused the server container unable to access asset directory. |
I successfully built and deployed the docker container and the front end seems to be working well.
maybe something was wrong.
The text was updated successfully, but these errors were encountered: