Hello Everyone, When trying to install a new instance of discourse, I’m getting this error (here is my install log): Configuration file at containers/app.yml updated successfully! Updates successful. Rebuilding in 5 seconds. Building app x86_64 arch detected. Ensuring launcher is up to date Fetching origin Launcher is up-to-date 2.0.20230313-1023: Pulling from discourse/base Digest: sha256:f7467469ab9e39c3548d4478e3f416c05b34a0ee58eb6e40b963e562005669cc Status: Image is up to date for discourse/base:2.0.20230313-1023 docker.io/discourse/base:2.0.20230313-1023 /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups.rb /usr/local/bin/pups --stdin I, [2023-03-27T20:31:27.457005 #1] INFO -- : Reading from stdin I, [2023-03-27T20:31:27.460746 #1] INFO -- : > locale-gen $LANG && update-locale I, [2023-03-27T20:31:27.480498 #1] INFO -- : Generating locales (this might take a while)... Generation complete. I, [2023-03-27T20:31:27.480671 #1] INFO -- : > mkdir -p /shared/postgres_run I, [2023-03-27T20:31:27.482598 #1] INFO -- : I, [2023-03-27T20:31:27.482814 #1] INFO -- : > chown postgres:postgres /shared/postgres_run I, [2023-03-27T20:31:27.484487 #1] INFO -- : I, [2023-03-27T20:31:27.484620 #1] INFO -- : > chmod 775 /shared/postgres_run I, [2023-03-27T20:31:27.486138 #1] INFO -- : I, [2023-03-27T20:31:27.486282 #1] INFO -- : > rm -fr /var/run/postgresql I, [2023-03-27T20:31:27.487948 #1] INFO -- : I, [2023-03-27T20:31:27.488123 #1] INFO -- : > ln -s /shared/postgres_run /var/run/postgresql I, [2023-03-27T20:31:27.489729 #1] INFO -- : I, [2023-03-27T20:31:27.489850 #1] INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 2023/03/27 20:31:27 socat[19] E connect(6, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory I, [2023-03-27T20:31:27.493311 #1] INFO -- : I, [2023-03-27T20:31:27.493434 #1] INFO -- : > rm -fr /shared/postgres_run/.s* I, [2023-03-27T20:31:27.495388 #1] INFO -- : I, [2023-03-27T20:31:27.495489 #1] INFO -- : > rm -fr /shared/postgres_run/*.pid I, [2023-03-27T20:31:27.497544 #1] INFO -- : I, [2023-03-27T20:31:27.497650 #1] INFO -- : > mkdir -p /shared/postgres_run/13-main.pg_stat_tmp I, [2023-03-27T20:31:27.499322 #1] INFO -- : I, [2023-03-27T20:31:27.499452 #1] INFO -- : > chown postgres:postgres /shared/postgres_run/13-main.pg_stat_tmp I, [2023-03-27T20:31:27.501120 #1] INFO -- : I, [2023-03-27T20:31:27.504597 #1] INFO -- : File > /etc/service/postgres/run chmod: +x chown: I, [2023-03-27T20:31:27.508049 #1] INFO -- : File > /etc/service/postgres/log/run chmod: +x chown: I, [2023-03-27T20:31:27.511402 #1] INFO -- : File > /etc/runit/3.d/99-postgres chmod: +x chown: I, [2023-03-27T20:31:27.514894 #1] INFO -- : File > /root/upgrade_postgres chmod: +x chown: I, [2023-03-27T20:31:27.515142 #1] INFO -- : > chown -R root /var/lib/postgresql/13/main I, [2023-03-27T20:31:28.735098 #1] INFO -- : I, [2023-03-27T20:31:28.735235 #1] INFO -- : > [ ! -e /shared/postgres_data ] && install -d -m 0755 -o postgres -g postgres /shared/postgres_data && sudo -E -u postgres /usr/lib/postgresql/13/bin/initdb -D /shared/postgres_data || exit 0 I, [2023-03-27T20:31:28.737235 #1] INFO -- : I, [2023-03-27T20:31:28.737282 #1] INFO -- : > chown -R postgres:postgres /shared/postgres_data I, [2023-03-27T20:31:28.742051 #1] INFO -- : I, [2023-03-27T20:31:28.742154 #1] INFO -- : > chown -R postgres:postgres /var/run/postgresql I, [2023-03-27T20:31:28.743865 #1] INFO -- : I, [2023-03-27T20:31:28.744025 #1] INFO -- : > /root/upgrade_postgres I, [2023-03-27T20:31:28.747140 #1] INFO -- : I, [2023-03-27T20:31:28.747267 #1] INFO -- : > rm /root/upgrade_postgres I, [2023-03-27T20:31:28.748792 #1] INFO -- : I, [2023-03-27T20:31:28.748982 #1] INFO -- : Replacing data_directory = '/var/lib/postgresql/13/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.749461 #1] INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.750313 #1] INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.751033 #1] INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.751628 #1] INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.752250 #1] INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.752905 #1] INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup I, [2023-03-27T20:31:28.754942 #1] INFO -- : I, [2023-03-27T20:31:28.755175 #1] INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.755407 #1] INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.756207 #1] INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/13/main/postgresql.conf I, [2023-03-27T20:31:28.756862 #1] INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres peer in /etc/postgresql/13/main/pg_hba.conf I, [2023-03-27T20:31:28.757062 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/13/main/pg_hba.conf I, [2023-03-27T20:31:28.757776 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf I, [2023-03-27T20:31:28.758225 #1] INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main I, [2023-03-27T20:31:28.759529 #1] INFO -- : > sleep 5 2023-03-27 20:31:28.807 UTC [42] LOG: starting PostgreSQL 13.10 (Debian 13.10-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2023-03-27 20:31:28.808 UTC [42] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-03-27 20:31:28.808 UTC [42] LOG: listening on IPv6 address "::", port 5432 2023-03-27 20:31:28.811 UTC [42] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-03-27 20:31:28.815 UTC [45] LOG: database system was shut down at 2023-03-27 20:28:11 UTC 2023-03-27 20:31:28.819 UTC [42] LOG: database system is ready to accept connections I, [2023-03-27T20:31:33.761313 #1] INFO -- : I, [2023-03-27T20:31:33.761575 #1] INFO -- : > su postgres -c 'createdb discourse' || true 2023-03-27 20:31:33.798 UTC [55] postgres@postgres ERROR: database "discourse" already exists 2023-03-27 20:31:33.798 UTC [55] postgres@postgres STATEMENT: CREATE DATABASE discourse; createdb: error: database creation failed: ERROR: database "discourse" already exists I, [2023-03-27T20:31:33.799993 #1] INFO -- : I, [2023-03-27T20:31:33.800298 #1] INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true 2023-03-27 20:31:33.836 UTC [59] postgres@discourse ERROR: role "discourse" already exists 2023-03-27 20:31:33.836 UTC [59] postgres@discourse STATEMENT: create user discourse; ERROR: role "discourse" already exists I, [2023-03-27T20:31:33.837797 #1] INFO -- : I, [2023-03-27T20:31:33.838050 #1] INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true I, [2023-03-27T20:31:33.876194 #1] INFO -- : GRANT I, [2023-03-27T20:31:33.876428 #1] INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"' I, [2023-03-27T20:31:33.912984 #1] INFO -- : ALTER SCHEMA I, [2023-03-27T20:31:33.913234 #1] INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"' NOTICE: extension "hstore" already exists, skipping I, [2023-03-27T20:31:33.952214 #1] INFO -- : CREATE EXTENSION I, [2023-03-27T20:31:33.952497 #1] INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"' NOTICE: extension "pg_trgm" already exists, skipping I, [2023-03-27T20:31:33.989195 #1] INFO -- : CREATE EXTENSION I, [2023-03-27T20:31:33.989492 #1] INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"' NOTICE: extension "hstore" already exists, skipping I, [2023-03-27T20:31:34.026202 #1] INFO -- : CREATE EXTENSION I, [2023-03-27T20:31:34.026457 #1] INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"' NOTICE: extension "pg_trgm" already exists, skipping I, [2023-03-27T20:31:34.063103 #1] INFO -- : CREATE EXTENSION I, [2023-03-27T20:31:34.063427 #1] INFO -- : > sudo -u postgres psql discourse I, [2023-03-27T20:31:34.065173 #1] INFO -- : update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = 'discourse' AND encoding = pg_char_to_encoding('SQL_ASCII'); I, [2023-03-27T20:31:34.106966 #1] INFO -- : File > /var/lib/postgresql/take-database-backup chmod: +x chown: postgres:postgres I, [2023-03-27T20:31:34.109188 #1] INFO -- : File > /var/spool/cron/crontabs/postgres chmod: chown: I, [2023-03-27T20:31:34.109307 #1] INFO -- : > echo postgres installed! I, [2023-03-27T20:31:34.111011 #1] INFO -- : postgres installed! I, [2023-03-27T20:31:34.115222 #1] INFO -- : File > /etc/service/redis/run chmod: +x chown: I, [2023-03-27T20:31:34.119487 #1] INFO -- : File > /etc/service/redis/log/run chmod: +x chown: I, [2023-03-27T20:31:34.123308 #1] INFO -- : File > /etc/runit/3.d/10-redis chmod: +x chown: I, [2023-03-27T20:31:34.123515 #1] INFO -- : Replacing daemonize yes with in /etc/redis/redis.conf I, [2023-03-27T20:31:34.124009 #1] INFO -- : Replacing (?-mix:^pidfile.*$) with in /etc/redis/redis.conf I, [2023-03-27T20:31:34.125560 #1] INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data I, [2023-03-27T20:31:34.127590 #1] INFO -- : I, [2023-03-27T20:31:34.127894 #1] INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf I, [2023-03-27T20:31:34.128253 #1] INFO -- : Replacing (?-mix:^bind .*$) with in /etc/redis/redis.conf I, [2023-03-27T20:31:34.129521 #1] INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf I, [2023-03-27T20:31:34.130794 #1] INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf I, [2023-03-27T20:31:34.132190 #1] INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf I, [2023-03-27T20:31:34.133379 #1] INFO -- : > echo redis installed I, [2023-03-27T20:31:34.135253 #1] INFO -- : redis installed I, [2023-03-27T20:31:34.135381 #1] INFO -- : > cat /etc/redis/redis.conf | grep logfile I, [2023-03-27T20:31:34.138227 #1] INFO -- : logfile "" I, [2023-03-27T20:31:34.138365 #1] INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf I, [2023-03-27T20:31:34.139576 #1] INFO -- : > sleep 10 103:C 27 Mar 2023 20:31:34.143 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 103:C 27 Mar 2023 20:31:34.144 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=103, just started 103:C 27 Mar 2023 20:31:34.144 # Configuration loaded 103:M 27 Mar 2023 20:31:34.144 * monotonic clock: POSIX clock_gettime 103:M 27 Mar 2023 20:31:34.144 * Running mode=standalone, port=6379. 103:M 27 Mar 2023 20:31:34.144 # Server initialized 103:M 27 Mar 2023 20:31:34.144 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 103:M 27 Mar 2023 20:31:34.145 * Loading RDB produced by version 7.0.7 103:M 27 Mar 2023 20:31:34.145 * RDB age 203 seconds 103:M 27 Mar 2023 20:31:34.145 * RDB memory usage when created 0.82 Mb 103:M 27 Mar 2023 20:31:34.145 * Done loading RDB, keys loaded: 0, keys expired: 0. 103:M 27 Mar 2023 20:31:34.145 * DB loaded from disk: 0.000 seconds 103:M 27 Mar 2023 20:31:34.145 * Ready to accept connections I, [2023-03-27T20:31:44.141477 #1] INFO -- : I, [2023-03-27T20:31:44.141711 #1] INFO -- : > thpoff echo "thpoff is installed!" I, [2023-03-27T20:31:44.144716 #1] INFO -- : thpoff is installed! I, [2023-03-27T20:31:44.144888 #1] INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end' I, [2023-03-27T20:31:44.192449 #1] INFO -- : I, [2023-03-27T20:31:44.192657 #1] INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end' I, [2023-03-27T20:31:44.239221 #1] INFO -- : I, [2023-03-27T20:31:44.239454 #1] INFO -- : > /usr/local/bin/ruby -e 'if (ENV["DISCOURSE_CDN_URL"] || "")[0..1] == "//"; puts "Aborting! CDN must have a protocol specified. Once fixed you should rebake your posts now to correct all posts."; exit 1; end' I, [2023-03-27T20:31:44.286979 #1] INFO -- : I, [2023-03-27T20:31:44.287178 #1] INFO -- : > rm -f /etc/cron.d/anacron I, [2023-03-27T20:31:44.289015 #1] INFO -- : I, [2023-03-27T20:31:44.291032 #1] INFO -- : File > /etc/cron.d/anacron chmod: chown: I, [2023-03-27T20:31:44.294734 #1] INFO -- : File > /etc/runit/1.d/copy-env chmod: +x chown: I, [2023-03-27T20:31:44.298332 #1] INFO -- : File > /etc/service/unicorn/run chmod: +x chown: I, [2023-03-27T20:31:44.301841 #1] INFO -- : File > /etc/service/nginx/run chmod: +x chown: I, [2023-03-27T20:31:44.305464 #1] INFO -- : File > /etc/runit/3.d/01-nginx chmod: +x chown: I, [2023-03-27T20:31:44.309064 #1] INFO -- : File > /etc/runit/3.d/02-unicorn chmod: +x chown: I, [2023-03-27T20:31:44.309147 #1] INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run I, [2023-03-27T20:31:44.309430 #1] INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf I, [2023-03-27T20:31:44.311151 #1] INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git reset --hard 130:C 27 Mar 2023 20:31:44.315 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 130:C 27 Mar 2023 20:31:44.315 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=130, just started 130:C 27 Mar 2023 20:31:44.315 # Configuration loaded 130:M 27 Mar 2023 20:31:44.315 * monotonic clock: POSIX clock_gettime 130:M 27 Mar 2023 20:31:44.315 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use 130:M 27 Mar 2023 20:31:44.315 # Failed listening on port 6379 (TCP), aborting. Updating files: 100% (32972/32972), done. I, [2023-03-27T20:31:45.986984 #1] INFO -- : HEAD is now at 59e548540 Build(deps): Bump sass from 1.58.3 to 1.59.2 in /app/assets/javascripts (#20656) I, [2023-03-27T20:31:45.987126 #1] INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git clean -f I, [2023-03-27T20:31:46.076992 #1] INFO -- : I, [2023-03-27T20:31:46.077119 #1] INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c ' if [ $(git rev-parse --is-shallow-repository) == "true" ]; then git remote set-branches --add origin main git remote set-branches origin tests-passed git fetch --depth 1 origin tests-passed else git fetch --prune --prune-tags origin tests-passed fi ' fatal: unable to access 'https://github.com/discourse/discourse.git/': gnutls_handshake() failed: Error in the pull function. I, [2023-03-27T20:34:46.977544 #1] INFO -- : I, [2023-03-27T20:34:46.977905 #1] INFO -- : Terminating async processes I, [2023-03-27T20:34:46.977937 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42 I, [2023-03-27T20:34:46.977970 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103 2023-03-27 20:34:46.978 UTC [42] LOG: received fast shutdown request 103:signal-handler (1679949286) Received SIGTERM scheduling shutdown... 2023-03-27 20:34:46.979 UTC [42] LOG: aborting any active transactions 2023-03-27 20:34:46.981 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1 2023-03-27 20:34:46.982 UTC [46] LOG: shutting down 103:M 27 Mar 2023 20:34:46.983 # User requested shutdown... 103:M 27 Mar 2023 20:34:46.983 * Saving the final RDB snapshot before exiting. 103:M 27 Mar 2023 20:34:46.987 * DB saved on disk 103:M 27 Mar 2023 20:34:46.987 # Redis is now ready to exit, bye bye... 2023-03-27 20:34:47.012 UTC [42] LOG: database system is shut down FAILED -------------------- Pups::ExecError: cd /var/www/discourse && sudo -H -E -u discourse bash -c ' if [ $(git rev-parse --is-shallow-repository) == "true" ]; then git remote set-branches --add origin main git remote set-branches origin tests-passed git fetch --depth 1 origin tests-passed else git fetch --prune --prune-tags origin tests-passed fi ' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"code", "cmd"=>["sudo -H -E -u discourse git reset --hard", "sudo -H -E -u discourse git clean -f", "sudo -H -E -u discourse bash -c '\n if [ $(git rev-parse --is-shallow-repository) == \"true\" ]; then\n git remote set-branches --add origin main\n git remote set-branches origin $version\n git fetch --depth 1 origin $version\n else\n git fetch --prune --prune-tags origin $version\n fi\n'", "sudo -H -E -u discourse bash -c '\n if [[ $(git symbolic-ref --short HEAD) == $version ]] ; then\n git pull\n else\n git -c advice.detachedHead=false checkout $version\n fi\n'", "mkdir -p tmp", "chown discourse:www-data tmp", "mkdir -p tmp/pids", "mkdir -p tmp/sockets", "touch tmp/.gitkeep", "mkdir -p /shared/log/rails", "bash -c \"touch -a /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log\"", "bash -c \"ln -s /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log $home/log\"", "bash -c \"mkdir -p /shared/{uploads,backups}\"", "bash -c \"ln -s /shared/{uploads,backups} $home/public\"", "bash -c \"mkdir -p /shared/tmp/{backups,restores}\"", "bash -c \"ln -s /shared/tmp/{backups,restores} $home/tmp\"", "chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp", "[ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete"]} bootstrap failed with exit code 128 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. cda75b6ebff62a27faea38809b2dc6d1aab1dd390e7a50711e8fa27f445e82bf I’m running Ubuntu 20.04 LTS in a Google Cloud Instance. I’ve already run the Discourse Doctor, and it didn’t help. Let me know, Jack

Maybe related to the new partial clone tech @gerhard ?

[image] Jack: unable to access 'https://github.com/discourse/discourse.git/': gnutls_handshake() failed: Error in the pull function. I don’t think it has anything to do with the partial clone. Something seems to interfere with the TLS handshake. Help! Upgrade constantly fails had the same issue and they are using Google Cloud as well, so maybe there’s a problem with that? :thinking:

Seems like the issue we have too. We do use Google Cloud, however we’ve been using it for at least 2 years with no issues -the issue only started to occur recently. We cannot pull any updates of discourse of plugin/themes. @gerhard @Falco

Yes but it does download the update from git but fails at the end… pretty lost here! Any advice would be extremely appreciated.

You can try lowering the MTU of the Docker interface: [image] Fresh install failing - gnutls_handshake() failed: Error in the pull function Self-hosting Well it turns out the issue was in fact the MTU of the docker0 network adapter. I resolved the issue by changing the following line: ExecStart=/usr/bin/dockerd -H fd:// to ExecStart=/usr/bin/dockerd --mtu=1400 -H fd:// in my /lib/systemd/system/docker.service Thanks for trying to assist.

Thank you - we’ll try that and report back. Much appreciated!

Issue when installing new Discourse instance

Product Support Self-hosting

Falco (Falco) March 28, 2023, 1:33pm 5

That’s a network level issue, so you may want to contact the support channel of your server provider.

Topic		Replies	Views
Failed install on ubuntu 22.04 Self-hosting	1	1189	December 25, 2023
Cloud installation is not working Self-hosting	11	1576	June 19, 2024
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use Self-hosting	3	6842	April 9, 2023
Trouble Rebuilding: gnutls_handshake() failed Self-hosting	1	936	September 7, 2023
First installation - Error on rebuild app Self-hosting	8	525	February 15, 2024

Issue when installing new Discourse instance

Related topics