# Difficulty duplicating space - loads blank **URL:** \ **Category:** Spaces\ **Created:** [January 11, 2023, 8:13pm UTC](https://discuss.huggingface.co/t/difficulty-duplicating-space-loads-blank/29400 "2023-01-11T20:13:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bryanbblewis11](https://avatars.discourse-cdn.com/v4/letter/b/aeb1de/32.png) [@bryanbblewis11](https://discuss.huggingface.co/u/bryanbblewis11)\ **Post date:** [January 11, 2023, 8:13pm UTC](https://discuss.huggingface.co/t/difficulty-duplicating-space-loads-blank/29400/1 "2023-01-11T20:13:17Z")
I may be entirely doing something wrong, but I’ve been trying to duplicate this Space for some time now: > **[Custom-Diffusion + SD Training - a Hugging Face Space by nupurkmr9](https://huggingface.co/spaces/nupurkmr9/custom-diffusion)** > > Discover amazing ML apps made by the community The duplicated space is successfully created in my profile, as can be found here: > **[Custom-Diffusion + SD Training - a Hugging Face Space by bryanbblewis11](https://huggingface.co/spaces/bryanbblewis11/custom-diffusion1)** > > Discover amazing ML apps made by the community However, I notice that when I go to the “App” tab of my duplicated space, it loads entirely blank ~80% of the time. If I check the console logs, I tend to see .js errors. This continues to occur after I reboot the space, or factory reboot the space. On rare occasions, I’ll visit the space, and it will load (sometimes buttons won’t work properly, in that they’re unresponsive, etc). The source space seems to not have any of these issues whatsoever. I’m wondering if I’m doing something wrong when trying to duplicate this, or why I might be experiencing UI/app issues (even after upgrading the space to a suitable GPU)? ---
**Author:** ![radames](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/radames/32/28246_2.png) [@radames](https://discuss.huggingface.co/u/radames)\ **Post date:** [January 15, 2023, 12:57pm UTC](https://discuss.huggingface.co/t/difficulty-duplicating-space-loads-blank/29400/2 "2023-01-15T12:57:26Z")
Hello @bryanbblewis11, I went through the process of duplicating the original Space and assigning a T4 medium hardware, and after a few minutes, it built successfully. I’ve noticed that your Space uses A10G, so I’ve also tested with A10G small, and it built successfully. Perhaps it is worth trying **Factory reboot this Space** on your settings once more. Please let me know if that helps ---
**Author:** ![bryanbblewis11](https://avatars.discourse-cdn.com/v4/letter/b/aeb1de/32.png) [@bryanbblewis11](https://discuss.huggingface.co/u/bryanbblewis11)\ **Post date:** [January 15, 2023, 9:51pm UTC](https://discuss.huggingface.co/t/difficulty-duplicating-space-loads-blank/29400/3 "2023-01-15T21:51:18Z")
Thanks for the reply, @radames! At present, it looks like this is working properly! I did indeed try a Factory Reboot of the space a few times, but it almost seems like a browser problem, where the logs would show that the space was ready, but the space would be entirely blank. I did try in Safari and Chrome, to note. Anyway, this appears resolved at this moment, but I will re-open the issue is the problem returns. Thank you! ---
**Author:** ![radames](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/radames/32/28246_2.png) [@radames](https://discuss.huggingface.co/u/radames)\ **Post date:** [January 16, 2023, 3:07pm UTC](https://discuss.huggingface.co/t/difficulty-duplicating-space-loads-blank/29400/4 "2023-01-16T15:07:30Z")
hi @bryanbblewis11, I understand now. I’ve seen this issue before. It seems like a browser cache/DNS issue. Maybe @XciD has some extra insights here? ---
**Author:** ![agutfraind](https://avatars.discourse-cdn.com/v4/letter/a/f4b2a3/32.png) [@agutfraind](https://discuss.huggingface.co/u/agutfraind)\ **Post date:** [May 25, 2023, 5:17pm UTC](https://discuss.huggingface.co/t/difficulty-duplicating-space-loads-blank/29400/6 "2023-05-25T17:17:35Z")
A possible cause is iframe and CORS: Currently a private Space with streamlit gets loaded as an iframe from a different domain. The browser responds by blocking this iframe. In iOS and Safari you see a warning you about CORS, but for some reason there is no warning in Chrome. The workaround is to disable CORS protection - there is a checkbox in Safari and a commandline setting when launching Chrome.