March 17, 20206 yr 1 hour ago, RichardRob said: Is that the proxy-confs/gitlab-ce.subdomain.conf file which everyone mentions in this thread without ever providing a full path? No, the settings file for Gitlab. Check the documentation of Gitlab to find the correct file. The one you mention is for reverse proxy and doesnt have anything to do with changing the ports to access Gitlab. You do need to adjust the proxy config if you reverse proxy Gitlab.
March 27, 20206 yr Hi, is the forth or fifth update and the issue was not fixed The issue is that when I click to a file link will go to "https://git.devboard.tech:9443/tips/linux/-/blob/master/crontab-check-start-app.md" instead of "https://git.devboard.tech/tips/linux/-/blob/master/crontab-check-start-app.md" for example. This behaviour is valid for all files on the gitlab. The git is up and running, you can check it. The rest if pages are OK. This issue has appeared about five updates ago, I do not changed any configuration file, I do not touch anything, after the update I see this behaviour....... Edited March 27, 20206 yr by MorgothCreator
March 28, 20206 yr 8 hours ago, MorgothCreator said: Hi, is the forth or fifth update and the issue was not fixed The issue is that when I click to a file link will go to "https://git.devboard.tech:9443/tips/linux/-/blob/master/crontab-check-start-app.md" instead of "https://git.devboard.tech/tips/linux/-/blob/master/crontab-check-start-app.md" for example. This behaviour is valid for all files on the gitlab. The git is up and running, you can check it. The rest if pages are OK. This issue has appeared about five updates ago, I do not changed any configuration file, I do not touch anything, after the update I see this behaviour....... I'm having the same exact issue. I can't find where you would configure this at all.
March 31, 20206 yr Hi, When installing the docker it is recommended that the GitLab data directory is configured to be in the cache. How can I relocate the repositories to the array? That is, they will take a lot of storage and keeping them in the cache is not feasible. Thank you!
April 1, 20206 yr 19 hours ago, Ruato said: Hi, When installing the docker it is recommended that the GitLab data directory is configured to be in the cache. How can I relocate the repositories to the array? That is, they will take a lot of storage and keeping them in the cache is not feasible. Thank you! Found a solution: Add an additional path to the docker configuration. Edit the gitlab.rb confgiration. Specify the new location as the only repository location via the Gitlab web UI.
April 7, 20206 yr Did anyone get mattermost running with this docker? I actually hadn't realised you could and have been concentrating on a standalone mattermost docker, but finding a few issues that ultimately stop it from running. I did get gitlab running quite easily and supposedly you edit one file and mattermost works. But when I do that it breaks. So am interested in what others have achieved. I'm spinning up a startup and chat is really important for us with all our remote workers.
April 8, 20206 yr How am I supposed to enable mattermost if I don't have a hostname? I'm currently using gitlab just as: http://UNRAID-IP-ADDRESS:9080 No fancy nginx reverse proxy or a hostname or anything like that. I went into /etc/gitlab/gitlab.rb and added the line: mattermost_external_url 'http://UNRAID-IP-ADDRESS:8065' (I also tried it without the port number) and ran: gitlab-ctl reconfigure and although Gitlab still comes up, going to http://IP:8065 does not work. How else is it supposed to work if you don't use URLs? Edited April 8, 20206 yr by frakman1
April 8, 20206 yr @frakman1 seems like we're both trying to do this, maybe we can help each other. I do run the awesome letsencrypt/nginx container though for https but figure I should at least be able to get it to work just on an IP address, but can't even get the package to start after editing gitlab.rb and starting the reconfigure. Does yours start after adding it? I note that unraid says it's started, but after a page refresh it's actually stopped - something to do with crashes not updating the GUI I guess.
April 8, 20206 yr @MarshalleqI actually just tried it after reading your post and being curious about using Mattermost. I hate how Gitlab says: oh it's just a one-line change and poof! you'll magically have a chat server. It's never that easy! haha Yes, my Gitlab starts normally after the reconfigure command. You might have a typo in that file, just a thought. When things go wrong with Gitlab, I normally look at this log file: tail -f /var/log/gitlab/gitlab-rails/production.log There are other log files in that folder that might be worth looking at depending on what's going on. Of course, there's always the docker logs as well.
April 8, 20206 yr Also, I see the mattermost page has a good NGINX config for it, however Gitlab comes with NGINX built in. Does anyone have a functioning NGINX setup using lets encrypt container? It's a lot to learn, when you don't know how the internals of an omnibus container work. Further I've noted that as soon as I add the external url as https, it enables it's own https stack, which I don't want. I assume I just add the external url as just http: and let's encrypt proxy it, like with everything else. However, I'd bet that this external URL will define all sorts of outgoing addresses that need it to be accurate and am wondering if it's even possible to do this. Here was me thinking this was going to be easy. Edit: Seems like I can use this: Disable bundled NGINX In /etc/gitlab/gitlab.rb set: nginx['enable'] = false Taken from here. Which has links to external web server settings. I guess I'll give this a go. Edited April 8, 20206 yr by Marshalleq
April 8, 20206 yr So giving a little back - here's how to get gitlab working with unrair letsencrypt/nginx neverse proxy and SSL. Obviously the lets encrypt container is covered elsewhere, so not going into that. I wouldn't be surprised to find that there are a few extra things to configure in NGINX to get everything working more betterer, but anyway, once you have a domain, change the following settings in gitlab.rb and reconfigure. Point a standard nginx proxy config at it on port 80. There's an official proxy config to base it from here. Configure for reverse proxy by editing gitlab.rb in your docker config location Find and locate the following values and change to below nginx['listen_port'] = 80 nginx['listen_https'] = false external_url 'https://gitlab.yourdomain.com' Add to existing trusted proxies so that the logging doesn’t all come from a single IP address. (example) gitlab_rails['trusted_proxies'] = ['192.168.1.0/24', '172.18.0.0/24'] Reconfigure as per standard reconfig procedure e.g. below # docker exec -it GitLab-CE bash # gitlab-ctl reconfigure That's all that's needed to get the page to come up anyway. I assume mattermost will be similar - hoping I can easily rename that to chat.domain.com Edited April 8, 20206 yr by Marshalleq
April 23, 20206 yr The more you fix things, the more broken they are 🤦♂️. Now Gitlab does not even start: Upgrading PostgreSQL to 11.7 cp /opt/gitlab/embedded/service/gitlab-rails/public/deploy.html /opt/gitlab/embedded/service/gitlab-rails/public/index.html ok: down: gitaly: 0s, normally up ok: down: logrotate: 1s, normally up ok: down: registry: 0s, normally up ok: down: sidekiq: 1s, normally up ok: down: sshd: 0s, normally up There was an error fetching locale and encoding information from the database Please ensure the database is running and functional before running pg-upgrade STDOUT: STDERR: psql: FATAL: the database system is starting up == Fatal error == Please check error logs == Reverting == ok: down: postgresql: 0s, normally up ok: run: postgresql: (pid 722) 0s == Reverted == == Reverted to 10.12. Please check output for what went wrong == rm -f /opt/gitlab/embedded/service/gitlab-rails/public/index.html ok: run: gitaly: (pid 744) 1s ok: run: logrotate: (pid 808) 0s ok: run: registry: (pid 821) 0s ok: run: sidekiq: (pid 832) 1s ok: run: sshd: (pid 838) 0s Upgrading the existing database failed and was reverted. Please check the output, and open an issue at: https://gitlab.com/gitlab-org/omnibus-gitlab/issues If you would like to restart the instance without attempting to upgrade, add the following to your docker command: -e GITLAB_SKIP_PG_UPGRADE=true
May 10, 20206 yr @MorgothCreator I ran into a similar issue when upgrading my standalone Gitlab from Gitlab 12.8.1 -> 12.10.3. The PostGres DB upgrade from 10.12 -> 11.7 failed. In my case, it pointed to a log file (pg_upgrade_server.log) that told me that it was due to low memory. Initializing the new database: OK Upgrading the data:Error upgrading the data to version 11.7 STDOUT: Performing Consistency Checks ----------------------------- Checking cluster versions ok *failure* Consult the last few lines of "pg_upgrade_server.log" for the probable cause of the failure. connection to database failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.50432"? could not connect to source postmaster started with the command: "/opt/gitlab/embedded/postgresql/10/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/opt/gitlab/postgresql/data" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/var/opt/gitlab/postgresql'" start Failure, exiting STDERR: Upgrading the data: NOT OK Traceback (most recent call last): 8: from /opt/gitlab/embedded/bin/omnibus-ctl:23:in `<main>' 7: from /opt/gitlab/embedded/bin/omnibus-ctl:23:in `load' 6: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/omnibus-ctl-0.6.0/bin/omnibus-ctl:31:in `<top (required)>' 5: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/omnibus-ctl-0.6.0/lib/omnibus-ctl.rb:746:in `run' 4: from /opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/omnibus-ctl-0.6.0/lib/omnibus-ctl.rb:204:in `block in add_command_under_category' 3: from /opt/gitlab/embedded/service/omnibus-ctl/pg-upgrade.rb:192:in `block in load_file' 2: from /opt/gitlab/embedded/service/omnibus-ctl/pg-upgrade.rb:249:in `general_upgrade' 1: from /opt/gitlab/embedded/service/omnibus-ctl/lib/gitlab_ctl/pg_upgrade.rb:130:in `run_pg_upgrade' /opt/gitlab/embedded/service/omnibus-ctl/lib/gitlab_ctl/pg_upgrade.rb:130:in `raise': wrong number of arguments (given 4, expected 0..3) (ArgumentError) Ensuring PostgreSQL is updated: NOT OK Error ensuring PostgreSQL is updated. Please check the logs dpkg: error processing package gitlab-ce (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu11) ... Errors were encountered while processing: gitlab-ce E: Sub-process /usr/bin/dpkg returned an error code (1) root@gitlab:~# tail -n 100 /var/opt/gitlab/postgresql/pg_upgrade_server.log ----------------------------------------------------------------- pg_upgrade run on Sun May 10 12:11:15 2020 ----------------------------------------------------------------- mand: "/opt/gitlab/embedded/postgresql/10/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/opt/gitlab/postgresql/data" -o "-p 50432 -b -c listen_addresses='' -c unix_socket_permissions=0700 -c unix_socket_directories='/var/opt/gitlab/postgresql'" start >> "pg_upgrade_server.log" 2>&1 waiting for server to start....LOG: listening on Unix socket "/var/opt/gitlab/postgresql/.s.PGSQL.50432" FATAL: coulcomd not map anonymous shared memory: Cannot allocate memory HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 15407661056 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections. LOG: database system is shut down stopped waiting pg_ctl: could not start server Examine the log output. root@gitlab:~# free -m total used free shared buffers cached Mem: 64431 61810 2620 669 885 10965 -/+ buffers/cache: 49959 14471 Swap: 0 0 0 14,693 MB needed Luckily you can bypass upgrading the PostGres DB for now.
May 27, 20206 yr is this hitting million CPU suddenly for anyone else? had to stop it. every time i turn it on, my CPU usage goes through the roof.
June 19, 20206 yr Does anyone know how to reduce the size of the Gitlab-CE container? Mine is about 2GB and it barely has anything in it. The docker-hub image is ~750MB so how did it get so big? I've already disabled prometheus_monitoring. Not sure what else I need to do.
July 9, 20205 yr Having an issue with my Gitlab-Ce instance. It is fully updated (and it ran perfectly before), however when I start Gitlab, I get the following: Running handlers:[0m There was an error running gitlab-ctl reconfigure: bash[migrate gitlab-rails database] (gitlab::database_migrations line 55) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1' Running handlers complete ---- Begin output of "bash" "/tmp/chef-script20200709-25-jjrrc7" ---- STDOUT: rake aborted! PG::ConnectionBad: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"? /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:48:in `block (3 levels) in <top (required)>' /opt/gitlab/embedded/bin/bundle:23:in `load' /opt/gitlab/embedded/bin/bundle:23:in `<main>' Tasks: TOP => gitlab:db:configure (See full trace by running task with --trace) STDERR: ---- End output of "bash" "/tmp/chef-script20200709-25-jjrrc7" ---- Ran "bash" "/tmp/chef-script20200709-25-jjrrc7" returned 1
July 12, 20205 yr On 7/10/2020 at 7:31 AM, Thor said: Having an issue with my Gitlab-Ce instance. It is fully updated (and it ran perfectly before), however when I start Gitlab, I get the following: Running handlers:[0m There was an error running gitlab-ctl reconfigure: bash[migrate gitlab-rails database] (gitlab::database_migrations line 55) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1' Running handlers complete ---- Begin output of "bash" "/tmp/chef-script20200709-25-jjrrc7" ---- STDOUT: rake aborted! PG::ConnectionBad: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"? /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/db.rake:48:in `block (3 levels) in <top (required)>' /opt/gitlab/embedded/bin/bundle:23:in `load' /opt/gitlab/embedded/bin/bundle:23:in `<main>' Tasks: TOP => gitlab:db:configure (See full trace by running task with --trace) STDERR: ---- End output of "bash" "/tmp/chef-script20200709-25-jjrrc7" ---- Ran "bash" "/tmp/chef-script20200709-25-jjrrc7" returned 1 I think this is due to their upgrades breaking things. Because I have ZFS snapshots I was able to roll it back and force it to stay on an older version. Not what I really wanted to do, but saved me the time of fixing it up. So not much help, but it might help to point you in the right direction.
July 20, 20205 yr I'm not sure how to get this set up. I installed the container. It had an error the first go and stopped. I restarted the container and now I can get a login screen but how to I login to manage it?
August 25, 20205 yr Hello I have a problem with my gitlab container. After starting it, it's running great. After round about one day, I only get a " 502 Whoops, GitLab is taking too much time to respond." message. If I look into my logs, it seams that the Redis database it not available anymore. I can restart the container, but after one day it's the same again. What is going wrong? My container settings: Extra Parameters: --env GITLAB_OMNIBUS_CONFIG="external_url 'https://myurl.com/'; gitlab_rails['lfs_enabled'] = true;" Network Type: Custom network with a LetsEncrypt Container Ports HTTP: 5090 HTTPS:5443 Application Data Storage Path: /mnt/user/git/git files/ <-- Share with Cache enabled (Use cache: yes) Config Storage Path and Config Storage Path: Default Path (/mnt/cache/appdata/gitlab-ce) Custom Path: - Container Path: /var/opt/gitlab/gitlab-rails/shared/lfs-objects - Host Path: /mnt/user/git/git lfs files/ <-- Share with Cache enabled (Use cache: yes) gitlab.rb Changes: To prevent the integrated nginx from trying to reach letsEncrypt and communicating with my letsEncrypt container via http instead. nginx[‘listen_port’] = 9080; nginx[‘listen_https’] = false; The GitLab Container Log: ==> /var/log/gitlab/sidekiq/current <== {"severity":"ERROR","time":"2020-08-25T19:40:21.824Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:22.825Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:23.443Z","message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:23.443Z","message":"/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:362:in `rescue in establish_connection'"} {"severity":"WARN","time":"2020-08-25T19:40:23.444Z","error_class":"Redis::CannotConnectError","error_message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)","error_backtrace":["config/initializers/zz_metrics.rb:198:in `connect'","lib/gitlab/instrumentation/redis_interceptor.rb:15:in `call'"],"retry":0} {"severity":"ERROR","time":"2020-08-25T19:40:23.445Z","message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"WARN","time":"2020-08-25T19:40:23.445Z","error_class":"Redis::CannotConnectError","error_message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)","error_backtrace":["config/initializers/zz_metrics.rb:198:in `connect'","lib/gitlab/instrumentation/redis_interceptor.rb:15:in `call'"],"retry":0} {"severity":"ERROR","time":"2020-08-25T19:40:23.826Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:24.828Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} ==> /var/log/gitlab/redis-exporter/current <== 2020-08-25_19:40:24.88917 time="2020-08-25T19:40:24Z" level=error msg="Couldn't connect to redis instance" ==> /var/log/gitlab/sidekiq/current <== {"severity":"ERROR","time":"2020-08-25T19:40:25.014Z","message":"heartbeat: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:26.468Z","message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"WARN","time":"2020-08-25T19:40:26.469Z","error_class":"Redis::CannotConnectError","error_message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)","error_backtrace":["config/initializers/zz_metrics.rb:198:in `connect'","lib/gitlab/instrumentation/redis_interceptor.rb:15:in `call'"],"retry":0} {"severity":"ERROR","time":"2020-08-25T19:40:26.470Z","message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"WARN","time":"2020-08-25T19:40:26.470Z","error_class":"Redis::CannotConnectError","error_message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)","error_backtrace":["config/initializers/zz_metrics.rb:198:in `connect'","lib/gitlab/instrumentation/redis_interceptor.rb:15:in `call'"],"retry":0} {"severity":"ERROR","time":"2020-08-25T19:40:26.830Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:27.831Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:28.446Z","message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"ERROR","time":"2020-08-25T19:40:28.447Z","message":"/opt/gitlab/embedded/lib/ruby/gems/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:362:in `rescue in establish_connection'"} {"severity":"WARN","time":"2020-08-25T19:40:28.447Z","error_class":"Redis::CannotConnectError","error_message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)","error_backtrace":["config/initializers/zz_metrics.rb:198:in `connect'","lib/gitlab/instrumentation/redis_interceptor.rb:15:in `call'"],"retry":0} {"severity":"ERROR","time":"2020-08-25T19:40:28.448Z","message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} {"severity":"WARN","time":"2020-08-25T19:40:28.449Z","error_class":"Redis::CannotConnectError","error_message":"Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)","error_backtrace":["config/initializers/zz_metrics.rb:198:in `connect'","lib/gitlab/instrumentation/redis_interceptor.rb:15:in `call'"],"retry":0} ==> /var/log/gitlab/puma/puma_stdout.log <== {"timestamp":"2020-08-25T19:40:28.795Z","pid":322,"message":"PumaWorkerKiller: Consuming 3111.04296875 mb with master and 4 workers."} ==> /var/log/gitlab/sidekiq/current <== {"severity":"ERROR","time":"2020-08-25T19:40:28.832Z","message":"Heartbeat thread error: Error connecting to Redis on /var/opt/gitlab/redis/redis.socket (Errno::ECONNREFUSED)"} Edited August 25, 20205 yr by andr0id
August 30, 20205 yr Hi, Can someone post their Nginx reverse proxy config with letsencrypt? I can't get it working. I am using letsencrypt from linuxserver. Thanks!
August 30, 20205 yr 5 hours ago, Moka said: Hi, Can someone post their Nginx reverse proxy config with letsencrypt? I can't get it working. I am using letsencrypt from linuxserver. Thanks! Not sure what you mean? Nginx is the reverse proxy, so you don't need to proxy nginx. If you are using the nginx container, you can just move the site the letsencrypt container as it is the same. The difference is certbot.
August 30, 20205 yr 6 hours ago, Moka said: Hi, Can someone post their Nginx reverse proxy config with letsencrypt? I can't get it working. I am using letsencrypt from linuxserver. Thanks! Just use the sample for gitea and change it a bit: server { listen 443 ssl; listen [::]:443 ssl; server_name gitlab.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app GitLab-CE; set $upstream_port 9080; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Don't forget to put them all in the same virtual docker network. nginx will look out for a container with the name you set for $upstream_app.
September 3, 20205 yr Not sure what I am missing. I am noob and need help. Trying to setup Gitlab docker, bridge, ports: 9080, 9443, 9022 (defaults with the template). Didn't change anything and I get the errors in the log file. Not sure what to look at. Tried different data paths and it didn't help. In the log files it logs "cannot migrate because of old version" Logs attached. Gitlab_log.txt Edited September 3, 20205 yr by 062bel313 Shouldn't have pasted that huge log
September 3, 20205 yr Hello I am having trouble adding an external domain to gitlab. When I do I get a 502 bad gateway error. Anyone that can help?
September 6, 20205 yr Gitlab docker: I was able to make the docker run. It was file permission issue and now after I corrected it, everything works, except for LFS; I get this error In the error, I can see the docker is using "unraid" as hostname, but for my system it should have been "meroUNRAID". I tried passing -e hostname 'meroUNRAID', but the Gitlab is still looking for the unraid. While initializing the docker, I see HOST_OS = "Unraid". Not sure how to pass my own host name. Changing the hostname file inside /etc/hostname also didn't fix. Any help?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.