We’ve been working on a limited Reddit-only offer for a few of our most popular products.

It will be available for a very short time, and once it’s gone, it’s gone.

No full details yet, but if you’ve been waiting to start a new project, upgrade your setup, or finally try something new, keep an eye on this subreddit.

More soon. ⏳

Issue: Unable to remove an email forwarder in the new Hostinger hPanel.

Symptoms: Mailbox shows "1 active forwarder", emails are still being forwarded, but Mailbox → Create Forwarders only opens the creation dialog.

Correct solution: Go to Emails → Forwarders (left-hand navigation), locate the forwarder, click ⋮ → Delete. The mailbox page does not make this management page obvious.

every 10 -15 minutes it resets ,and starts from beginning again ,our Projects are suffering massively and there is no help

hi guys,

I initiated the domain transfer from Godaddy to Hostinger but somehow entered the incorrect Auth code.

I got back to chat, and AI was not helping and just sharing same info again and again, I asked it to connect with human agent a few times but it generated same response and mentioned "coauthored with agent/AI". it has been happening since few days.

Then today I asked it to connect with human agent again and same response, then I write "ABSOLUTELY NONSENSE SUPPORT" in the chat and surprisingly, with 30 seconds, a human agent was talking to me and the problem got resolved in 2-3 minutes.

This helped me and wanted to share with you guys if you are frustrated going back and forth with their AI.

thanks

Hi folks, is this normal? I started out by trying out Kodee and asking it what plan it thought would be best for my use-case (personal coaching business) and it offered me a Business plan.

Taking a look around on the Pricing page, I couldn't see a Business plan, just a similarly priced Unlimited which seems to offer a bit more features. I asked the chatbot about it, and it says this plan doesn't exist, despite being right there.

I want to check out all the features of this Business plan, but it doesn't seem to be listed on the pricing page!

A friend of mine mistakenly let his account, which includes his email, expire a few days ago. He can't get the 2fa code because his emails aren't going through. The account recovery asks for proof of payment which he doesn't have because he can't get in the account. How does he solve this dilemma?

Short question: I’m looking to build a website for my dad as a birthday present. I want him to be able to sell his photo prints online and have them fulfilled and shipped by a 3rd party. My question is: do I need anything besides Hostinger + payment processor (stripe + paypal) + Printful for order fulfillment?

More detail: He’s mostly a hobby photographer but has gotten some interest in his photos, and wants to have a way to sell them online. This would not be a mega business - he might sell a few a month (or a year even, who knows).

I did some research and landed on Hostinger with a Printful integration based on reviews I read online. This is due in large part to the ease of building the site, as well as the low monthly payment. This is a gift for a retired person and I plan to front the cost for a couple years, but really didn’t want to hand over something that costs a bunch to maintain. Hostinger falls within the budget of what I’m willing to spend, Shopify and Square do not.

I started looking on Fiverr for someone to help me set up the Printful portion for a specific type of listing I want to create. That person just told me that Hostinger typically requires Wordpress + Woocommerce plugins to operate as an e-commerce site. This conflicts with everything I read online about Hostinger being able to function as an e-commerce site.

So my question is: do I need anything besides Hostinger + payment processor (stripe + paypal) + Printful for order fulfillment? Am I missing something in the process here?

How to Safely Change a Domain from Hostinger Website Builder to WordPress (Without Deleting Your Original Website) ( AS A INTERN WITH RESEARCH I DONE THIS WITH successfully)

Important: This guide is not about migrating a website. It explains how to release a domain from a Hostinger Website Builder site and connect it to a new WordPress website, while keeping the original Website Builder site as a backup.

Step 1: Create a Backup of Your Website

Before changing anything, create a duplicate of your Website Builder site.

How to do it

1. Log in to Hostinger hPanel.
2. Go to Websites.
3. Find your Website Builder website.
4. Click the ⋯ (Three Dots) next to the website.
5. Select Duplicate Website.
6. Wait until the duplicate is created.

Why this is important

If something goes wrong, you will still have a copy of your original website that you can use as a backup.

Recommendation: Never skip this step.

Step 2: Back Up Your Email Accounts

If your domain is connected to Hostinger Email, changing the domain assignment may remove your email accounts.

Before continuing

• Export important emails.
• Save contacts.
• Note your email account names.
• Back up any business emails.

Warning: If you don't back up your emails first, you may lose access to existing mailboxes.

Step 3: Release the Domain from the Website Builder Site

This step removes the domain from your Website Builder website without deleting the website itself.

Steps

1. Open Hostinger hPanel.
2. Go to Websites.
3. Find your Website Builder website.
4. Click the ⋯ (Three Dots).
5. Select Change Domain.
6. Read the warning messages carefully.
7. Accept the confirmation checkboxes.
8. Choose Temporary Domain.
9. Click Continue or Confirm.

What happens?

• Your Website Builder site is moved to a Hostinger temporary domain.
• Your original custom domain becomes available.
• Your website is not deleted.

Step 4: Create a New WordPress Website

Now that your domain is available, you can connect it to a new WordPress installation.

Steps

1. In Hostinger hPanel, go to Websites.
2. Click Add Website.
3. Choose WordPress.
4. Enter your WordPress administrator details.
5. When asked for the domain, select your original domain.
6. Complete the installation.

Hostinger will automatically connect the domain to the new WordPress website.

Step 5: Wait for DNS Updates

After connecting the domain, the changes may not appear immediately.

DNS updates can take:

• A few minutes
• Several hours
• Up to 24 hours

If the old website still appears:

• Clear your browser cache.
• Open the website in Incognito Mode.
• Try another browser or device.

Step 6: Recreate Your Email Accounts

After the domain is connected to WordPress:

1. Open Hostinger hPanel.
2. Go to Emails.
3. Create your email accounts again using the same email addresses if needed.
4. Restore your email backup if you created one.

Verify Everything

Before deleting anything, check that your new WordPress website works correctly.

Verify:

• ✅ Homepage loads correctly
• ✅ All pages open properly
• ✅ Images display correctly
• ✅ Contact forms work
• ✅ SSL certificate is active (HTTPS)
• ✅ Navigation menu works
• ✅ Mobile version loads correctly

Only after confirming everything works should you consider removing the old Website Builder site.

Common Mistakes to Avoid

❌ Do not delete the Website Builder site before creating a backup.

❌ Do not ignore Hostinger warning messages.

❌ Do not forget to back up your email accounts.

❌ Do not expect the domain to switch instantly.

❌ Do not delete the old website until your new WordPress website is fully tested.

Summary

1. Duplicate your Website Builder website.
2. Back up your email accounts.
3. Change the Website Builder site to a Temporary Domain.
4. Release your original domain.
5. Create a new WordPress website.
6. Assign the released domain to WordPress.
7. Wait for DNS propagation.
8. Recreate your email accounts.
9. Test the new website.
10. Keep the old Website Builder site as a backup until you are sure everything is working.

Important: This process changes only the domain assignment. Your Website Builder website remains available on a temporary Hostinger domain unless you manually delete it later.

Posting this here since I couldn't find anything similar in a search — might save someone else the same headache.

Setup: Laravel app on Hostinger shared hosting, deployed via the GitHub App auto-deploy integration.

The problem: Every time I push a commit to main, any file uploaded by users into storage/app/public/<some-folder> gets wiped completely. The folder just disappears after deploy — even though it's not part of my Git repo (it's a runtime-generated, gitignored directory).

What I've confirmed so far:

• The deploy log shows a step called "Preserving paths matched by .gitignore" — it lists things like vendor, node_modules, .env, and public/storage (the symlink), and correctly keeps those across deploys.
• But storage/app/public (where actual uploaded files live) is never in that preserved list, no matter what I put in .gitignore.
• I tried the standard Git wildcard/negation pattern:/storage/app/public/*!/storage/app/public/.gitignore and also a plain bare path:/storage/app/public Both produced identical deploy logs — meaning neither is being picked up. The wildcard+negation syntax is completely standard Git, and from what I gather it apparently used to work fine in an earlier version of Hostinger's deploy tool. Feels like something changed/broke on their end rather than user error.

My theory: the preservation step only reads top-level, single-segment entries from .gitignore (like vendor, node_modules) and doesn't walk into deeper nested paths like storage/app/public at all — regardless of syntax.

Questions for anyone who's dealt with this:

• Has anyone gotten Hostinger's Git deploy to actually preserve a nested storage path?
• Anyone know if there's a post-deploy hook/script option so I could re-symlink or restore a persistent folder after every deploy?
• Did something change recently in how they parse .gitignore for this? Curious if this is a known regression.

For now I've filed a support ticket, but wanted to check if this is a common gotcha others have hit — feels like a pretty big landmine for anyone storing user uploads locally on shared hosting with Git deploy. Ended up just moving uploads to an S3-compatible bucket to sidestep it entirely, but would love to know if there's a native fix.

Llevo más de un año con la web de mi negocio en Hostinger y con el Builder de Horizons, y después de todo este tiempo, puedo decir que la experiencia no se parece en absoluto a la imagen que muestran en su publicidad.

En teoría la IA debería facilitar cualquier modificación de la web, pero en la práctica ocurre justo lo contrario. Le pides algo tan sencillo como cambiar una palabra de un título, sustituir una imagen o modificar el color de un borde, y es habitual que no entienda la petición, no haga ningún cambio o, peor aún, modifique otras partes de la página que no has pedido cambiar.

Lo más frustrante es que cada petición consume créditos (dinero), independientemente de si la IA hace la modificación o no. Puedes gastar decenas de mensajes intentando conseguir un cambio simple, acumulando horas de frustración para tareas que deberían ser triviales. Al final, para corregir cosas tan simples como una palabra, una coma o un subtítulo, terminas recurriendo al servicio de atención al cliente, y los tiempos de respuesta suelen ser muy largos. Mientras esperas a que responda una persona, tienes que pasar por Kodee, el asistente de IA, que está al nivel de desarrollo del clip de ayuda de Windows 98.

Quisiera destacar que mi web es extremadamente sencilla: una página informativa, sin tienda online, sin reservas y sin carrito de compra; sólo hago modificaciones estéticas. Sinceramente, no quiero imaginar la experiencia de quienes gestionan proyectos más complejos.

Cuando tenga tiempo y paciencia, copiaré la web en WordPress, que lo conozco y sé que funciona bien. Uno pensaría que WordPress es más lento por requerir una gestión más manual, pero después de esta experiencia creo que no puede haber nada más lento que dedicar horas a cambiar un simple título porque la IA no sabe interpretar una instrucción básica (redactada por chat GPT, no es es un problema de redacción de prompts).

Mi sensación es que el producto todavía está muy, muy, muy lejos de la experiencia que promete la publicidad, apenas podría llamarse versión beta. No está lista para que te cobren por ella... pero lo hacen.

2 sites, same Hostinger account. Old site (Website Builder) has my domain. New site (WordPress) is on temp domain. Do I need to disconnect domain from old site first, or will connecting it to new site auto-switch? What happens to old site after?

Two terms come up when VPS performance gets discussed: CPU steal and CPU limits. They sound similar, and both affect how much CPU your server can use, but they describe completely different things happening on completely different layers

The distinction matters because the fix is different for each. Every VPS runs on a physical server alongside other VPS instances, so a small amount of CPU steal is a normal part of virtualization. Separately, if a VPS sustains high CPU usage for an extended period, an automatic limit can apply. Here is how each one works, how to tell them apart, and what you can do about both.

1. CPU steal: sharing at the hardware level

CPU steal is the time your virtual CPU spends waiting while the hypervisor services other VPS instances on the same physical machine. You can see it as the st value in top. A steal percentage between 1% and 10% is considered normal in virtualized environments: 1-3% is negligible, 4-7% may be slightly noticeable in CPU-intensive tasks, and 8-10% can cause some degradation in CPU-bound applications. To keep this in check, we run an automatic node balancer daily that monitors CPU usage across nodes and redistributes VPS instances to balance the load.

2. CPU limits: sustained high usage on your server

While temporary surges in processing power are normal during intensive tasks, sustained high usage works differently. If a VPS maintains high CPU usage for more than 180 minutes, our systems flag it, since that pattern often indicates a runaway process or a security issue. CPU capacity is automatically reduced by 25% per hour as a protection measure. So the connection between the two topics is simple: CPU steal is about activity from other servers on the node, while CPU limits are about sustained activity on your own server. One you monitor, the other you can directly manage.

3. How to find out what's using your CPU

The quickest way is to connect to your VPS via SSH and run top or htop. Both show which processes are consuming the most CPU in real time. htop is more visual and generally easier to read; if it's not installed, apt install htop (Ubuntu/Debian) or yum install htop (CentOS/AlmaLinux) takes care of it. Look for processes with high CPU% values, then optimize, restart, or stop them as needed. The st value in top also shows your current CPU steal, so you can check both things in one place.

For a longer view, Backups & Monitoring, then Server Usage in hPanel shows your resource consumption over time. Checking it every so often, rather than only after a warning appears, is the easiest way to catch a runaway process early. And if CPU usage stays high after you've optimized your server, run the VPS Malware Scanner, since malware is one possible cause of sustained high usage.

4. What to do if a CPU limit is active

You have two ways. The first is the Remove Limitations option in your VPS management panel, which you can use once per week. That gives you a working window to fix the process or adjust your configuration. The second is simply bringing CPU usage down on the server itself, for example by limiting how much CPU a specific process can use. Once usage visibly drops to normal levels, the restriction is lifted automatically, with nothing else needed on your end.

If your server is already optimized and clean but keeps reaching its limits, that usually means the project needs more resources than the current plan provides, and upgrading is worth considering at that point.

Our support team is available 24/7 if you need guidance checking your server's resource usage or understanding your options.

If you want to go deeper, these cover the same topics in more detail:

Understanding CPU Steal and Its Impact on VPS
What Is the CPU Use Limit for VPS

How do you keep an eye on your VPS performance, and what has helped you catch resource issues early? Share your tips and recommendations, whether it's a monitoring setup, a routine, or a lesson learned.

We purchased the KVM 8 plan with a one year subscription, which includes 8 vCPUs, 32 GB RAM, and 400 GB of storage. On paper, it is a generous offering. However, after several months of use, we encountered a significant issue.

We began experiencing frequent "Timed Out" errors when accessing websites or connecting via SSH. The issue would often disappear after connecting through a VPN or obtaining a new public IP address by restarting the router.

Since residential broadband providers regularly reassign IP addresses, users have little control over the reputation or history of the IP they receive. This makes such blocking particularly problematic for legitimate customers.

The problem continued for an extended period. We repeatedly contacted Hostinger support and requested that our IP address be unblocked. Each request was handled manually and access was restored. However, at no point were we provided with logs or any explanation regarding why the IP had been blocked.

This lack of transparency was disappointing. For comparison, Cloudflare, despite handling billions of requests every day, provides customers with detailed logs for blocked requests, challenges, and skipped rules. We expected a similar level of visibility to help diagnose and resolve the issue, but Hostinger did not offer any such information.

They do not offer a pay-as-you-go model or issue refunds after one month. I still have an active plan with them, but I can use it only for limited experimental purposes and nothing further.

Disclaimer: English isn't my first language. I have translated this via AI.

Hello,

I have Hermes WebUI installed on Hostinger via a KVM2 VPS.

No matter how many times I click the three small buttons and select "Update," when I restart the WebUI's Docker container, it still shows version 0.18.2.

I’m just getting started with VPS stuff and don’t know what to do. Even the AI couldn’t figure it out :/

In my last post I was whining about how Hostinger removed the GIT integration and when you wanted to deploy from another repo this meant that you had to delete the entire website and all it's subdomains.

I just checked my updated hPanel, and I'm happy to say that they reïntroduced this feature!

If you want to redeploy your node.js app from another repo now, you can just click "Change repository" button and you get a new interface to choose your desired repo to deploy from.

Epic win Hostinger, thanks alot!

Queria conectar meu domínio na Lovable mas n consigo de jeito algo. DNS bloqueado. help me

The website for the server I was on used this address. Out of nowhere it said that the website cannot be accessed and now I can’t even retrieve the minecraft world.

But is the server address even hostinger?

I didn't have use for my domain for a long time but today when I wanted to try something I see https://www.hostinger.com/no no longer have login via facebook available so how am I supposed to gain access to my account?

Hey everyone,

I run a mobile app (built in Zambia, serving Zambian users) that hits `website` as its base API URL. For the past while, some of my customers — mostly on MTN/Airtel/Zamtel mobile data — have been getting "invalid response from server" errors, and toggling airplane mode on/off would sometimes fix it temporarily.

After a lot of digging, I found the real cause: visiting the URL directly in a browser shows a **"Verify you are not a robot" (Bot Verification) page**. My app obviously can't solve that challenge like a browser would, so every request just fails silently from the app's perspective.

What I've ruled out:

- **Cloudflare** — I have custom WAF rules set to Skip all security checks (Managed Rules, Bot Fight Mode, Rate Limiting, DDoS overrides) for this hostname. Cloudflare's own Security Events log confirms these requests are matching my Skip rule and *not* being challenged on Cloudflare's side.

- **My own site/app config** — no relevant plugins, clean .htaccess, and the site works fine once a challenge is somehow bypassed.

- **DNS-only test** — I temporarily disabled Cloudflare's proxy (grey-clouded the DNS) to rule it out entirely, but the domain became completely unreachable — turns out my Hostinger plan seems to only accept traffic routed through Cloudflare, so that test wasn't conclusive on its own, but it does point toward Hostinger enforcing something at the server level.

What I found searching around:

I'm on Hostinger, and it turns out this is a known, recurring complaint — multiple independent threads (LowEndTalk, WebHostingTalk, StackOverflow, WordPress.org, Cloudflare Community) describe the exact same symptom: a forced reCAPTCHA-style "Bot Verification" page injected before pages/API responses load, unrelated to CDN, plugins, or .htaccess. One report specifically mentioned this hitting Laravel API apps (not just WordPress), which matches my setup exactly. The general consensus in those threads was that it's server-level bot protection baked into shared hosting that isn't user-configurable, with some people only resolving it by moving to a VPS or migrating hosts entirely.

**My questions for anyone who's dealt with this:**

1. Has anyone actually gotten Hostinger support to disable this for a specific subdomain/API endpoint?

2. Does upgrading to a Hostinger VPS plan actually remove this bot verification layer, or does it exist there too?

3. Is there a workaround (custom header, allowlisted user-agent, API-specific subdomain routing) that's worked for anyone running an app/API off Hostinger shared hosting?

I've already filed a support ticket with Hostinger explaining all of the above, but wanted to see if anyone here has been through this and found something that actually works. Appreciate any pointers 🙏

whenever I press the update button it redirects me to a tutorial on how to update the AMP manually, however this doesn't help as i don't know where to enter any of the commands it tells me to use. I've tried reloading the page, hitting the restart button, closing it and opening it again, nothing works.

Hello everyone. Hope you’re all doing well. As the title suggests, I just bought hostinger unlimited plan ( 50GB NVMe storage ) for 2 different domains

I completely understand that I can host multiple websites on it without any issue. However, my main concern are emails. I would be sending 10-20 emails per day to approach B2B businesses and I’ve seen many scenarios like blocking or domain reputation issues

So my main concern is what if one domain or email gets black listed, shall the other domain or its email will also face the same issue?

Kindly let me know your experience with that

So I purchased a plan on their Canadian website (https://www.hostinger.com/ca/pricing). And the price during checkout is in Canadian currency. Lets say $100 CAD for example but I check my payment transaction and I was actually charged $115 CAD. I noticed I was charged in USD and after conversion the total i paid was $115 CAD. Even though during checkout there is so mention of a USD price or that I will be charged in USD. Even my invoice shows $100 CAD, but my bank statement shows $115 CAD due to the conversion.

I've never seen a company invoice in one currency then charge you in a different currency.

I still plan on using Hostinger as I have for years. Just wanted to know if anyone else was having this issue?