beameio / beame-insta-ssl

HTTP is over. Don’t get left behind. Get free, secure HTTPS tunneling to your machine! Quick start here!

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

CNAME to beam hostname

dok18 opened this issue · comments

commented

Hi,

I am trying to use a CNAME on my private domain (i.e. test.example.com) to my beame-insta-ssl hostname (i.e. xxxxx.v1.p.beameio.net).

I am not able to establish connection.

user@host ~ $ host test.example.com
test.example.com is an alias for xxxxx.v1.p.beameio.net.
xxxxx.v1.p.beameio.net is an alias for xxxxx.tr9k0gta5imrufpf.v1.p.beameio.net.
xb5fbpf258kpvl3v.tr9k0gta5imrufpf.v1.p.beameio.net is an alias for ec2-35-157-75-47.eu-central-1.compute.amazonaws.com.
ec2-35-157-75-47.eu-central-1.compute.amazonaws.com has address 35.157.75.47
user@host ~ $ curl -vi https://test.example.com
*   Trying 35.157.75.47...
* TCP_NODELAY set
* Connected to test.example.com (35.157.75.47) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* Unknown SSL protocol error in connection to test.example.com:443 
* Curl_http_done: called premature == 1
* Closing connection 0
curl: (35) Unknown SSL protocol error in connection to test.example.com:443 

Is this even possible?

Thanks.

commented

Someone reading this?

yes, sorry. U can not use beame-insta with private domains today not part of the usecase