Skip to content

config option noTLSVerify does not work #707

Description

@ivanixgames

Trying to get cloudflare tunnel to support https with a ssl cert in my server.
It seems from documentation that the noTLSVerify option in the config.yaml is what supposed to be used, but does not.
Can anyone confirm if ssl is indeed required or not?
Here is my config as i followed from a previous bug submission (#277)

-----------------
tunnel: mytunnel
credentials-file: /home/ubuntu/.cloudflared/xxxxxxxx.json

originRequest:
  noTLSVerify: true

ingress:
  - service: https://xx.xx.xx.xx:443
    hostname: my.sub.mydomain.com
  - service: http://xx.xx.xx.xx:80
    hostname:  my.sub.mydomain.com
  - service: http_status:404
------------------------------------------------
$ cloudflared tunnel run  mytunnel
 Comes up ok, no obvious errors or other.
 ------------------------------------------------
 In browser: 
 https://my.sub.mydomain.com
 displays
 --------------------------------------------
This site can’t provide a secure connection sub2.sub1.mydomain.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
-----------------------------------------

Also, I tried using an origin cert generated by cloudflare, it seems also not to be recognized.
Ultimately i was hoping to get wildcard supported but even specific hostname not working.

Anyone have any ideas?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority: NormalMinor issue impacting one or more usersType: BugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions