If you're using normal dashboard tunnels, it sounds like your tunnel got deleted or the token for it

CChaika If you're using normal dashboard tunnels, it sounds like your tunnel got deleted...

D

dave•6/22/23, 3:39 PM

I'm using quick tunnels

D

dave•6/22/23, 3:41 PM

dave@mbp demo-api % cloudflared tunnel --url http://127.0.0.1:54192
2023-06-22T15:39:32Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-06-22T15:39:32Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF |  Your quick Tunnel has been created! Visit it at (it may take some time to be reachable):  |
2023-06-22T15:39:34Z INF |  https://martin-dear-loads-handhelds.trycloudflare.com                                     |
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-06-22T15:39:34Z INF Version 2023.6.1
2023-06-22T15:39:34Z INF GOOS: darwin, GOVersion: go1.19.10, GoArch: arm64
2023-06-22T15:39:34Z INF Settings: map[ha-connections:1 protocol:quic url:http://127.0.0.1:54192]
2023-06-22T15:39:34Z INF Generated Connector ID: cb1c6869-b229-409d-9f82-17bf7f3ff979
2023-06-22T15:39:34Z INF cloudflared will not automatically update if installed by a package manager.
2023-06-22T15:39:34Z INF Initial protocol quic
2023-06-22T15:39:34Z INF ICMP proxy will use 10.50.2.46 as source for IPv4
2023-06-22T15:39:34Z INF ICMP proxy will use fe80::ea:17a4:384f:b607 in zone en7 as source for IPv6
2023-06-22T15:39:34Z INF Created ICMP proxy listening on 10.50.2.46:0

dave@mbp demo-api % cloudflared tunnel --url http://127.0.0.1:54192
2023-06-22T15:39:32Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-06-22T15:39:32Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF |  Your quick Tunnel has been created! Visit it at (it may take some time to be reachable):  |
2023-06-22T15:39:34Z INF |  https://martin-dear-loads-handhelds.trycloudflare.com                                     |
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-06-22T15:39:34Z INF Version 2023.6.1
2023-06-22T15:39:34Z INF GOOS: darwin, GOVersion: go1.19.10, GoArch: arm64
2023-06-22T15:39:34Z INF Settings: map[ha-connections:1 protocol:quic url:http://127.0.0.1:54192]
2023-06-22T15:39:34Z INF Generated Connector ID: cb1c6869-b229-409d-9f82-17bf7f3ff979
2023-06-22T15:39:34Z INF cloudflared will not automatically update if installed by a package manager.
2023-06-22T15:39:34Z INF Initial protocol quic
2023-06-22T15:39:34Z INF ICMP proxy will use 10.50.2.46 as source for IPv4
2023-06-22T15:39:34Z INF ICMP proxy will use fe80::ea:17a4:384f:b607 in zone en7 as source for IPv6
2023-06-22T15:39:34Z INF Created ICMP proxy listening on 10.50.2.46:0

dave@mbp demo-api % cloudflared tunnel --url http://127.0.0.1:54192
2023-06-22T15:39:32Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-06-22T15:39:32Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF |  Your quick Tunnel has been created! Visit it at (it may take some time to be reachable):  |
2023-06-22T15:39:34Z INF |  https://martin-dear-loads-handhelds.trycloudflare.com                                     |
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-06-22T15:39:34Z INF Version 2023.6.1
2023-06-22T15:39:34Z INF GOOS: darwin, GOVersion: go1.19.10, GoArch: arm64
2023-06-22T15:39:34Z INF Settings: map[ha-connections:1 protocol:quic url:http://127.0.0.1:54192]
2023-06-22T15:39:34Z INF Generated Connector ID: cb1c6869-b229-409d-9f82-17bf7f3ff979
2023-06-22T15:39:34Z INF cloudflared will not automatically update if installed by a package manager.
2023-06-22T15:39:34Z INF Initial protocol quic
2023-06-22T15:39:34Z INF ICMP proxy will use 10.50.2.46 as source for IPv4
2023-06-22T15:39:34Z INF ICMP proxy will use fe80::ea:17a4:384f:b607 in zone en7 as source for IPv6
2023-06-22T15:39:34Z INF Created ICMP proxy listening on 10.50.2.46:0

dave@mbp demo-api % cloudflared tunnel --url http://127.0.0.1:54192
2023-06-22T15:39:32Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2023-06-22T15:39:32Z INF Requesting new quick Tunnel on trycloudflare.com...
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF |  Your quick Tunnel has been created! Visit it at (it may take some time to be reachable):  |
2023-06-22T15:39:34Z INF |  https://martin-dear-loads-handhelds.trycloudflare.com                                     |
2023-06-22T15:39:34Z INF +--------------------------------------------------------------------------------------------+
2023-06-22T15:39:34Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2023-06-22T15:39:34Z INF Version 2023.6.1
2023-06-22T15:39:34Z INF GOOS: darwin, GOVersion: go1.19.10, GoArch: arm64
2023-06-22T15:39:34Z INF Settings: map[ha-connections:1 protocol:quic url:http://127.0.0.1:54192]
2023-06-22T15:39:34Z INF Generated Connector ID: cb1c6869-b229-409d-9f82-17bf7f3ff979
2023-06-22T15:39:34Z INF cloudflared will not automatically update if installed by a package manager.
2023-06-22T15:39:34Z INF Initial protocol quic
2023-06-22T15:39:34Z INF ICMP proxy will use 10.50.2.46 as source for IPv4
2023-06-22T15:39:34Z INF ICMP proxy will use fe80::ea:17a4:384f:b607 in zone en7 as source for IPv6
2023-06-22T15:39:34Z INF Created ICMP proxy listening on 10.50.2.46:0

C

ChaikaOP•6/22/23, 3:43 PM

hmmm, if you try to start it up now, do you get

Tunnel ID: invalid UUID length: 0

Tunnel ID: invalid UUID length: 0

Tunnel ID: invalid UUID length: 0

Tunnel ID: invalid UUID length: 0?

C

ChaikaOP•6/22/23, 3:44 PM

it doesn't seem to work for me either, I either get that error above, or the same unauthorized, across two machines

C

ChaikaOP•6/22/23, 3:46 PM

... and now they seem to work fine again, interesting
Still some errors/reconnects until they get working. If you try now, does it eventually work?
I guess they did say the service is without any guarantees lol

D

dave•6/22/23, 3:49 PM

oh now it's working

D

dave•6/22/23, 3:50 PM

C

ChaikaOP•6/22/23, 3:50 PM

yea looks like it was a bad deployment on their end or something, I had the same issue at first, and then started getting more and more successful connections. Only on Quick Tunnels though, my real tunnels seemed unaffected, I restarted one to test, but ymmv

D

dave•6/22/23, 3:51 PM

my real tunnel was degraded.

P

Ping for toast•6/22/23, 5:36 PM

I don't understand snippets. I have a workers site, why would I use snippets instead?

P

Ping for toast•6/22/23, 5:37 PM

Are they faster?

PPing for toast I don't understand snippets. I have a workers site, why would I use snippets ins...

H

Hello, I’m Allie!•6/22/23, 5:38 PM

They are free, and they can be triggered by a Rules Engine statement

H

Hello, I’m Allie!•6/22/23, 5:38 PM

Though I don’t think you can use them to run Sites

C

ChaikaOP•6/22/23, 5:39 PM

Very simple things like wanting to redirect based on a regex/parsed URL, before you had to do a full worker for, now you can easily do it in a snippet.

C

ChaikaOP•6/22/23, 5:39 PM

plus you can chain them

P

Ping for toast•6/22/23, 5:40 PM

I have a mostly static cloudflare pages site and just need to change a couple of lines of text on the page. Could snippets work for that?

C

ChaikaOP•6/22/23, 5:41 PM

eeeeeeeeh that's not very simple. Maybe, you could certainly do so with a normal worker and the html rewriter, but Snippets have very limited CPU (5ms) and memory (2 MB), might be cutting it close, if it's a very small html page, maybe

CChaika eeeeeeeeh that's not very simple. Maybe, you could certainly do so with a normal...

P

Ping for toast•6/22/23, 5:41 PM

Yeah I'm using the HTML rewriter rn

W

Walshy•6/22/23, 5:42 PM

that should easily be able to fit

W

Walshy•6/22/23, 5:42 PM

We stream through HTMLRewriter, it doesn't use a lot of CPU

W

Walshy•6/22/23, 5:42 PM

if you were trying to parse it all, I'd say you'd have issues. Just changing a bit of text, sounds doable to me

WWalshy if you were trying to parse it all, I'd say you'd have issues. Just changing a b...

P

Ping for toast•6/22/23, 5:43 PM

Yup. Just finding an id, changing the text content

PPing for toast Yeah I'm using the HTML rewriter rn

C

ChaikaOP•6/22/23, 5:43 PM

if you already have it deployed, you should be able to see the CPU time from the existing worker

P

Ping for toast•6/22/23, 5:43 PM

Cool and just to be clear, the main advantage of the snippet engine is that it's completely free?

W

Walshy•6/22/23, 5:43 PM

and it's got the powerful ruleset engine for specific invocation

WWalshy and it's got the powerful ruleset engine for specific invocation

P

Ping for toast•6/22/23, 5:44 PM

Makes sense. I'll check my stats for the worker

C

ChaikaOP•6/22/23, 5:45 PM

I think the main advantage is being able to use them for really customizable rules using ruleset engine to trigger, even in front of Workers themselves. Workers are pretty cheap

P

Ping for toast•6/22/23, 5:45 PM

This would be excellent actually. A good part of my quota is just dedicated to a high traffic static site with a very simple worker

W

Walshy•6/22/23, 5:46 PM

hahaha err yeah, that should work

C

ChaikaOP•6/22/23, 5:46 PM

is it confirmed that cache isn't an extra subrequest, since you only get one?

W

Walshy•6/22/23, 5:46 PM

Cache doesn't count towards a subrequest afaik

P

Ping for toast•6/22/23, 5:47 PM

Is there any performance difference between workers and snippets?

W

Walshy•6/22/23, 5:47 PM

I'd have to test it to be 100% sure but it should be fine

PPing for toast Is there any performance difference between workers and snippets?

W

Walshy•6/22/23, 5:47 PM

Snippets are just Workers so no

WWalshy Cache doesn't count towards a subrequest afaik

K

kian•6/22/23, 5:49 PM

It counts towards the 50 on a normal Worker meowthinking

K

kian•6/22/23, 5:49 PM

Is snippets special?

P

Ping for toast•6/22/23, 5:49 PM

owch. let's see if we can trim this down

P

Ping for toast•6/22/23, 5:50 PM

wow pages with full SSR are only a couple ms slower than this simple worker... I have some optimization to do!

Kkian It counts towards the 50 on a normal Worker <:meowthinking:350680941804388352>

W

Walshy•6/22/23, 5:51 PM

oh it does? damn

W

Walshy•6/22/23, 5:51 PM

nevermind then

K

kian•6/22/23, 5:51 PM

it’s not supposed to but they also didnt plan to fix it since “50 is enough”

K

kian•6/22/23, 5:51 PM

W

Walshy•6/22/23, 5:51 PM

the 1 subrequest limit is a little awkward ablobsweats

Kkian it’s not supposed to but they also didnt plan to fix it since “50 is enough”

W

Walshy•6/22/23, 5:52 PM

ah...

W

Walshy•6/22/23, 5:52 PM

that makes sense

W

Walshy•6/22/23, 5:52 PM

yeah we should probably fix that now for Snippets

K

kian•6/22/23, 5:52 PM

well, fix as in move it to be inhouse subreq like KV/etc

P

Ping for toast•6/22/23, 5:53 PM

is there any detailed docs about the expensive parts of HTMLRewriter? It would be interesting to know what's consuming the largest amount of CPU time

K

kian•6/22/23, 5:53 PM

kj::Own<CacheClient> IoContext::getCacheClient() {
  // TODO(someday): Should Cache API requests be considered in-house? They are already not counted
  //   as subrequests in metrics and logs (like in-house requests aren't), but historically the
  //   subrequest limit still applied. Since I can't currently think of a use case for more than 50
  //   cache API requests per request, I'm leaving it as-is for now.
  limitEnforcer->newSubrequest(false);
  return getIoChannelFactory().getCache();
}

kj::Own<CacheClient> IoContext::getCacheClient() {
  // TODO(someday): Should Cache API requests be considered in-house? They are already not counted
  //   as subrequests in metrics and logs (like in-house requests aren't), but historically the
  //   subrequest limit still applied. Since I can't currently think of a use case for more than 50
  //   cache API requests per request, I'm leaving it as-is for now.
  limitEnforcer->newSubrequest(false);
  return getIoChannelFactory().getCache();
}

kj::Own<CacheClient> IoContext::getCacheClient() {
  // TODO(someday): Should Cache API requests be considered in-house? They are already not counted
  //   as subrequests in metrics and logs (like in-house requests aren't), but historically the
  //   subrequest limit still applied. Since I can't currently think of a use case for more than 50
  //   cache API requests per request, I'm leaving it as-is for now.
  limitEnforcer->newSubrequest(false);
  return getIoChannelFactory().getCache();
}

kj::Own<CacheClient> IoContext::getCacheClient() {
  // TODO(someday): Should Cache API requests be considered in-house? They are already not counted
  //   as subrequests in metrics and logs (like in-house requests aren't), but historically the
  //   subrequest limit still applied. Since I can't currently think of a use case for more than 50
  //   cache API requests per request, I'm leaving it as-is for now.
  limitEnforcer->newSubrequest(false);
  return getIoChannelFactory().getCache();
}

W

Walshy•6/22/23, 5:53 PM

that says

false

false

though

If you're using normal dashboard tunnels, it sounds like your tunnel got deleted or the token for it

Similar Threads

Similar Threads

Similar Threads