13:17 <Haris_> hello all

13:18 <Haris_> gitlab is using ruby 3.0.0 with bundler and oauth is part of it. I changed SSL Cert and now puma is failing saying ====> 2024-06-24_13:16:35.71631 {"timestamp":"2024-06-24T13:16:35.704Z","pid":2641,"message":"! Unable to load application: Bundler::GemRequireError: There was an error while trying to load the gem 'omniauth-twitter'.\nGem Load Error is: The SSL CERT provided does not exist.\nBacktrace for gem load

13:18 <Haris_> error is:\n/opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/oauth-0.5.6/lib/oauth/consumer.rb:15:in `\u003cclass:Consumer\u003e'\n/opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/oauth-0.5.6/lib/oauth/consumer.rb:9:in

13:18 <Haris_> ..lengthy stack trace

13:19 <Haris_> on first look, in the stack trace its not dumping what config it picked up that it can't find or which is leading it to not have the SSL Cert

13:20 <Haris_> from the stack trace ===> 2024-06-24_13:16:31.36870 /opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/oauth-0.5.6/lib/oauth/consumer.rb:15:in `<class:Consumer>': The SSL CERT provided does not exist. (RuntimeError)

13:20 <Haris_> how do I find out what SSL cert it is getting that its unable to find?

13:30 <adam12> Haris_: Might be a bit challenging to debug Gitlab because of how they package things but I'd try to use `rdbg` and set a breakpoint on that line. Then see if you can go up and find the certificate path.

13:32 <adam12> So something like `rdbg -c <command you run to start gitlab>` then `b /opt/gitlab/embedded/lib/ruby/gems/3.0.0/gems/oauth-0.5.6/lib/oauth/consumer.rb:15 ;; c` or something