Hostinger Horizons is in its early stages and sometimes, you may face some errors that would stop you from proceeding with your project, and you can find in this article how to fix them.
When an error does not get fixed after the first try, there is a very high likelihood that second, third and so on trials will also fail.
Even further spamming this request to fix the error can cause the app to get broken even more in multiple spots.
Our product team is fully aware of those and working constantly to fix them and making our product even better 🚀
In general, the best practice to fix errors is to click on "Revert to this message" button to the message in prior to the one you started facing errors 💡
Table of Contents
General troubleshooting steps
Prompt to fix
Lost progress
High system usage
Pop-up ask Horizons to fix
Stuck on loading
Failed to deploy
Web app is deployed but offline
Additional help
General troubleshooting steps
General troubleshooting steps
Whenever Horizons spots an error to be fixed, a pop-up will be displayed inside your project:
Click on "Ask to Fix" to fix the issue and wait for a moment while it gets fixed. Have in mind it counts as one of the messages sent in the daily usage limit with the tool.
Take a screenshot of the error you face and send it in Horizons chat so that the AI itself would fix the issue
Go to ChatGPT or any other AI tool of your preference, ask for it to rewrite the prompt message you submitted following an AI language model, then copy and paste the prompt - generally, Horizons understands better AI generated prompt messages
Click on "Revert to this message" in which the first error happened and try to write in the prompt to the AI more context on what was broken in the request to fix the error:
Another option is to revert to a state where the app did not yet go into this error loop and to write the prompt that initially broke it in a simpler manner.
Have in mind that once you decide to revert a message, the other messages you sent after that are permanently lost and the reverted message, even if retracted, is still counted on your Horizons messages limit.
Prompt to fix
Prompt to fix
The Prompt to fix situation is applied to situations in which:
When you write a prompt to Horizons AI asking to fix the issue, and the issue doesn't get initially fixed
After writing this initial prompt to fix the error, you insist on prompting one or more times still requesting Horizons to fix the previous errors
Normally, when Horizons give errors, it is expected that the pop-up to fix the error via button will be clicked, and this is the best course of action:
Best practices to proceed:
Click on "Revert to this message" in which the first error happened and try to rewrite in the prompt to the AI more context on what was broken in the request to fix the error:
Another option is to revert to a state where the app did not yet go into this error loop and to write the prompt that initially broke it in a simpler manner.
Lost progress
Lost progress
The Lost Progress situation is applied to situations in which:
You had progressed with your Horizons project, then you did a prompt requesting a new action, it generated the new action result, but lost the previous project progress you worked on
Normally, when Horizons give errors, it is expected that the pop-up to fix the error via button will be clicked, and this is the best course of action:
Best practices to proceed:
Initially, you can prompt something referring to the lLost Progress you had following a better AI prompt reading format, such as:
"Enhance my current project by integrating [new element] without modifying the existing structure or content."
"Update only [specific section] by applying [new change], while keeping all other sections unchanged."
"Add [new feature or change] to my existing project without altering or removing any current content."
If after the step above the issue remains, then click on "Revert to this message" in which the first error happened (when the progress was lost):
Then, rewrite in the prompt with the requested new action following a similar format to the bullet point above.
High system usage
High system usage
The High System Usage situation is applied to situations in which:
You see a banner on the top right corner of your Horizons web application mentioning the system usage is high and for you to try again later:
Proceed as below:
Try doing the same action a couple of times and repeating it again, it should be able to work after some trials
If it persists after that, please try again in a couple of hours as there are a lot of people using Horizons, and due to its popularity, we are working on handing all this demand.
If after a few hours the issue persists, reach out to our Customer Success team: How to contact Hostinger support
Pop-up ask Horizons to fix
Pop-up ask Horizons to fix
Normally, when Horizons give errors, it is expected that the pop-up to fix the error via button will be clicked, and this is the best course of action:
Best practices to proceed with this:
Click on "Revert to this message" in which the first error happened and try to rewrite in the prompt to the AI more context on what was broken in the request to fix the error:
Another option is to revert to a state where the app did not yet go into this error loop and to write the prompt that initially broke it in a simpler manner.
Stuck on loading
Stuck on loading
The Stuck on Loading situation is applied to situations in which:
The right screen for generated preview for Horizons keeps on loading, but "freezes" on this and nothing happens
You see the "loading" sign Horizons preview screen but you are unable to take any actions inside Horizons tool
The errors basically looks like the example image below:
In order to fix this:
Click on the Refresh button on the top corner of the preview screen:
If after this you are unable to achieve the expected result, reload the whole browser windows tab, as in the example below using Google Chrome:
If the situation persists after this, take a console screenshot of the error faced and reach out to our Customer Success team: How to contact Hostinger support
To take a console screenshot, follow these steps:
Open the Console tab in your browser:
For Chrome/Firefox on Windows: CTRL+SHIFT+J
For Chrome/Firefox on Mac: COMMAND+OPTION+J
For Safari on Mac: COMMAND+OPTION+C
Reload the page and repeat the steps to catch the same error.
Take a screenshot of the console errors and send it to our support:
- Screenshotting with Windows
- Take a screenshot on your Mac
- Lightshot extension for screenshots
Failed to deploy
Failed to deploy
The Failed to deploy website situation is applied to situations in which:
You tried to deploy your web application and got the an error banner on the top right corner of your Hostinger Horizons tool as the image below:
In order to fix this:
Normally, if you face an issue with the display of your web application such as no preview displayed (white blank result) or stuck on loading (as the image below), it's expected that the deploy error banner will be displayed:
If your web application preview is working as expected and you see the deploy banner error, take a console screenshot of the error faced and reach out to our Customer Success team: How to contact Hostinger support
To take a console screenshot, follow these steps:
Open the Console tab in your browser:
For Chrome/Firefox on Windows: CTRL+SHIFT+J
For Chrome/Firefox on Mac: COMMAND+OPTION+J
For Safari on Mac: COMMAND+OPTION+C
Reload the page and repeat the steps to catch the same error.
Take a screenshot of the console errors and send it to our support:
- Screenshotting with Windows
- Take a screenshot on your Mac
- Lightshot extension for screenshots
Web app is deployed but offline
Web app is deployed but offline
If you are using Hostinger Horizons and wants to get your web app project live and working, that are some steps to ensure this will happen, as below:
Make sure your domain is pointing to Hostinger servers:
To point your domain name to Hostinger, please log into your domain provider's website, and find your domain nameservers settings. Then, delete all the current nameservers and insert the following two:
- ns1.dns-parking.com
- ns2.dns-parking.com
You can also point it following an A record procedure instead of NameServers. You can find all details on how to point a domain to Hostinger here.
Ensure that your application is fully ready and finished, and that all functions inside of it are working as expected.
Double-check if you already deployed your website:
Finally, verify if your domain is connected to your web application project:
Navigate to the Websites list section on the left sidebar
Click on Change domain for the specific web application that you wish to connect to your domain
Follow the next steps on the hPanel:
Additional help
Additional help
If you need additional help, reach out to our Customer Success team: How to contact Hostinger support.
Additionally, explore the most common mistakes users make when developing web apps with Hostinger Horizons. By learning from these examples, you’ll be able to create functional, efficient, and well-structured apps from the start.