# Kibana - Need help on MS SQL connector configuration **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [October 24, 2024, 8:45am UTC](https://discuss.elastic.co/t/kibana-need-help-on-ms-sql-connector-configuration/369335 "2024-10-24T08:45:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jerome\_Escamilla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerome_escamilla/32/137776_2.png) [@Jerome\_Escamilla](https://discuss.elastic.co/u/Jerome_Escamilla)\ **Post date:** [October 24, 2024, 8:45am UTC](https://discuss.elastic.co/t/kibana-need-help-on-ms-sql-connector-configuration/369335/1 "2024-10-24T08:45:29Z")
Hi Everyone, I'm trying do MS SQL connector configuration in Kibana using Docker but I can't continue because I can't run it in Docker and here is the instruction I'm following: ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/4/14ad38dc0879c89b26c6bbf74b6cd8ce8847966c.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/1/2116e847be5cf53b9aa2427976a1c01a419ddeb5.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/4/b44068f78e3ba6fca34c30b75e83d9286f7492c6.png) config.yml after editing ```auto ## ================= Elastic Connectors Configuration ================== # ## NOTE: Elastic Connectors comes with reasonable defaults. ## Before adjusting the configuration, make sure you understand what you ## are trying to accomplish and the consequences. # # ## ------------------------------- Connectors ------------------------------- # ## The list of connector clients/customized connectors configurations. ## Each object in the list requires `connector_id` and `service_type`. ## An example is: ## connectors: ## - connector_id: changeme # the ID of the connector. ## service_type: changeme # The service type of the connector. ## api_key: changeme # The Elasticsearch API key used to write data into the content index. #connectors: [] # # ## The ID of the connector. ## (Deprecated. Configure the connector client in an object in the `connectors` list) #connector_id: null # # ## The service type of the connector. ## (Deprecated. Configure the connector client in an object in the `connectors` list) #service_type: null # # ## ------------------------------- Elasticsearch ------------------------------- # ## The host of the Elasticsearch deployment. #elasticsearch.host: http://localhost:9200 # # ## The API key for Elasticsearch connection. ## Using `api_key` is recommended instead of `username`/`password`. #elasticsearch.api_key: null # # ## The username for the Elasticsearch connection. ## Using `username` requires `password` to also be configured. ## However, `elasticsearch.api_key` is the recommended configuration choice. #elasticsearch.username: elastic # # ## The password for the Elasticsearch connection. ## Using `password` requires `username` to also be configured. ## However, `elasticsearch.api_key` is the recommended configuration choice. #elasticsearch.password: changeme # # ## Whether SSL is used for the Elasticsearch connection. #elasticsearch.ssl: true # # ## Path to a CA bundle, e.g. /path/to/ca.crt #elasticsearch.ca_certs: null # # ## Whether to retry on request timeout. #elasticsearch.retry_on_timeout: true # # ## The request timeout to be passed to transport in options. #elasticsearch.request_timeout: 120 # # ## The maximum wait duration (in seconds) for the Elasticsearch connection. #elasticsearch.max_wait_duration: 60 # # ## The initial backoff duration (in seconds). #elasticsearch.initial_backoff_duration: 1 # # ## The backoff multiplier. #elasticsearch.backoff_multiplier: 2 # # ## Elasticsearch log level #elasticsearch.log_level: INFO # # ## Maximum number of times failed Elasticsearch requests are retried, except bulk requests #elasticsearch.max_retries: 5 # # ## Retry interval between failed Elasticsearch requests, except bulk requests #elasticsearch.retry_interval: 10 # # ## ------------------------------- Elasticsearch: Bulk ------------------------ # ## Options for the Bulk API calls behavior - all options can be ## overridden by each source class # # ## The number of docs between each counters display. #elasticsearch.bulk.display_every: 100 # # ## The max size of the bulk queue #elasticsearch.bulk.queue_max_size: 1024 # # ## The max size in MB of the bulk queue. ## When it's reached, the next put operation waits for the queue size to ## get under that limit. #elasticsearch.bulk.queue_max_mem_size: 25 # # ## Minimal interval of time between MemQueue checks for being full #elasticsearch.bulk.queue_refresh_interval: 1 # # ## Maximal interval of time during which MemQueue does not dequeue a single document ## For example, if no documents were sent to Elasticsearch within 60 seconds because of ## Elasticsearch being overloaded, then an error will be raised. ## This mechanism exists to be a circuit-breaker for stuck jobs and stuck Elasticsearch. #elasticsearch.bulk.queue_refresh_timeout: 60 # # ## The max size in MB of a bulk request. ## When the next request being prepared reaches that size, the query is ## emitted even if `chunk_size` is not yet reached. #elasticsearch.bulk.chunk_max_mem_size: 5 # # ## The max size of the bulk operation to Elasticsearch. #elasticsearch.bulk.chunk_size: 500 # # ## Maximum number of concurrent bulk requests. #elasticsearch.bulk.max_concurrency: 5 # # ## Maximum number of concurrent downloads in the backend. #elasticsearch.bulk.concurrent_downloads: 10 # # ## Maximum number of times failed bulk requests are retried #elasticsearch.bulk.max_retries: 5 # # ## Retry interval between failed bulk attempts #elasticsearch.bulk.retry_interval: 10 # # ## Enable to log ids of created/indexed/deleted/updated documents during a sync. ## This will be logged on 'DEBUG' log level. Note: this depends on the service.log_level, not elasticsearch.log_level #elasticsearch.bulk.enable_operations_logging: false # ## ------------------------------- Elasticsearch: Experimental ------------------------ # ## Experimental configuration options for Elasticsearch interactions. # # ## Enable usage of Connectors API instead of calling connectors indices directly #elasticsearch.feature_use_connectors_api: false ## ------------------------------- Service ---------------------------------- # ## Connector service/framework related configurations # # ## The interval (in seconds) to poll connectors from Elasticsearch. #service.idling: 30 # # ## The interval (in seconds) to send a new heartbeat for a connector. #service.heartbeat: 300 # # ## The maximum number of retries for pre-flight check. #service.preflight_max_attempts: 10 # # ## The number of seconds to wait between each pre-flight check. #service.preflight_idle: 30 # # ## The maximum number of errors allowed in one event loop. #service.max_errors: 20 # # ## The number of seconds to reset `max_errors` count. #service.max_errors_span: 600 # # ## The maximum number of concurrent content syncs. #service.max_concurrent_content_syncs: 1 # # ## The maximum number of concurrent access control syncs. #service.max_concurrent_access_control_syncs: 1 # # ## The maximum size (in bytes) of files that the framework should be willing ## to download and/or process. #service.max_file_download_size: 10485760 # ## The interval (in seconds) to run job cleanup task. #service.job_cleanup_interval: 300 # # ## Connector service log level. #service.log_level: INFO # # ## ------------------------------- Extraction Service ---------------------------------- # ## Local extraction service-related configurations. ## These configurations are optional and are not included by default. ## The presence of these configurations enables local content extraction. ## By default, this whole object is `null`. ## See: https://www.elastic.co/guide/en/enterprise-search/current/connectors-content-extraction.html#connectors-content-extraction-local # # ## The host of the local extraction service. #extraction_service.host: null # # ## Request timeout for local extraction service requests, in seconds. #extraction_service.timeout: 30 # # ## Whether or not to use file pointers for local extraction. ## This can have very positive impacts on performance - ## both speed and memory consumption. ## However, it also requires that the Connectors deployment and the ## local extraction service deployment must share a filesystem. #extraction_service.use_file_pointers: False # # ## The size (in bytes) that files are chunked to for streaming when sending ## a file to the local extraction service. ## Only applicable if `extraction_service.use_file_pointers` is `false`. #extraction_service.stream_chunk_size: 65536 # # ## The location for files to be extracted from. ## Only applicable if `extraction_service.use_file_pointers` is `true`. #extraction_service.shared_volume_dir: /app/files # # ## ------------------------------- Sources ---------------------------------- # ## An object mapping service type names to class Fully Qualified Names ## E.g. `connectors.sources.mongo:MongoDataSource`. ## If adding a net-new connector, it must be added here for the framework to detect it. ## Default includes all tech preview, beta, and GA connectors in this repository. ## An example is: ## sources: ## mongodb: connectors.sources.mongo:MongoDataSource connectors: - connector_id: "CpvrupIB-q7RRtqst-qQ" service_type: "mssql" api_key: "SVFtZ3ZaSUItZDFiUkRpaHQzV0M6SVRoY3VNM2lRWEtUel9hY0E2VGttQQ==" elasticsearch: host: "http://localhost:9200" api_key: "SVFtZ3ZaSUItZDFiUkRpaHQzV0M6SVRoY3VNM2lRWEtUel9hY0E2VGttQQ==" ``` When trying to deploy to docker I'm getting this error: ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b80e410cd40dcc97b11d7c69f4499b179aa821cc.png) Is there something wrong with the syntax I'm using? I was able to make it work before Also If I choose the other option "Run from Source" how to do the make install and make run part? ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/4/a464ecd714d6aa365fb12832124dff4aab934691.png) ---
**Author:** ![eMitch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/emitch/32/93607_2.png) [@eMitch](https://discuss.elastic.co/u/eMitch)\ **Post date:** [October 30, 2024, 4:46pm UTC](https://discuss.elastic.co/t/kibana-need-help-on-ms-sql-connector-configuration/369335/2 "2024-10-30T16:46:02Z")
> [@Jerome\_Escamilla](#): > > ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b80e410cd40dcc97b11d7c69f4499b179aa821cc.png) i dont think the syntax with ...`"/connectors`... will work. try: `docker run -v "C:\Users\jerom\connectors\connectors-config:/config" --tty --rm docker.elastic.co/enterprise-search/elastic-connectors:8.15.0.0 /app/bin/elastic-ingest -c /config/config.yml` ---
**Author:** ![Jerome\_Escamilla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerome_escamilla/32/137776_2.png) [@Jerome\_Escamilla](https://discuss.elastic.co/u/Jerome_Escamilla)\ **Post date:** [October 31, 2024, 7:09am UTC](https://discuss.elastic.co/t/kibana-need-help-on-ms-sql-connector-configuration/369335/3 "2024-10-31T07:09:51Z")
> [@eMitch](#): > > \/connectors Hi Eddie, Thanks for the response, I was able to make it work now but I'm getting an issue regarding my certificate and I'm using the original default cert that was created during the installation. ```auto PS C:\WINDOWS\system32> docker run -v "C:\Users\jerom\connectors\connectors-config:/config" --tty --rm docker.elastic.co/enterprise-search/elastic-connectors:8.15.0.0 /app/bin/elastic-ingest -c /config/config.yml [FMWK][07:00:45][INFO] Running connector service version 8.15.0.0 [FMWK][07:00:45][INFO] Loading config from /config/config.yml [FMWK][07:00:45][INFO] Running preflight checks [FMWK][07:00:45][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 0 secs) [FMWK][07:00:45][ERROR] Could not connect to the Elasticsearch server [FMWK][07:00:45][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:00:46][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 1 secs) [FMWK][07:00:46][ERROR] Could not connect to the Elasticsearch server [FMWK][07:00:46][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:00:48][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 3 secs) [FMWK][07:00:48][ERROR] Could not connect to the Elasticsearch server [FMWK][07:00:48][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:00:52][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 7 secs) [FMWK][07:00:52][ERROR] Could not connect to the Elasticsearch server [FMWK][07:00:52][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:01:00][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 15 secs) [FMWK][07:01:00][ERROR] Could not connect to the Elasticsearch server [FMWK][07:01:00][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:01:16][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 31 secs) [FMWK][07:01:16][ERROR] Could not connect to the Elasticsearch server [FMWK][07:01:16][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:01:48][INFO] Waiting for Elasticsearch at https://192.168.100.69:9200 (so far: 63 secs) [FMWK][07:01:48][ERROR] Could not connect to the Elasticsearch server [FMWK][07:01:48][ERROR] Cannot connect to host 192.168.100.69:9200 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1007)')] [FMWK][07:02:52][CRITICAL] https://192.168.100.69:9200 seems to be unreachable. Bye! [FMWK][07:02:52][INFO] Bye PS C:\WINDOWS\system32> ``` Please see the screenshot and .ymls (I removed most of the commented lines to make it easier to read) I'm using for reference. Elastic ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/5/65fb4734144047043ab53f8cfd2e880a3d8c4486.png) ```auto #----------------------- BEGIN SECURITY AUTO CONFIGURATION ----------------------- # # The following settings, TLS certificates, and keys have been automatically # generated to configure Elasticsearch security features on 29-10-2024 09:02:12 # # -------------------------------------------------------------------------------- # Enable security features xpack.security.enabled: true xpack.security.enrollment.enabled: true # Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents xpack.security.http.ssl: enabled: true keystore.path: certs/http.p12 # Enable encryption and mutual authentication between cluster nodes xpack.security.transport.ssl: enabled: true verification_mode: certificate keystore.path: certs/transport.p12 truststore.path: certs/transport.p12 # Create a new cluster with the current node only # Additional nodes can still join the cluster later cluster.initial_master_nodes: ["JEROME"] # Allow HTTP API connections from anywhere # Connections are encrypted and require user authentication http.host: 0.0.0.0 # Allow other nodes to join the cluster from anywhere # Connections are encrypted and mutually authenticated #transport.host: 0.0.0.0 #----------------------- END SECURITY AUTO CONFIGURATION ------------------------- ``` Kibana ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/6/66bc792b8d25de0447b1ca0b76c6bbc70701edec.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/44e11a8dfd6dcd2b762e91b19f704240b5a07030.png) ```auto elasticsearch.hosts: ['https://192.168.100.69:9200'] elasticsearch.serviceAccountToken: AAEAAWVsYXN0aWMva2liYW5hL2Vucm9sbC1wcm9jZXNzLXRva2VuLTE3MzAxOTMxOTczNTc6ZEQyQmJjQVFSZC1FdjYxbWxsNDJidw elasticsearch.ssl.certificateAuthorities: ['C:\Users\jerom\OneDrive\Desktop\ES\kibana-8.15.3\kibana-8.15.3\data\ca_1730193198512.crt'] xpack.fleet.outputs: [{id: fleet-default-output, name: default, is_default: true, is_default_monitoring: true, type: elasticsearch, hosts: ['https://192.168.100.69:9200'], ca_trusted_fingerprint: b01873cc24498cfc7850ba5277b9a737b23cb1b6c1e8b6badba9b5d9fbeb7406}] ``` config.yml ```auto connectors: - connector_id: "P7tb4ZIBNu3kZhyEiuCc" service_type: "mssql" api_key: "UUx0YzRaSUJOdTNrWmh5RUh1QUo6SUhGY2VnZVVRWFM4NDZOTHNhcUNadw==" elasticsearch: host: "https://192.168.100.69:9200" api_key: "UUx0YzRaSUJOdTNrWmh5RUh1QUo6SUhGY2VnZVVRWFM4NDZOTHNhcUNadw==" ```