"Model is not available"
See original GitHub issueI attempted to download this matterport model: https://my.matterport.com/show/?m=BPgscPGiQd3
However, when running the script again afterwards with the webserver, I get the message: “Oops, model not available” (and a link to their troubleshooting page)
Looking at the server.log, I don’t really see any 404s besides the favicon, which I doubt would be a big issue? (Btw - the favicon does show in the browser on the webserver)
2022-06-04 13:19:45 INFO Server started up
2022-06-04 13:19:48 INFO Redirecting /js/showcase.js => /js/showcase-internal.js as using our internal showcase.js file
2022-06-04 13:19:48 WARNING 404 error: /favicon.ico may not be downloading everything right
I just noticed, the web browser also had a 404 for “message File”
View in browser: http://127.0.0.1:8080
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET / HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /css/showcase.css HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /css/unsupported_browser.css HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /js/browser-check.js HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /js/showcase.js HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /?m=BPgscPGiQd3 HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET //api/v2/users/current HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] code 404, message File not found
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /favicon.ico HTTP/1.1" 404 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /js/136.js HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "POST /api/mp/models/graph HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /fonts/roboto-regular.woff2 HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /locale/messages/strings_nl.json HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:48] "GET /locale/strings.json HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:49] "GET /fonts/roboto-500.woff2 HTTP/1.1" 200 -
127.0.0.1 - - [04/Jun/2022 13:19:49] "GET /fonts/roboto-300.woff2 HTTP/1.1" 200 -
Any hints or tips? Or is this tool simply out of date?
Issue Analytics
- State:
- Created a year ago
- Comments:21 (3 by maintainers)
Top Results From Across the Web
z3.z3types.Z3Exception: model is not available - Stack Overflow
It throws the following exception: z3.z3types.Z3Exception: model is not available. All the variables (e.g. i2, i10, etc are Integer).
Read more >Model Is Not Currently Available | Revit 2019
The error may occur when two users are synching at the same time or a third party application/service interacting with the files prevents...
Read more >Internal error: Model not available for <project> #943 - GitHub
I'm using Eclipse IDE for Enterprise Java Developers (Version: 2019-09 R (4.13.0), Build id: 20190917-1200) with Buildship plugin (3.1.2.
Read more >Oops, Model Not Available - Matterport Help Center
I'm an administrator or collaborator trying to share the model · Is the model shared correctly? · Is the model archived? · Is...
Read more >Error: Model is not available on server - Riva
When i send request to riva server for Transcribe give me Error: Model is not available on server. How can i solve this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Mattio1990 - Just add this file
graph_posts/GetModelDetails.json
below and archive the virtual tour url again.https://github.com/rebane2001/matterport-dl/blob/bc8c2db9898bfaa9aee700052b3deacaa36595a7/graph_posts/GetModelDetails.json
You are free to leave it open until the PR is merged in (which will actually automatically close it). Slightly more likely a user seeing this error will see this if its open than closed. If not hopefully they just search:)
As for using this before merge, Paito’s method does likely work but we won’t officially support this fix until we get everything merged in (I would assume within the next week or two).