Exception when renewing certificate for tracking domain when tracking domain no longer exists

[willpower232]

A couple of our older organizations within Postal have fallen out of use and not been cleaned up which has meant that the tracking domains for them no longer exist.

The certificate renewal process has started throwing an exception in this case: Faraday::ConnectionFailed: Connection reset by peer - SSL_connect

A solution is to turn off SSL for the tracking domains in question but also I believe the code could handle this situation better as presumably it can be triggered by any form of losing the tracking domain.

Sentry tracks the offending line of code as https://github.com/atech/postal/blob/634d3af59d392e84bdcd2b843b427f3a79d3ff4c/app/models/track_certificate.rb#L55 but I'm not precisely sure what the problem is.

Even some basic exception handling would improve the situation, I just don't know enough ruby to sort it out!

Stack trace is here but the line numbers are slightly different for some reason

Errno::ECONNRESET: Connection reset by peer - SSL_connect
  from net/protocol.rb:44:in `connect_nonblock'
  from net/protocol.rb:44:in `ssl_socket_connect'
  from net/http.rb:928:in `connect'
  from net/http.rb:863:in `do_start'
  from net/http.rb:852:in `start'
  from net/http.rb:1384:in `request'
  from faraday/adapter/net_http.rb:80:in `perform_request'
  from faraday/adapter/net_http.rb:38:in `block in call'
  from faraday/adapter/net_http.rb:85:in `with_net_http_connection'
  from faraday/adapter/net_http.rb:33:in `call'
  from acme/client/faraday_middleware.rb:18:in `call'
  from faraday/rack_builder.rb:143:in `build_response'
  from faraday/connection.rb:387:in `run_request'
  from faraday/connection.rb:138:in `get'
  from acme/client/resources/authorization.rb:15:in `verify_status'
  from acme/client/resources/challenges/base.rb:13:in `verify_status'
  from app/models/track_certificate.rb:57:in `verify'
  from app/models/track_certificate.rb:35:in `get'
  from app/jobs/renew_track_certificates_job.rb:6:in `block in perform'
  from active_record/relation/delegation.rb:39:in `each'
  from active_record/relation/delegation.rb:39:in `each'
  from app/jobs/renew_track_certificates_job.rb:4:in `perform'
  from lib/postal/worker.rb:55:in `receive_job'
  from lib/postal/worker.rb:88:in `block in join_queue'
  from bunny/consumer.rb:56:in `call'
  from bunny/channel.rb:1703:in `block in handle_frameset'
  from bunny/consumer_work_pool.rb:97:in `block (2 levels) in run_loop'
  from bunny/consumer_work_pool.rb:92:in `loop'
  from bunny/consumer_work_pool.rb:92:in `block in run_loop'
  from bunny/consumer_work_pool.rb:91:in `catch'
  from bunny/consumer_work_pool.rb:91:in `run_loop'

[willpower232]

Tracking certificates have left the building so this is no longer an issue past me.