Frequently Asked Questions

Getting Started

What do I need to deploy a service with Hostly?

All you need is a Docker image, and you are ready to go!

Do I need to know Docker or Kubernetes to use Hostly?

No, you only need the Docker image. We take care of everything else!

Can Hostly build my application directly from a Git repository?

No, but virtually every online Git provider offers a CI/CD pipeline that can build a Docker image. You can use that image in Hostly.

Which Docker images can I use with Hostly?

In principle, all of them. If you are not sure, just try it out for free!

Can I use images from a private or alternative registry instead of Docker Hub?

Yes, as long as the registry configuration does not prevent it, any registry can be used.

Does my application need to meet certain requirements to run on Hostly?

The application must be available as a Docker image. At the moment, only one port per service is supported. Additional components such as databases, caches, or workers run as separate services in the same workspace and reach each other via their service name, see Use Cases and Examples. Since a deployment with Hostly is quick to set up, it is worth simply trying an image.

How long does it take until a newly deployed service is reachable?

Usually it only takes a few seconds until a service is online and reachable. The duration mostly depends on the application.

Account and Workspace

What is a workspace?

A workspace is the logical unit under a Hostly subdomain. For example, the workspace 'example' is available at example.hostly.ninja.

Can I rename my workspace later?

No, at the moment a workspace can no longer be renamed once it has been created.

Can I change my workspace domain later?

No, at the moment the workspace domain can no longer be changed once the workspace has been created.

Can another user use the same workspace domain?

No, another user cannot use the same workspace domain because it is unique to each workspace.

What happens to my workspace if I delete all services?

The workspace continues to exist, which means the workspace domain is retained and new services can be deployed.

Services and Deployments

What is the difference between a service and a deployment?

A deployment creates a service. A service is the application that can be reached from the internet.

Can I run multiple services at the same time?

Of course! Either more services are deployed in one workspace (only in the Paid Tier), or across multiple workspaces.

How many services can I run in the Free Tier?

The limit in the Free Tier is one service per workspace.

Can I deploy the same service multiple times?

Of course! The services need different service domains, but otherwise it is up to you which services you deploy and how. Alternatively, it is also possible to change the deployment of a service, but then there is only one instance of the service.

Can I switch back to a previous version of my service?

No, at least not directly. The previous Docker image can of course simply be deployed again, but that has to be done manually.

How do I change the settings of an existing service?

By changing the deployment. In doing so, all settings can be adjusted, and finally a new deployment can be started.

Do I need to redeploy a service if I want to change the Docker image tag used?

Yes, to change the Docker image the deployment must be changed, including when a different image tag is used.

What happens with an image using the tag `latest`?

Hostly loads the image that the `latest` tag points to for the deployment.

Is a `latest` image updated automatically?

No, Hostly does not change the service after deployment. To run the version `latest` currently points to, restart the service.

Domains, Network, and HTTPS

At which address is my service reachable?

Put simply: <service-domain-fragment>.<workspace-domain-fragment>.hostly.ninja

What is the difference between a workspace domain fragment and a service domain fragment?

As the names suggest, the workspace domain fragment describes the complete workspace, and the service domain fragment describes a single service within that workspace.

Can I change my service's domain fragment later?

When the deployment of the service is changed, the domain fragment can also be changed. Alternatively, a new service can be deployed with an alternative domain fragment.

Which internal port do I need to specify for my service?

The port your application listens on inside the container. Common configurations are, for example, 80, 2000, 3000, 8080. Background workers that never accept connections can be deployed without a port.

Can I make multiple ports of a container publicly reachable?

At the moment, there is only the option to make one port publicly reachable. If multiple ports are needed for specific use cases, you are welcome to contact us directly so we can find a solution.

Can I run a database on Hostly?

Yes. Deploy the database image as a service with "Only reachable internally" enabled, so it gets no public domain. Your other services reach it at <service-name>:<port>, e.g. db:5432. Add a volume (paid tier) so the data survives restarts. See Web app with PostgreSQL.

How do my services communicate with each other?

All services of a workspace reach each other at <service-name>:<port>. Any TCP protocol works. Services of other workspaces cannot reach them. The address is shown on the service details page.

Can I change the service name later?

No. Other services use the service name to reach the service, so it is fixed when the service is created. The subdomain, in contrast, can be changed by modifying the deployment.

Why can my container be running even though the service is not reachable via its domain?

Does Hostly support HTTPS or SSL?

Yes! Every service in Hostly can be made available via HTTPS. This is the default setting during deployment.

Do I have to configure a certificate myself for HTTPS?

No! Hostly takes care of creating and validating a Let's Encrypt certificate for every service.

Troubleshooting

My service is running, but the website is not reachable - what can I check?

If the deployment is not quite complete yet, that may be the reason. The most common reason is probably an incorrect port in the deployment, so make sure it is correct!

Hostly reports my service as unreachable even though the container is running - why?

The container may be working, but the containerized application may not be running correctly or as expected. Check the service logs to perhaps find a clue!

My service responds on the wrong port - how do I change the port?

The deployment can be changed in the service details. There is also an option there to correct the port.

My Docker image cannot be loaded - what could be the reason?

There can be several reasons. Here are the most likely possibilities:

• Is the image name correct?
• Is the image tag correct?
• Is the container registry reachable?
• Has the container registry been configured correctly?
• Has the container registry been set up correctly in the deployment?

Access to my private registry is not working - what can I check?

Is the registry configured correctly? Was the registry set up correctly in the deployment?

My `latest` image was not updated - why?

Hostly does not interfere with your services without your action. That also means images are not updated automatically as long as they are not restarted.

My service was paused without my action - why?

Normally, a notification with the reason for the pause should have been sent. You can find more information there. The most likely reason for the pause, however, is that a workspace limit was reached.

Why did my logs disappear after a restart?

For the sake of simplicity, and because the parameters can change with every start, only "current" logs are retained.

Why can't I restore my old deployment?

Hostly's simplicity means that the complex process of restoration cannot yet be represented appropriately at the moment.

Why can I no longer access my old service domain after deletion?

Because the associated service no longer exists. At the same time, the service domain is released again in the workspace.

Billing and Conceptual Questions

Which resources cause costs?

CPU, RAM, egress, and reserved Persistent Storage.

Is only actual resource usage billed?

Yes, for CPU, RAM, and egress, only the actual resource usage is billed. For Persistent Storage, the reserved storage capacity is billed, not the storage capacity used.

How exactly does Hostly measure my usage?

Hostly continuously measures resource usage for CPU, RAM, and egress in the background while a service is running. Persistent Storage is measured according to the reserved storage capacity.

Why is usage measured more precisely than the final invoice amount?

To maintain fair billing both for users and for Hostly, we measure concrete usage very precisely. However, to avoid problems with billing at the end, we round to individual cents.

How does High Availability affect my usage?

The exact additional usage depends on several factors, so for a rough estimate it is good to assume triple the usage.

Does a paused service cause costs?

If Persistent Storage is used for the service in the Paid Tier, it continues to be billed normally.

Does a stopped service cause costs?

If Persistent Storage is used for the service in the Paid Tier, it continues to be billed normally.

Is an existing but stopped service still counted toward the number of services?

Yes, as long as the service is not deleted, it is counted.