I'm having the same error as you on Chrome, but it seems to work properly for me on Firefox. The other programmers are asleep (it's late for all of us) and I'm actually heading to bed now too so I'm unable to troubleshoot it right now. But we'll look into it tomorrow if the problem persists. For now as a temporary solution I recommend trying Firefox or another browser if you're able, since I've only encountered this in Chrome so far.

Are you sure you were still logged in after you cleared your cache? It might have shown you that if you got logged out by the cache clearing. And are you sure you cleared your cache correctly? We actually double-checked our server configuration, based on the specific error messages given by the broken images, but the configuration looks correct on our end. If I were you I'd double-check that you cleared the cache correctly, or just wait until you're on Safari again if you're unfamiliar with Chrome.

For the record, our servers haven't had issues with this holiday at all so far :) The usual problem we have during holidays is lag caused by the increased server strain, but none of that has shown up so far. The problem reported in this thread is unrelated and specific to Lumi trees, and seems to be more related to browser cache than anything on our end :v

Hey everyone, good news! Grace () was able to investigate this today and we think she figured it out! She just pushed a fix which will be finished uploading within the next few minutes. If you're on Chrome and have this issue, please let me know if it seems to be good now :D

Has it shown up correctly for you at all so far? I have a suspicion your issue might actually be unrelated to the others because of China's internet restrictions. Are you/can you try using a VPN? Can you share a screenshot of what it looks like for you on Chrome after clearing your browser cache?

Hey everybody, if you are still experiencing this error in Google Chrome, please make sure you are viewing the https version of Subeta. In your address bar, if the URL begins with http simply change it to https to view the correct version. If this does not fix your issue, please follow the steps below to help us debug it further:

1. Clear your browser cache again (I'm so sorry)
2. Reload the tree page and screenshot what you see.
3. Open the Javascript console by pressing Ctrl+Shift+J
4. Copypaste or screenshot any messages you see in the console.

Then, follow these steps to get your exact Chrome version number:

1. In the address bar, go to chrome://version
2. Copy the first four lines (Google Chrome, Revision, OS, and JavaScript)

I'll need the following information that you got from the steps below:

1. The screenshot of the tree page (so I can see what specific elements are failing for you)
2. The console output
3. The chrome version information

Thank you SO MUCH for your patience and help in debugging this issue. We think the CORS error is resolved, and we're having trouble reproducing the error again on our end, so this data will help us figure out what exactly is going on.

I think any tree issues right now are related to the server issues we are having today, rather than the usual chrome error this topic was about. So please wait for now, until there is more news from us about the server issues, since it is possible that resolving them will resolve this as well.