Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content

GitLab

69 Topics 701 Posts
Scheduled critical security release for PHP
More details here: PHP scheduled critical security release CVE-2026-115560
  • GitLab - Package Updates

    Pinned Locked
    264
    1 Votes
    264 Posts
    373k Views
    Package UpdatesP
    [1.122.3] Update gitlab-foss to 19.5.6 Full Changelog Re-evaluate SAML admin groups on Admin Mode re-entry GitLab Enterprise Edition Scope vulnerability lookup for Secrets FP detection to the relevant project (merge request) Validate policy configuration before executing scheduled PEP jobs (merge request) Apply a foundational flow's declared privileges on every entry point (merge request) Ignore Duo settings for groups without Duo access (merge request) Pin validated IPs for Octokit connections (merge request) Block quick actions for MCP-scoped tokens (merge request) [Backport 19.5] Fix confluence URL not being validated when integration is inactive (merge request) Restrict merge_after to users who can set metadata (merge request) Skip per-ref Redis cache in protected branch push check
  • Help with improving GitLab startup latency

    2
    3 Votes
    2 Posts
    134 Views
    robiR
    Ah yeah, from the chown it seems it is necessary for GitLab to start, but maybe not all at once. If the command is run twice, once with depth 1 to allow GitLab to start, then later full depth if needed; that should solve the startup delay. If there's any changes to the container/updates those permissions reset.
  • Could the GitLab package be optimized to reduce its Docker image size?

    4
    3 Votes
    4 Posts
    273 Views
    andreasduerenA
    @james nice
  • GitLab package - critical patch 19.3.2 available

    5
    2 Votes
    5 Posts
    336 Views
    jamesJ
    Hello @tobiasb and @cte.ch We are currently validating the GitLab v19.4.1 release. I expect an app update to be available in approximately one hour
  • 1 Votes
    3 Posts
    252 Views
    girishG
    For the moment, you can ignore the warning. Our gitlab shows the same warning. @jayonrails the new postgres is via the new ubuntu image, which is part of our 10.1 roadmap
  • 1 Votes
    10 Posts
    1k Views
    girishG
    @simon yeah, that makes sense. I think I will just cap it for all instances to 4.
  • GitLab not starting.

    4
    0 Votes
    4 Posts
    563 Views
    N
    @joseph said: @nckne please update, this is already fixed . Thanks! Yes - I can confirm it is working in the latest version of the package. Thank you very much!
  • 1 Votes
    4 Posts
    746 Views
    T
    Roll back for GitLab is a no-go thing. Let's hope that Gitlab does not do something in future update release which would prevent using it.
  • Cannot add group images: Error 403 Forbidden

    Solved
    4
    1 Votes
    4 Posts
    875 Views
    P
    Perfect, thanks a lot!
  • PostGres SQL Error update from v1.112.4 to v1.113.0

    9
    1 Votes
    9 Posts
    1k Views
    M
    I had the exact same problem and the post of arnaudguy fixed it like a charm. So please set the app in repair mode use the postgres button on the top to enter postgres follow the steps of arnaudguy SELECT tc.constraint_name, kcu.column_name, ccu.table_name AS foreign_table_name, ccu.column_name AS foreign_column_name FROM information_schema.table_constraints tc JOIN information_schema.key_column_usage kcu ON tc.constraint_name = kcu.constraint_name JOIN information_schema.constraint_column_usage ccu ON ccu.constraint_name = tc.constraint_name WHERE tc.table_name = 'user_agent_details' AND tc.constraint_type = 'FOREIGN KEY'; SELECT COUNT(*) AS nb_violations FROM user_agent_details WHERE organization_id IS NULL; BEGIN; DELETE FROM user_agent_details WHERE organization_id IS NULL; COMMIT; ALTER TABLE user_agent_details VALIDATE CONSTRAINT check_17a3a18e31; BEGIN DELETE 1 COMMIT ALTER TABLE SELECT conname, convalidated FROM pg_constraint WHERE conname = 'check_17a3a18e31'; Exit postgres \q deactivate repair mode and voilá it works again... thanks a lot to you guys...
  • Gitlab runners fail every 30th build

    Moved
    4
    1 Votes
    4 Posts
    2k Views
    D
    We solved this in the end by adding some clean up to the GitLab runner's after_script in our .gitlab-ci.yml file: before_script: - stat -c %m /tmp - du -sh /tmp - ls /tmp -la - export XDG_CACHE_HOME=$(mktemp -d) # Each job leaks files into the gitlab-runner's private /tmp after_script: - rm -rf $XDG_CACHE_HOME - du -sh /tmp - ls /tmp -la - find /tmp -mindepth 1 -maxdepth 1 -user gitlab-runner -exec rm -rf {} + - du -sh /tmp - ls /tmp -la We could see the files that got left over when we added the logging lines.
  • Cannot login after restoring from backup to v.1.112.4

    2
    1 Votes
    2 Posts
    490 Views
    J
    @davejgreen I have responded on support@ . Let's continue there and I will report back my findings here.
  • S3 Artifacts

    3
    0 Votes
    3 Posts
    691 Views
    J
    In /app/data/gitlab.yml, there is a artifacts section. You can just set it to enabled. You don't need S3 as such, it stores in filesystem by default into /app/data/shared/artifacts artifacts: enabled: true
  • Gigantic blunder caused by a lack of warnings

    Moved
    5
    2 Votes
    5 Posts
    2k Views
    necrevistonnezrN
    @nebulon said in Gigantic blunder caused by a lack of warnings: Curiously nothing about that possible side-effect is mentioned in the gitlab docs either https://docs.gitlab.com/administration/incoming_email/ or at least I didn't see it. It could be clearer but it does say „We recommend using an email address that receives only messages that are intended for the GitLab instance“ and it goes on about „dedicated“ addresses….
  • How to run a GitLab container registry (2024)

    6
    1 Votes
    6 Posts
    3k Views
    jamesgallagherJ
    @timconsidine Yes, this is what I run today and it has worked really, really well ... integrates nicely with Gitlab. But the deprecation the Gitlab folks have in mind for 3rd party registries is a worry (https://docs.gitlab.com/administration/packages/container_registry/#use-an-external-container-registry-with-gitlab-as-an-auth-endpoint). There's talk about them doing a hard deprecation which I'm taking to mean would stop it working completely rather than just being unsupported as today
  • "Unlock instructions" email due to brute force attack on gitlab users

    20
    1 Votes
    20 Posts
    9k Views
    jamesJ
    Hello @allanbowe Not by default from Cloudron. (Maybe in the future) I would advise to temporary edit the GitLab NGINX file to only allow certain IP addresses. This manual change will get reset with every Cloudron / Server / App restart. So it is really temporary. Example for APP ID 682ca768-93e5-4bcb-a760-677daa9a8e3b Go into the application NGINX config folder: cd /home/yellowtent/platformdata/nginx/applications/682ca768-93e5-4bcb-a760-677daa9a8e3b Edit the sub.domain.tld.conf file, in this case dokuwiki.cloudron.dev: nano dokuwiki.cloudron.dev.conf Inside this section, add: # https server server { # allow localhost allow 127.0.0.1; # allow cloudron proxy allow 172.18.0.1; # allow this servers public ipv4 allow REDACTED-IPV4; # allow this servers public ipv6 allow REDACTED-IPV6; # Allow some other specific IPv4 e.g VPN allow VPN-IP; # deny all other deny all; [...] } Reload the NGINX service: systemctl reload nginx.service This will result for other IPs that are not explicitly allowed to return a 403 Forbidden: [image: 52b04087-811c-4d9f-8a90-2b20cb5de9f4-image.png] Keep in mind, every Cloudron / Server / App Restart will reset this change!
  • Enable KAS ("Kubernetes Agent Server")

    7
    0 Votes
    7 Posts
    4k Views
    J
    @arnaudguy yes
  • Persistent memory issues—how to reduce/remove extra features?

    4
    2 Votes
    4 Posts
    2k Views
    S
    Thanks for the answers—so to be clear it’s not possible to reduce the features as their docs suggest? (Through some rb config) To be honest the gitea instance was hacked, so that was not ideal, and I switched from gogs to gitea awhile ago and cannot exactly recall why.
  • Pushing to a branch doesn't trigger callbacks

    2
    1
    1 Votes
    2 Posts
    1k Views
    J
    @lukaszj could it be same as https://gitlab.com/gitlab-org/gitlab/-/issues/348565 ? From a comment there, One "workarround" that seems to work is to trigger the HouseKeeping on the general settings . The issue is still not fixed but maybe you can look for log string "Internal API error" ? There are some detailed logs in /run/gitlab/log/ (only available via Web Terminal)
  • gitlab-ee question

    Moved
    17
    0 Votes
    17 Posts
    9k Views
    girishG
    @AriusII No plans for next 3 months atleast (but that's as far as our planning goes). But given EE is selfhosted, it's not outside our scope.