This is the help page for Deco My Tree at decomytree.sbti-test.com. It is unrelated to other websites with the same name and is not an official status page for any website. Check the domain in your address bar first. A tutorial for another Deco My Tree can show different login methods or recovery steps from the ones available here.
Before clearing browser data or switching devices, save any draft and keep your private management link safe. Clearing site data can remove your guest identity and unfinished work. A public tree link lets people visit; it does not prove ownership or restore management access.
Find the problem you can see
Keep the exact error message on screen if possible. A missing tree, a locked letter, a rejected send and a failed Google sign-in are different problems. Repeatedly pressing Send or creating another tree will not solve all of them. Start with the matching case below, then use Feedback or Contact on this page if the suggested step does not help.
These checks describe this site's behavior. They do not tell you whether another service is down. If your original tree is on a different domain, return to that site's own help or support. Never enter a password from one website into another just because both pages use the name Deco My Tree.
Common Deco My Tree problems and what to do
The link does not open, or the tree is not found
A tree URL includes a short identifier after /t/. A shortened, mistyped or incomplete link can point to no active tree. A missing-tree response is different from a network error: the server was reached, but it did not find an active tree at that address.
Copy the full public link again from the original message, without adding punctuation from the surrounding sentence. Ask the owner to share it again if necessary. If you are the owner, try the browser that created the tree or the Google account already bound to it. A bare /recover address cannot find a tree for you; recovery needs the complete private management link, including its token.
I can see ornaments, but cannot read the wishes
The tree owner normally reads received wishes from Christmas Day in the time zone saved when the tree was created. Before then, a letter can be locked even though its ornament is visible. Pro alone does not open letters early. An author can read their own sent wish with the same identity; other visitors can read only public wishes after reveal.
Check the tree's opening information and whether you are using the owner's identity. A separate early unlock, when available and completed, applies to the owner and its stated letters. It does not make private letters readable to everyone. If the problem appears while reporting a wish, not_readable means reporting is not permitted for that letter; it is not the error for waiting until Christmas.
Sending fails or the tree is not accepting wishes
Receiving closes at the start of New Year in the tree's saved time zone. The owner can also turn off receiving sooner. A not_accepting message can therefore be expected behavior. Rate-limited sending, blocked content and a failed network request have other causes and should be handled separately.
For a closed season or a tree that is not accepting, ask the owner rather than retrying the same send. For rate_limited, wait before trying again. For content_blocked, edit the message or signature and remove the text identified as unsuitable. For a network error, preserve your draft, check your connection and reload when it is safe. After reconnecting, check whether the wish already appeared before sending again. Do not assume a spinning button proves that nothing was saved.
I cannot send a wish to my own tree
This site rejects sending from the identity that owns the destination tree. The corresponding error is own_tree. Signing out just to bypass that rule is not a repair. A separate self_wish error applies when replying to your own wish; it does not describe every failed send.
Share your public tree link with a friend who wants to leave a wish, or open a friend's tree to write to them. If you unexpectedly see this error on someone else's tree, check which tree URL you opened and which identity is active. Use Feedback if those details do not match what the page shows, without sharing your private management link.
Google sign-in fails, or verification fails
This site supports Google sign-in. An auth_failed message concerns the sign-in flow. A captcha_failed message concerns the separate human-verification challenge used for guest actions. Completing one does not mean the other succeeded. Some older tutorials show email and password forms belonging to other services.
For a sign-in failure, return to this site and start Google sign-in again, choosing the account already bound to your tree. For a verification failure, reload the challenge, let it finish and retry the action. You can create a tree without a Google account. First-time guest sending depends on the site's setting; if the page asks you to sign in, use Google rather than searching for a password-reset form here.
My tree disappeared after switching devices or clearing site data
A guest tree can still exist even when the new browser does not recognize you as its owner. Your public tree URL is not a management credential. Opening it on another device may show you the same visitor view that a friend sees, with no owner controls.
Use the complete private management link you saved, or sign in to the Google account you previously bound. If the original guest identity still works in another browser, open the tree's share dialog and retrieve the private management link there before clearing anything. Keep that link private. If the identity, management link and bound Google access are all lost, we cannot promise recovery; tell support what happened without posting tokens or passwords.
The page behaves differently inside Instagram, LINE or another app
An in-app browser can handle cookies, sign-in redirects and installation differently from your usual browser. Our installation and notification guides distinguish those environments. In particular, notification support in an embedded browser should not be taken as proof that the tree itself is broken.
Copy the public tree link and open it in Safari or your usual system browser, as the existing guide recommends. If you are moving your own guest tree, save the private management link first, since a different browser may have a different identity. Keep your draft before leaving the current page. Use this as a compatibility check; it does not guarantee that a separate service or a closed tree will start accepting wishes.
Still stuck? Send the details that help us reproduce it
Use Feedback below or open Contact. Include the public page URL, the exact visible error, your browser and device, and the action that led to it. Say whether you are visiting, sending a wish, or managing your own tree. If you tried another browser, mention whether the result changed. Tell us whether you still have access in the browser where you made the tree.
Leave out your private management token, Google credentials and the contents of a private letter. If you attach a screenshot, crop or cover them first. Support cannot repair a tree on a different domain, and a contact request does not guarantee recovery when all ownership access is lost.
This page is a troubleshooting guide, not a live outage monitor. A single missing tree or a locked letter does not establish an outage. Check the domain and exact error, then follow the relevant steps above. Use Feedback or Contact if you can reproduce a problem on this site.
Will clearing cookies fix my tree?expand_more
Do not clear them as your first step. A guest identity and unfinished drafts depend on browser data. Save your private management link or bind to Google while you still have access. Otherwise you could remove the access you need to manage a tree that still exists.
Can I recover my tree from its public link?expand_more
A public link alone does not restore ownership. Use a saved private management link containing its token, or sign in to Google if the tree was already bound to that account. If the original browser still recognizes you, retrieve the management link from the share dialog before changing devices.
Do I have to subscribe to Pro to read my messages?expand_more
The normal reveal does not require Pro. Owners read received wishes when their tree's reveal time arrives. Early unlocking is separate from Pro and follows the scope shown for that unlock. Private wishes remain unavailable to unrelated visitors even after reveal.
Return to your tree when the problem is resolved
If you already have a tree, use the button to return to it. If you are new here, create a tree and save its private management link before sharing the public one.