fix: use created listener when serving tls (#530)

Issue was being encountered where configured LISTEN_On address and port
were being disregarded when running with TLS enabled. This was happening
because we were not using the configured listener.

Signed-off-by: Mikhail Swift <mikhail@testifysec.com>

Author: Mikhail Swift

cmd/archivista/main.go

@@ -89,8 +89,8 @@ func main() {
 
 	go func() {
 		if archivistaService.Cfg.EnableTLS {
-			if err := srv.ListenAndServeTLS(archivistaService.Cfg.TLSCert, archivistaService.Cfg.TLSKey); err != nil {
-				logrus.Fatalf("unable to start http serveR: %+v", err)
+			if err := srv.ServeTLS(listener, archivistaService.Cfg.TLSCert, archivistaService.Cfg.TLSKey); err != nil {
+				logrus.Fatalf("unable to start http server: %+v", err)
 			}
 		} else {
 			if err := srv.Serve(listener); err != nil {