Solved Could not fetch specs from https://rubygems.org/

[Neluser]

Hello. I had a completely full memory on the server. Therefore, the platform has ceased to start correctly. I scaled the server and added more memory to disk. After that, the platform started working correctly, but the redmine application stopped starting. Recovering from backup, removing plugins did not give any results.
The log shows that there is a problem connecting to https://rubygems.org/
How can I fix this problem

Thanks.

=> Ensure directories
Apr 21 16:31:36 => Generate database config
Apr 21 16:31:36 => Generate email config
Apr 21 16:31:36 => Fixing /tmp permissions
Apr 21 16:31:36 => Refresh gems for current ruby version
Apr 21 16:31:36 The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x64-mingw32, x86-mswin32. To add those platforms to the bundle, run bundle lock --add-platform x86-mingw32 x64-mingw32 x86-mswin32.
Apr 21 16:31:36 The dependency ffi (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x64-mingw32, x86-mswin32. To add those platforms to the bundle, run bundle lock --add-platform x86-mingw32 x64-mingw32 x86-mswin32.
Apr 21 16:31:56 Fetching source index from https://rubygems.org/
Apr 21 16:32:06
Apr 21 16:32:16 Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/
Apr 21 16:32:26 Retrying fetcher due to error (3/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/
Apr 21 16:32:36 Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/
Apr 21 16:32:36 Could not fetch specs from https://rubygems.org/

[nebulon]

Have you followed all the steps outlined in the docs for such a situation, especially https://docs.cloudron.io/troubleshooting/#unbound may be relevant here.

[Neluser]

@nebulon Thanks!!!
I followed the recommendations and I managed to fix it.
I tried to do in the application terminal itself.
But it turned out it was necessary to use the server terminal. (feel stupid )
The problem was with the "Unbound" service.