A domain and a server are separate things: buying both does not connect them. Connecting them means one DNS record saying which machine answers for the name.

The record you need

An A record on the bare name, pointing at your server's address. The name is usually written as @, which means "the domain itself".

@    A    3600    203.0.113.10

Add a second one for www if you want www.your-domain.ge to work too — same address, name www.

Your server's address is on its page in the client area.

Where to add it

If the domain uses our nameservers, add it in the client area: open the domain, find the DNS card, add the record. Nothing else to configure.

If the domain is registered elsewhere, add it wherever its DNS is managed — that is usually the registrar you bought it from, not us. We cannot change records for a domain that does not point at our nameservers, and neither can anyone else.

How long it takes

Minutes for you, up to a few hours for everyone else. The number in the record above is the cache time in seconds — 3600 means other servers may keep the old answer for an hour after you change it.

So test from a device that has never opened the site before, or from mobile data rather than the same network. A page that still shows the old thing is usually a cache somewhere between you and the server, not a mistake in the record.

Then the certificate

HTTPS needs a certificate, and a certificate can only be issued once the name already points at the machine. Set the record first, then let the panel request one — in Coolify that happens by itself when you enter the domain.

A "certificate could not be issued" error almost always means the record has not taken effect yet. Wait, then ask again.