@dsuresh (suresh) posted a new topic, subject "Gitlab read repository". It read:

   ##  Describe the issue/error/question
    
    Trying to read gitlab repository information using gitlab access token
    
    ##  What is the error message (if any)?
    
    {  
    “message”: “self signed certificate in certificate chain”,  
    “name”: “Error”,  
    “stack”: “Error: self signed certificate in certificate ibrooks@example.net (_tls_wrap.js:1497:34) at TLSSocket.emit (events.js:315:20) at TLSSocket._finishInit (_tls_wrap.js:932:8) at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)”,  
    “code”: “SELF_SIGNED_CERT_IN_CHAIN”  
    }
    
    ##  Please share the workflow
    [code] 
        (Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)
        
    [/code]
    
    ##  Share the output returned by the last node
    
    ##  Information on your n8n setup
    
      * **n8n version: 0.178.2
      * **Database you're using (default: SQLite):SQLite
      * **Running n8n with the execution process [own(default), main]: Browser
      * **Running n8n via [Docker, npm, n8n.cloud, desktop app]:**

@Jon (Jon) replied

    Hey @dsuresh,
    
    Can you fill out all of the template so that we know how you are running n8n and what version you are using.
    
    Are you self hosting Gitlab as well? The error looks like you are using a self signed certificate and we don't have an option to ignore certificate errors with the Gitlab node at the moment.

So @joeldeteves (Joel DeTeves) replied

    Adding to what @Jon said, you may be able to work around this issue using the `http` node as it has an option to ignore SSL:
    
    image604×881 26.1 KB
    
    But TLDR; fix your certificate issue

@dsuresh (suresh) replied

    Jon:
    
    > as
    
    I have updated the ticket with more details. Not self hosting gitlab.

@Jon (Jon) replied

    Really? That surprises me. Is it npm, docker or desktop?
    
    Sadly if you are getting a self signed certificate back it is going to be something on your network like a proxy or AV trying to do content inspection or there is something wrong with Gitlab.
    
    The only thing we could do is add an option to ignore cert errors but in cases like this it is probably good to know something is possibly intercepting your traffic.


{'source': 'discourse', 'url': 'https://community.n8n.io/t/gitlab-read-repository/18996', 'title': 'Gitlab read repository', 'views': 10, 'has_accepted_answer': False, 'word_count': 372, 'like_count': 0, 'reply_count': 3, 'participant_count': 3, 'posts': 5, 'tags': '', 'author': '@dsuresh (suresh)', 'participants': '@dsuresh (suresh), @Jon (Jon), @joeldeteves (Joel DeTeves)', 'image_url': [None], 'created_at': '2022-10-24T16:42:01.606Z', 'last_posted_at': '2022-10-24T20:20:45.087Z'}