Target with Tailscale failing after new https rule

[franse]

Hello all
Wappler 7.9.4
NodeJS

After this:

Local Development with HTTPS

Intro Wappler now supports local development using HTTPS out of the box. This is ideal for testing APIs, authentication flows, or any feature that requires a secure connection - all without needing a real domain or external certificate. [!NOTE] This feature is available only for Wappler local and Docker targets using Node.js. Automatic SSL Certificate Generation with mkcert Wappler integrates the mkcert tool to automatically generate local SSL certificates. You don’t need to install or co…

I imagine that all targets running development with https will try to create and use a cert..

But now my target using magicdns will fail:

  https: {
    enabled: true,
    options: {
      key: 'desktop****.ts.net-key.pem',
      cert: 'desktop****.ts.net.pem',
      ca: null
    }

Which ends in:

Error: ENOENT: no such file or directory, open 'E:\xampp\htdocs\****\certs\desktop****.ts.net-key.pem'
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'E:\\xampp\\htdocs\\****\\certs\\desktop****.ts.net-key.pem'
}

Is there a chance to avoid this?

[guptast]

Hi Francisco,

I’ve been using Tailscale and Tailnet in my projects. The error indicates that Tailscale cannot find the valid certificates that match the magicdns name. These certificates might be missing (Wappler didn’t create them locally) or have different names.

I haven’t set up or used magicdns to access the local machine using https; instead, I use Tailscale to create internal networking between web apps, databases and access servers and databases from the local machine.

Have you thought about using Tailscale Funnel to expose local resources through a secure connection?

Tailscale Funnel · Tailscale Docs

[franse]

Hey @guptast thank you as always for the reply..

The problem here is that I'm using funnel, the address starts with https, so not possible to use that address in the Wappler project url under development without Wappler trying to create the certs..

I can use instead, localhost:4000 and then manually enter to the tailscale address which is the same result, but that makes everytime I need to preview something from Wappler, the browser will open localhost instead the tailscale one (so I need to edit each tab url)

Of course is not a big problem, and I think is a very isolated one..
But maybe there's another workaround..

Hope I made myself clear and thanks again

[guptast]

I get what you are saying. Tailscale Funnel needs its own certificates, and Wappler seems to create its own when you start a project url with https.

From what I can see, there is no option in Wappler’s Project Target settings to use Tailscale certificates instead of making new ones, at least not in the interface.

Another thing you might want to look into is ‘cloudflared’. It’s a secure tunnel that connects your machine’s outgoing traffic to Cloudflare’s network, and you can access it through a public HTTPS URL. Plus, you won’t need a certificate, Tailscale Funnel or any changes to how you access your local project on ports 3000 or 8100.

[franse]

It's not about the cert, it's about trying to use an https url in target url without Wappler forcing to create a custom https cert..

[guptast]

Perhaps Wappler team can provide an option in Wappler's Project Target settings interface to use different certificates when https protocol is enabled for local targets.