Skip to content
Tibica Tibica Docs

t.Site FAQ

This page aims to answer common questions about t.Site, a Tibica application that simplifies the process of managing and deploying websites. If you have any additional questions or need help troubleshooting your website deployment, please contact us at help@tibica.io.

General Questions

Q: I can’t locate my website’s repository in t.Git. What should I do?

A: Repositories created through the t.Site application are organized within the cloud-site project in t.Git. Think of a project as a folder that can house multiple repositories. To locate your website’s repository, open the cloud-site project in t.Git.

Q: My website’s build status shows as ‘Failed’ in the History tab. How can I fix this?

A: To understand why your website build failed, click on the options menu (the “three dots” icon) next to your build status. This will allow you to view the build logs and identify the error’s cause. If you suspect the issue is not related to your code but rather with the underlying logic of t.Site, please reach out to us at help@tibica.io for assistance.

Q: The website built successfully, but not everything is functioning correctly. Can we access the final build folder?

A: Yes, you can access the final build folder. Navigate to the History tab and click on the options menu (the “three dots” icon) next to your build. Select the Get Artifact option to download the folder containing the final build of your website.

Q: What does it mean if my website build is marked as ‘Skipped’?

A: A ‘Skipped’ status indicates that the build process for your website did not commence. This could be due to multiple quick successive edits to your website, where only the latest changes are deployed, skipping earlier ones. It might also occur if there have been no code changes since the last successful build.

Q: After setting up my domain and clicking CONFIRM, I receive a ‘Not found’ error. What’s the issue?

A: DNS validation can take some time to process. Ensure that you’ve followed all setup instructions correctly and allow a few hours for changes to take effect. If the issue persists, consult the Troubleshoot DNS validation problems guide for common issues and solutions.