Hostinger Horizons: Troubleshooting

While building your project with Hostinger Horizons, you might occasionally come across small issues — but don’t worry! Most of them are easy to fix, and this article is here to guide you step by step.

If the issue doesn’t resolve on the first try, repeated attempts might fail to fix as well. Instead, we recommend following the suggested troubleshooting steps carefully to avoid unintended changes or complications.

For quick tips on troubleshooting prompt errors, check this video.

Or keep reading for more detailed step-by-step.

General troubleshooting steps

If no error messages appear, follow these steps, check Network Requests.

Open the site → Right-click → Inspect → Network.

Click the failing request and copy the URL, Payload, and Error. You can copy the error as text and ask Horizons to fix it.

You can combine all the information into one message for the AI.
Example: “When I log in and add a new customer, I get console error ‘Network request’. Network tab shows request to token?grant_type=password with payload { username: ‘test’, password: ‘test’ }, error { code: 400, error_code: ‘invalid_credentials’ }. Can you fix the issue?”

Pop-up ask Horizons to fix

However, 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.

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.

Make sure your domain is pointing to Hostinger servers.

If it’s not pointed, 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:

1. Navigate to the Websites list section on the left sidebar

2. Click on Change domain for the specific web application that you wish to connect to your domain

3. Follow the next steps on the hPanel:
   ​

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.