Problem with installation on vps ubuntu

Kacper_Kacper · February 18, 2025, 12:02am

Retrying download gem from https://rubygems.org/ due to error (2/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/syntax_tree-disable_ternary-1.0.0.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (2/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/test-prof-1.4.4.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (2/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/unf-0.2.0.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (2/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/yaml-lint-0.1.2.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (3/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/syntax_tree-disable_ternary-1.0.0.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (3/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/test-prof-1.4.4.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (3/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/unf-0.2.0.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (3/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/yaml-lint-0.1.2.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/syntax_tree-disable_ternary-1.0.0.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/test-prof-1.4.4.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/unf-0.2.0.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/yaml-lint-0.1.2.gem`. It is likely that you need to grant write permissions for that path.

Fetching yard 0.9.37




Retrying download gem from https://rubygems.org/ due to error (2/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/yard-0.9.37.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (3/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/yard-0.9.37.gem`. It is likely that you need to grant write permissions for that path.

Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.3.0/cache/yard-0.9.37.gem`. It is likely that you need to grant write permissions for that path.

Bundler::PermissionError: There was an error while trying to write to `/var/lib/gems/3.3.0/cache/base64-0.2.0.gem`. It is likely that you need to grant write permissions for that path.
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/shared_helpers.rb:109:in `rescue in filesystem_access'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/shared_helpers.rb:104:in `filesystem_access'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/rubygems_integration.rb:393:in `block in download_gem'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/retry.rb:40:in `run'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/retry.rb:30:in `attempt'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/rubygems_integration.rb:385:in `download_gem'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/source/rubygems.rb:494:in `download_gem'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/source/rubygems.rb:451:in `fetch_gem'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/source/rubygems.rb:435:in `fetch_gem_if_possible'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/source/rubygems.rb:177:in `install'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/installer/gem_installer.rb:55:in `install'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/installer/gem_installer.rb:17:in `install_from_spec'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/installer/parallel_installer.rb:133:in `do_install'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/installer/parallel_installer.rb:124:in `block in worker_pool'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/worker.rb:62:in `apply_func'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/worker.rb:57:in `block in process_queue'
  <internal:kernel>:187:in `loop'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/worker.rb:54:in `process_queue'
  /var/lib/gems/3.3.0/gems/bundler-2.6.4/lib/bundler/worker.rb:90:in `block (2 levels) in create_threads'

An error occurred while installing base64 (0.2.0), and Bundler cannot continue.

In Gemfile:
  actionmailer was resolved to 7.2.2.1, which depends on
    actionpack was resolved to 7.2.2.1, which depends on
      actionview was resolved to 7.2.2.1, which depends on
        rails-dom-testing was resolved to 2.2.0, which depends on
          activesupport was resolved to 7.2.2.1, which depends on
            base64

Arkshine · February 18, 2025, 12:22am

Welcome,

Can you please provide details on the context of this error?

Additionally, writing a descriptive title would be helpful!

Kacper_Kacper · February 18, 2025, 12:31am

Hello, I need help with the installation, I have these errors and I don’t know what to do

Kacper_Kacper · February 18, 2025, 12:32am

An error occurred while installing base64 (0.2.0), and Bundler cannot
continue.

Arkshine · February 18, 2025, 12:35am

Is it a standard installation?

Kacper_Kacper · February 18, 2025, 12:38am

Yes, I do the standard installation, but I don’t know why it doesn’t work and gives me these errors

tobiaseigen · February 18, 2025, 12:45am

Is your server connected to the Internet?

Kacper_Kacper · February 18, 2025, 12:46am

yes
connected

tobiaseigen · February 18, 2025, 12:49am

Looks like there is a problem with permissions for the user you are running the install script with. Is it the root user?

Also, is this a new cloud server or one you have already been using for something else? If so it is hard to support.

Kacper_Kacper · February 18, 2025, 12:51am

Hostname for your Discourse? [discourse.example.com]: [discourse.example.com

Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname:  [discourse.example.com.
WARNING: Connection to http://[discourse.example.com (port 80) also fails.

This suggests that [discourse.example.com resolves to some IP address that does not reach this
machine where you are installing discourse.

The first thing to do is confirm that [discourse.example.com resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.

If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.

This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type

./launcher rebuild app

Kacper_Kacper · February 18, 2025, 12:52am

i dont have domian namee

tobiaseigen · February 18, 2025, 12:56am

It’s not going to be possible to set up discourse without a domain name.

Kacper_Kacper · February 18, 2025, 12:59am

so you can’t set up a forum without a domain name on a VPS server? because I just want to see how it runs without anything and what it looks like

Kacper_Kacper · February 18, 2025, 1:13am

i have domian and how to add on this serwer ?

Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: lemontest.online.
WARNING: Connection to http://lemontest.online (port 80) also fails.

This suggests that lemontest.online resolves to some IP address that does not reach this
machine where you are installing discourse.

The first thing to do is confirm that lemontest.online resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.

If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for “open ports YOUR CLOUD SERVICE” might help.

This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type

./launcher rebuild app

Arkshine · February 18, 2025, 1:31am

You likely need to wait for the DNS to propagate first.

tobiaseigen · February 18, 2025, 1:44am

If you want to just take Discourse for a spin you will be way better off just spinning up a free trial on our hosting. See Discourse pricing | Discourse - Civilized Discussion to sign up.

NateDhaliwal · February 18, 2025, 10:31am

Or, a development install on GitHub Codespaces is a quick way to create a development server.

Kacper_Kacper · February 18, 2025, 10:49am

New problem pls help

[BABEL] Note: The code generator has deoptimised the styling of /var/www/discourse/app/assets/javascripts/discourse/ember/ember-template-compiler.js as it exceeds the max of 500KB.
[BABEL] Note: The code generator has deoptimised the styling of /var/www/discourse/app/assets/javascripts/discourse/ember/ember.js as it exceeds the max of 500KB.
…[Babel: @glimmer/component > applyPatches]
…[Babel: @ember/test-waiters > applyPatches]
…[Babel: dialog-holder > applyPatches]
…[Babel: ember-this-fallback > applyPatches]
…[Babel: float-kit > applyPatches]
…[Babel: select-kit > applyPatches]
…[@embroider/compat/app]
…[@embroider/webpack]
…[@embroider/webpack]
…[@embroider/webpack]
…[@embroider/webpack]
…[@embroider/webpack]
…[@embroider/webpack]
…[@embroider/webpack]
…[SourceMapConcat]
…[Babel: admin > applyPatches]
…[Babel: admin > applyPatches]
…[SourceMapConcat]
…[TerserWriter]
…[Babel: discourse > applyPatches]
…[SourceMapConcat]
…[TerserWriter]
…[Babel: discourse-plugins > applyPatches]
I, [2025-02-18T10:26:24.750667 #1] INFO – : Building
Environment: production
The setting ‘staticAddonTrees’ will default to true in the next version of Embroider and can’t be turned off. To prepare for this you should set ‘staticAddonTrees: true’ in your Embroider config.
The setting ‘staticAddonTestSupportTrees’ will default to true in the next version of Embroider and can’t be turned off. To prepare for this you should set ‘staticAddonTestSupportTrees: true’ in your Embroider config.
building…
undefined
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGKILL (Forced termination): ember build -prod

I, [2025-02-18T10:26:24.756178 #1] INFO – : Terminating async processes
I, [2025-02-18T10:26:24.756288 #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/15/bin/postmaster -D /etc/postgresql/15/main pid: 59
I, [2025-02-18T10:26:24.757035 #1] INFO – : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 126
126:signal-handler (1739874384) Received SIGTERM scheduling shutdown…
2025-02-18 10:26:24.760 UTC [59] LOG: received fast shutdown request
2025-02-18 10:26:24.764 UTC [59] LOG: aborting any active transactions
2025-02-18 10:26:24.789 UTC [59] LOG: background worker “logical replication launcher” (PID 73) exited with exit code 1
2025-02-18 10:26:24.791 UTC [68] LOG: shutting down
2025-02-18 10:26:24.793 UTC [68] LOG: checkpoint starting: shutdown immediate
126:M 18 Feb 2025 10:26:24.811 # User requested shutdown…
126:M 18 Feb 2025 10:26:24.811 * Saving the final RDB snapshot before exiting.
126:M 18 Feb 2025 10:26:24.816 * DB saved on disk
126:M 18 Feb 2025 10:26:24.816 # Redis is now ready to exit, bye bye…
2025-02-18 10:26:25.088 UTC [68] LOG: checkpoint complete: wrote 2489 buffers (1.9%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.098 s, sync=0.178 s, total=0.297 s; sync files=2471, longest=0.003 s, average=0.001 s; distance=17648 kB, estimate=17648 kB
2025-02-18 10:26:25.117 UTC [59] LOG: database system is shut down

FAILED

Pups::ExecError: cd /var/www/discourse && su discourse -c ‘bundle exec rake assets:precompile:build’ failed with return #<Process::Status: pid 1136 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn’
exec failed with the params {“cd”=>“$home”, “tag”=>“build”, “hook”=>“assets_precompile_build”, “cmd”=>[“su discourse -c ‘bundle exec rake assets:precompile:build’”]}
bootstrap failed with exit code 1
** 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.
5e2c50cc49948daebea3d0a08243a0c0fecc7160db84b4c4e0b995d0ab4b38c9

Kacper_Kacper · February 18, 2025, 7:58pm

i dont know to instal bostrap of this error

Ethsim2 · March 17, 2025, 12:00pm

when i got this error it was because the A record host wasn’t @ in name cheap

the last time i installed discourse propagation was within the hour, so the above is a good check for ports unreachable.

Topic		Replies	Views
Rebuild Failed, please help! Installation	7	908	September 28, 2022
Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue Installation	20	2381	January 25, 2024
Discourse Rebuild Failed to Bootstrap Installation	6	519	August 31, 2023
Bundle error on upgrade from v2.8.14 to v.3.0.0 Installation	3	961	February 11, 2023
Failing rebuild Installation	5	1063	March 13, 2023

Problem with installation on vps ubuntu

FAILED

Related topics