GitLab CE, ready-made on a Frankfurt VPS
Your own GitLab CE in Germany: Git repositories, merge requests, issues, CI/CD and a container registry. Ready 15–35 minutes after the server starts.
from $8.00 /mo
Plan and price
GitLab CE itself is free: you pay the normal monthly price of the Frankfurt plan. It needs at least 4 GB RAM and 40 GB disk, and the Apps tab only shows it on plans big enough for it.
Ready in 15–35 minutes
Order
Servers → Order → Frankfurt, choose a plan, then select GitLab CE on the Apps tab — or press Order on this page.
The server starts
An Ubuntu 24.04 server is created in Frankfurt like any other.
The app installs itself
On first boot GitLab CE installs and configures itself. There is nothing to do on your side.
Ready
Allow 15–35 minutes from the moment the server is running.
What you get
- Repositories and merge requests
- Host your code and review changes with merge requests.
- Issues
- Track work right next to the code.
- CI/CD
- Build and test from your repositories.
- Container registry
- Keep your container images next to your code.
How to log in
Open the address
Your app is at
https://<server-ip-with-dashes>.sslip.iowith a free Let’s Encrypt certificate. For a server at 1.2.3.4 that ishttps://1-2-3-4.sslip.io.Sign in
User
root, with the password from/root/APP-INFO.txt.Use Git over SSH
Clone and push over SSH on port 22, as
git@<your-address>.Find your login details
They are in
/root/APP-INFO.txtand are printed when you log in over SSH asrootwith the server’s root password from the panel.
The app login uses the server’s root password when it meets the app’s own password rules; otherwise a generated password is used. Either way it is in /root/APP-INFO.txt. Servers created with only an SSH key always get a generated one.
Use your own domain
Point the A record
At your DNS provider, point the domain’s A record to the server IP.
Wait until it resolves
Check that the domain already resolves to the server IP.
Run one command
Log in over SSH as
rootand run the command below with your domain.
nexoran-app-domain example.comGood to know
In the first minutes your browser can show a self-signed certificate until Let’s Encrypt succeeds; it is retried every 15 minutes.
GitLab CE needs at least 4 GB of RAM and 40 GB of disk, and 4 vCPUs are recommended — that is why we suggest s1.large.
Questions about GitLab CE
Why does my browser warn about the certificate?
In the first minutes GitLab CE can use a self-signed certificate until Let’s Encrypt succeeds. It is retried every 15 minutes.
Which plan should I pick?
At least 4 GB of RAM and 40 GB of disk; 4 vCPUs are recommended, so we suggest s1.large.
The address doesn’t open yet
Wait the full 35 minutes after the server is running, then check /root/APP-INFO.txt.
Where is the password?
In /root/APP-INFO.txt on the server. It is also shown when you log in over SSH as root.
GitLab CE isn’t in the Apps list. Why?
The chosen plan is too small. GitLab CE needs at least 4 GB RAM and 40 GB disk; pick a bigger plan and it appears.
Can I put GitLab CE on a server I already have?
Yes, on a Frankfurt server: choose Reinstall and pick GitLab CE. Reinstalling wipes the disk.
Is it available in Istanbul?
No. Ready-made apps are only for Frankfurt (Germany) servers.
How is it billed?
Like any server: the monthly plan price is taken when the server is created, and if you cancel, the unused hours go back to your wallet. Pay by card or USDT/TRX (TRC20). You can upgrade to a bigger Frankfurt plan later; the disk can only grow.
Still not reachable after 45 minutes?
If GitLab CE still does not open 45 minutes after the server started, or the domain command fails, open a ticket.
From signup to SSH
Create an account
Sign up with your email and confirm it.
Top up your wallet
By card or with USDT/TRX on TRC20.
Order a server
Pick a plan and a system. It is usually online within a few minutes, with the root or Administrator password in your panel.