Bug Description
When adding a new project with a custom domain that uses Cloudflare DNS with Proxy enabled (orange cloud), accessing the domain results in Cloudflare Error 525: SSL Handshake Failed.
This occurs because Cloudflare expects a valid SSL certificate (or a self-signed/internal certificate depending on Cloudflare's SSL/TLS mode like Full/Strict) on the openship-edge reverse proxy, but openship-edge fails to terminate or negotiate the SSL handshake for new hostnames upon project creation.
Error Output / Evidence
SSL handshake failed Error code 525
What happened?
Cloudflare is unable to establish an SSL connection to the origin server.
It appears that the SSL configuration used is not compatible with Cloudflare.
Steps to Reproduce
Create a new project in Openship (v0.4.8) and attach a custom domain (e.g., app.example.xyz).
Point the domain's DNS to the server IP via Cloudflare with Proxy Enabled (Orange Cloud).
Access the domain in a browser (https://app.example.xyz).
Observe Cloudflare Error 525 (SSL Handshake Failed) on the host edge.
Expected Behavior
openship-edge should automatically issue/serve a valid SSL certificate (or properly handle SNI fallback) when a new domain is attached to a project.
Alternatively, Openship should support self-signed internal cert generation so Cloudflare's Full/Strict SSL proxying mode can complete the handshake seamlessly.
Bug Description
When adding a new project with a custom domain that uses Cloudflare DNS with Proxy enabled (orange cloud), accessing the domain results in Cloudflare Error 525: SSL Handshake Failed.
This occurs because Cloudflare expects a valid SSL certificate (or a self-signed/internal certificate depending on Cloudflare's SSL/TLS mode like Full/Strict) on the
openship-edgereverse proxy, butopenship-edgefails to terminate or negotiate the SSL handshake for new hostnames upon project creation.Error Output / Evidence
What happened?
Cloudflare is unable to establish an SSL connection to the origin server.
It appears that the SSL configuration used is not compatible with Cloudflare.
Steps to Reproduce
Create a new project in Openship (v0.4.8) and attach a custom domain (e.g., app.example.xyz).
Point the domain's DNS to the server IP via Cloudflare with Proxy Enabled (Orange Cloud).
Access the domain in a browser (https://app.example.xyz).
Observe Cloudflare Error 525 (SSL Handshake Failed) on the host edge.
Expected Behavior
openship-edge should automatically issue/serve a valid SSL certificate (or properly handle SNI fallback) when a new domain is attached to a project.
Alternatively, Openship should support self-signed internal cert generation so Cloudflare's Full/Strict SSL proxying mode can complete the handshake seamlessly.