Every server you start on OpenSysLab gets a raw IP address — something like 143.198.112.47. It works, but nobody wants to hand that to their team or customers. Mapping your own domain (for example crm.yourcompany.com) to the server IP takes about ten minutes and makes everything that follows — bookmarks, SSL, sharing — much nicer. Here is the whole process, start to finish.

1. Find your server IP

Your server’s IP is shown in My Account → My Servers next to every server, and it is also in the “your server is ready” email you received when provisioning finished. Copy it — you will paste it into your DNS settings in a moment.

2. Add an A record at your DNS provider

Your domain’s DNS lives wherever you registered or manage it — Cloudflare, Namecheap, GoDaddy, Route 53, or your hosting company. Open the DNS management page and create a record with these values:

• Type: A
• Name / Host: the subdomain you want — crm, app, chat, or @ if you want the bare domain
• Value / Points to: your server IP
• TTL: automatic, or as low as the provider allows while you test

Save the record. A few honest notes:

• Subdomains are easier than the bare domain. app.yourcompany.com just works; the bare yourcompany.com may already serve your website. Pick a fresh subdomain per service — one for the business app, one for the Open WebUI chat.
• Running several apps on one server? Give each its own hostname: crm.yourcompany.com for the app, chat.yourcompany.com for Open WebUI. You will point each one at the same IP and let the server route by name.
• If you use Cloudflare, set the record to “DNS only” (grey cloud) while you set up. The orange-cloud proxy hides your IP behind Cloudflare, which breaks the direct IP connection and complicates the certificate step below. You can re-enable the proxy afterwards if you want.

3. Check that the record has propagated

DNS changes are not instant. Most providers propagate in a few minutes; the worst case with a long TTL is an hour or two. To check from your own machine:

• macOS / Linux: dig +short crm.yourcompany.com or ping crm.yourcompany.com
• Windows: nslookup crm.yourcompany.com

When the answer shows your server IP, the name resolves. If it shows nothing or the old value, wait and try again — or use a public propagation checker like whatsmydns.net to see progress around the world.

4. Get HTTPS on the name

Your server already answers on its IP, and the apps respond on their ports — but browsers will flag http:// as insecure, and some features simply require a valid certificate. The fix is a free Let’s Encrypt certificate, and this is where your Vibe-code agent earns its keep. Once the domain resolves, open the chat on your server and say something like:

“Set up HTTPS for crm.yourcompany.com pointing to this server — install certbot, configure the reverse proxy, redirect HTTP to HTTPS, and make sure auto-renewal is in place.“

The agent will install certbot, obtain the certificate (it needs port 80 open for the domain-validation challenge, so confirm your firewall allows it), adjust the web server config, and add a renewal timer. Afterwards, https://crm.yourcompany.com just works, and it stays working.

If you would rather do it by hand, the short version on any Ubuntu server is: sudo apt install certbot python3-certbot-nginx, then sudo certbot --nginx -d crm.yourcompany.com, and follow the prompts. Certbot edits the nginx config and installs the renewal hook for you.

5. Point the name at the right app

One server runs several services — the business app (for example Odoo on port 8069) and Open WebUI on port 3000. The reverse proxy decides which hostname goes where. Tell the agent exactly what you want: “Route crm.yourcompany.com to my Odoo and chat.yourcompany.com to Open WebUI, both over HTTPS.” It will write the virtual hosts, wire up the certificates, and restart the proxy.

Good to know

• Your DNS is yours. OpenSysLab does not manage or resell domains. Any registrar works — you only ever need to edit DNS records yourself.
• The IP stays put. A running server keeps its IP for its whole life. It only changes if you delete the server and start a new one — then you update the A record once and you are done.
• No domain yet? The IP address in My Servers works for everything in the meantime, including the agent chat and the apps.
• Stuck halfway? The agent can diagnose DNS and certificate problems from the server side — “crm.yourcompany.com still shows a certificate error, figure out why” is a perfectly good prompt.

A custom domain plus HTTPS is the difference between a test box and something you can put in front of customers. Your server, your name, your certificate — set up in one sitting. Browse the catalog on the shop page or revisit Odoo Vibe-Coding platform on OpenSysLab.