What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The quickest route depends on your repository. A public GitLab project can be cloned over HTTPS without credentials. A private project can use a read-only SSH deploy key, while the GitLab App is the more integrated option for private HTTPS cloning, repository selection, push events, and merge-request preview deployments.
Antihost offers VPS plans with one-click Coolify, NVMe storage and a 14-day free trial.
For continuous deployment, connect the repository, choose the production branch, enable Deploy on push (webhooks), and verify the first delivery in Coolify’s Deployment Logs. A GitLab App receives provider events through the integration; a public-repository or deploy-key application needs a manually configured GitLab webhook.
As an Amazon Associate I earn from qualifying purchases.
Choose the right GitLab connection method
Coolify supports three practical source paths. The best choice is determined by repository visibility, how narrowly you want to scope credentials, and whether you need merge-request previews.
| Method | Repository access | Authentication scope | Events and previews | Best fit |
|---|---|---|---|---|
| Public HTTPS URL | Public repository | None for cloning | Manual webhook; push events and optional merge-request events | A public project where you want the simplest setup |
| SSH deploy key | Private repository | One project, normally read-only | Manual webhook; push events and optional merge-request events | A single private repository or an environment where an App integration is unavailable |
| GitLab App | Private or public repositories, selected through the integration | App-managed repository access | Integrated provider events; push deployments and merge-request previews | Teams that need repository browsing, private HTTPS cloning, or several event-driven workflows |
The GitLab App does not remove the need to configure deployment behavior in Coolify. The application still needs a selected branch and Deploy on push (webhooks) enabled before a push can update it.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Prerequisites before you connect GitLab
- A running Coolify instance connected to a server that can reach GitLab over the network.
- Permission to read the GitLab project. For a deploy key, you need to add a public key to that project; for the App, you need to create or authorize the App source.
- A repository URL and the branch that should deploy to the target environment.
- A Docker-capable server. Coolify runs applications as Docker containers on the connected server.
- If the application pulls a private container image, separate registry credentials. Git credentials authenticate source cloning; they do not authenticate GitLab Container Registry access.
Decide whether the application is built from source with Nixpacks, Railpack, a Static build, a Dockerfile, or Docker Compose. That build choice is made in the Coolify application configuration after the source is connected.
Connect a public GitLab repository over HTTPS
Use this path when the project is genuinely public and you do not need private-repository authorization. Because GitLab can serve the repository without credentials, Coolify can clone the HTTPS URL directly.
Free tools Windows power users keep installed
One-click scans. No signup required.
- In Coolify, create a new application on the server where it should run.
- Choose the public repository source option and enter the project’s HTTPS clone URL.
- Select the deployment branch. Treat this as the production branch: a push to another branch will not update this application.
- Choose the build path that matches the repository: Nixpacks, Railpack, Static, Dockerfile, or Docker Compose.
- Save the application and perform an initial deployment. Confirm in Deployment Logs that Coolify cloned the expected repository and checked out the requested commit.
A public URL only solves source authentication. Automatic deployment still requires a webhook and the correct Auto deploy setting, described below.
Deploy a private repository with an SSH deploy key
A deploy key is a useful least-scope credential when one Coolify application needs access to one private GitLab project. The private key stays in Coolify; the matching public key is attached to the GitLab project.
1. Create or store the key in Coolify
In Coolify’s source or private-repository configuration, create a new SSH key pair or paste an existing private key into the deploy-key credential field. Keep the private key confidential. Do not paste it into the repository, an image, or a public issue.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
2. Add the public key to the GitLab project
- Open the target project in GitLab.
- Go to Settings > Repository > Deploy keys.
- Add the public half of the key saved in Coolify.
- Grant write access only if your deployment process truly needs it; a clone-and-build workflow normally needs read access.
The key must be added to the exact project that owns the repository. Adding it to a group or a different project does not authorize the clone.
3. Use the repository’s SSH URL
Copy the SSH clone URL from GitLab, such as [email protected]:group/project.git. Preserve the group and project path exactly; an HTTPS URL or a misspelled namespace will not use the deploy key correctly.
4. Create the Coolify application
- Start a new application in Coolify.
- Select Private Repository (with deploy key).
- Choose the stored key and enter the repository SSH URL.
- Select the branch and build method.
- Deploy once and inspect the log. The successful sequence should show authentication to GitLab, a clone of the selected repository, and a checkout of the configured commit.
If cloning fails, first compare the public key shown in Coolify with the key listed under the correct GitLab project’s Deploy keys. Then check that the URL uses the SSH form and that the Coolify server can reach GitLab.
Connect through the GitLab App
The GitLab App is the integrated path. It is designed for repository browsing, private HTTPS cloning, and provider events, so it is generally preferable when you manage several repositories or need merge-request preview deployments.
GitLab.com setup
- In Coolify, add a new GitLab App source.
- Follow the authorization flow and grant access to the projects that Coolify should be allowed to use.
- Return to the application-creation screen and select the repository from the App-connected projects.
- Select the branch and build method, then save the application.
- Run an initial deployment and verify that the log clones the selected repository and checks out the requested commit.
Self-managed GitLab setup
For a self-managed GitLab installation, the App source needs both the GitLab URL and the GitLab API URL. Enter the externally reachable base URL for the GitLab instance and the corresponding API endpoint exactly as your installation exposes them. If GitLab is behind a firewall or private network, the Coolify server must still be able to reach those endpoints.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
- Create the GitLab App source in Coolify.
- Enter the self-managed GitLab URL and API URL when prompted.
- Complete the App registration or authorization in GitLab.
- For each project that will deploy, add the webhook URL and matching secret token supplied by Coolify.
- Enable Push events for branch deployments. Enable Merge request events when the project uses preview environments.
- In Coolify, create the application, choose the App-connected repository and branch, and deploy.
The exact registration screens can differ between GitLab.com and self-managed releases, but the required information is the same: the GitLab base URL, its API URL for self-managed installations, project authorization, and the webhook settings for each project.
Configure automatic deployments with a manual webhook
Public-URL and deploy-key applications use a manual GitLab webhook. The webhook tells Coolify that a Git event occurred; Coolify then decides whether that event matches the application’s configured branch and deployment policy.
1. Copy the webhook URL from Coolify
Open the application’s webhook or deployment settings in Coolify and copy the generated webhook URL. Do not retype it. A missing character or an extra slash can make GitLab’s delivery fail.
2. Create a strong shared secret
Save a secret of at least 16 characters in Coolify, then use the identical value in GitLab. Treat it like a credential and avoid placing it in source control or chat transcripts.
3. Add the webhook in GitLab
- Open the GitLab project.
- Go to Settings > Webhooks.
- Paste the Coolify webhook URL.
- Enter the exact same secret token.
- Enable Push events.
- Also enable Merge request events if this application should create previews for merge requests.
- Save the webhook.
4. Enable deployment on push in Coolify
In the application, open Advanced > Deployment and set Auto deploy to Deploy on push (webhooks). Saving a webhook in GitLab without this Coolify setting leaves the application in a manually deployed state.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
5. Test before changing production code
Use GitLab’s webhook test action and inspect the delivery response. Then push a harmless commit to the branch configured in Coolify. Open Deployment Logs and verify the event, repository, branch, commit, build, and container update.
Automatic deployments with the GitLab App
When the GitLab App is configured, Coolify receives provider events through the integration, so you do not add a separate manual Git webhook URL for the same application. The application still needs Deploy on push (webhooks) enabled and must be connected to the branch you intend to deploy.
For each App-connected project, configure the webhook URL and matching token supplied by Coolify, then select the appropriate event types. Push events drive branch deployments. Merge-request events are used for preview deployments when the application and environment are configured to create previews.
A push to a different branch does not update the production application automatically. Create another application or environment with that branch, or change the configured branch deliberately before relying on it for releases.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How a GitLab-triggered Coolify deployment works
Coolify describes the model this way: “A deployment combines configuration saved in Coolify with a trigger such as Deploy, Redeploy, a Git webhook, or an API request.”
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
- Event arrives: GitLab sends a push or merge-request event through the App integration or manual webhook.
- Application is matched: Coolify checks the source, project, event type, and configured branch.
- Source and version are resolved: Coolify identifies the requested repository and commit, then clones or fetches it with the configured Git credential.
- Build is selected: The saved application configuration determines whether Coolify uses Nixpacks, Railpack, Static, Dockerfile, or Docker Compose.
- Image and runtime are prepared: Coolify builds or pulls the necessary image and applies runtime configuration such as environment values and exposed service settings.
- Containers are updated: The connected server runs the resulting application as Docker containers, replacing or updating the prior deployment according to the application configuration.
A successful webhook delivery therefore does not guarantee a successful release. Delivery only starts the process; the Deployment Logs reveal whether cloning, building, image retrieval, or container startup failed.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Set up merge-request preview deployments
Preview deployments let a merge request run in an isolated or temporary environment before it reaches the production branch. They require event delivery and an application configuration that supports previews.
- Use the GitLab App or a manual webhook path that has Merge request events enabled.
- Configure the Coolify application or preview environment to build the merge-request source rather than only the production branch.
- Define the runtime settings, domain behavior, and resource limits appropriate for temporary environments.
- Open a merge request and inspect Deployment Logs for the source ref and commit associated with the preview.
- Close or merge the request and confirm that the preview lifecycle follows the policy you selected.
Do not assume that enabling merge-request events alone creates previews. The event must be enabled in GitLab and matched to a Coolify preview-capable application configuration.
Troubleshoot failed connections and deployments
GitLab reports that the webhook cannot be reached
- Confirm the Coolify server is publicly reachable from GitLab on the required HTTPS endpoint.
- Check reverse-proxy, firewall, DNS, and TLS configuration between GitLab and Coolify.
- Use GitLab’s webhook delivery details to distinguish a network timeout from an HTTP error returned by Coolify.
The webhook arrives but no deployment starts
- Verify that Advanced > Deployment > Auto deploy is set to Deploy on push (webhooks).
- Confirm the event type is enabled. A push event will not substitute for a merge-request event when previews are expected.
- Check that the pushed branch exactly matches the branch selected in the Coolify application.
- Review Deployment Logs for a rejected event or a source/branch mismatch.
Secret-token validation fails
Compare the GitLab token and the secret saved in Coolify character by character. Re-save both values if necessary, then send a new test delivery. A token that is almost identical still fails authentication.
SSH cloning fails for a private project
- Confirm the public key is attached under the correct project’s Settings > Repository > Deploy keys.
- Verify that Coolify is using the matching private key.
- Use the repository’s SSH URL, for example
[email protected]:group/project.git, not an HTTPS URL. - Check network access from the Coolify server to GitLab and inspect the clone step in Deployment Logs.
The source clone succeeds but the image pull fails
Repository credentials and registry credentials are separate. If the deployment pulls a private container image, configure credentials for the relevant container registry in Coolify. A valid GitLab deploy key or App authorization does not grant permission to pull that image.
Recommended Free Tools
The build succeeds but the application is unavailable
Continue through the Deployment Logs after the build step. Check runtime environment values, exposed ports, health checks, domain and proxy configuration, and container startup output. GitLab connectivity is no longer the likely cause once the image has built successfully.
Quick Recap
Operational and security practices
- Use a deploy key when one project should be readable by one application; avoid sharing a broad personal access credential for a narrow deployment.
- Limit deploy-key permissions to read access unless deployment genuinely writes back to the repository.
- Protect webhook secrets and rotate them if they are exposed.
- Keep production branch selection explicit. Document which branch each Coolify application deploys.
- Separate production and preview environments so merge-request code cannot silently replace production containers.
- Monitor both sides of the integration: GitLab webhook delivery results and Coolify Deployment Logs.
- Remember that the server needs outbound access to GitLab and enough capacity to build and run Docker workloads.
A practical connection checklist
- Choose public HTTPS, an SSH deploy key, or the GitLab App based on repository privacy and event requirements.
- Confirm the Coolify server can reach GitLab and run Docker workloads.
- Connect the repository and select the exact deployment branch.
- Choose Nixpacks, Railpack, Static, Dockerfile, or Docker Compose as appropriate.
- Deploy once manually and confirm the expected commit appears in Deployment Logs.
- For public or deploy-key sources, copy the Coolify webhook URL into GitLab, use a shared secret of at least 16 characters, enable the required events, and set Auto deploy to Deploy on push (webhooks).
- For the GitLab App, configure the project webhook and event types supplied by Coolify; do not add a second manual Git webhook URL for the same integration.
- Test delivery, push to the configured branch, and watch the complete deployment log.
- If a private image is pulled, configure registry credentials separately from Git credentials.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
