ta-daa

Ddave isn't WARP supposed to be instant?

H

Hello, I’m Allie!•5/20/23, 10:17 PM

Up to 1 minute, I think

D

dave•5/20/23, 10:17 PM

same

D

dave•5/20/23, 10:17 PM

even used my iPhone

Y

yigitOP•5/20/23, 10:17 PM

thank you for your efforts, but will be same for you in few seconds I think

Yyigit thank you for your efforts, but will be same for you in few seconds I think

H

Hello, I’m Allie!•5/20/23, 10:18 PM

Renders fine, shows proxied through ORD

D

dave•5/20/23, 10:18 PM

fl=368f25
h=wope.com
ip=removed
ts=1684621097.855
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
colo=MIA
sliver=005-tier1
http=http/3
loc=KY
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

fl=368f25
h=wope.com
ip=removed
ts=1684621097.855
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
colo=MIA
sliver=005-tier1
http=http/3
loc=KY
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

fl=368f25
h=wope.com
ip=removed
ts=1684621097.855
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
colo=MIA
sliver=005-tier1
http=http/3
loc=KY
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

fl=368f25
h=wope.com
ip=removed
ts=1684621097.855
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36
colo=MIA
sliver=005-tier1
http=http/3
loc=KY
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

Original message was deleted

D

dave•5/20/23, 10:18 PM

huh I thought WARP no longer was supposed to leak your IP?

Yyigit ta-daa

D

dave•5/20/23, 10:19 PM

try clearing your cache

D

dave•5/20/23, 10:19 PM

stupid I know

Original message was deleted

D

dave•5/20/23, 10:19 PM

oh what.

D

dave•5/20/23, 10:19 PM

but... I haz cloudflare IP

D

dave•5/20/23, 10:19 PM

I'm using WireGuard though

Yyigit thank you for your efforts, but will be same for you in few seconds I think

D

dave•5/20/23, 10:19 PM

yeah I can't get the error

Ddave I'm using WireGuard though

H

Hello, I’m Allie!•5/20/23, 10:20 PM

Maybe the IP eraser thing requires the WARP app?

HHello, I’m Allie!Maybe the IP eraser thing requires the WARP app?

D

dave•5/20/23, 10:20 PM

that'd be weird.

H

Hello, I’m Allie!•5/20/23, 10:22 PM

IIRC, the app does do more than just enable/disable a Wireguard tunnel

H

Hello, I’m Allie!•5/20/23, 10:22 PM

So it shouldn’t be out of the ballpark

Y

yigitOP•5/20/23, 10:22 PM

I have tried with VPNs and seems like fixed

Y

yigitOP•5/20/23, 10:23 PM

yeap guys, this issue only affects my IP, totally weird.

Yyigit ta-daa

Y

yigitOP•5/20/23, 10:24 PM

the weirdest part is that, it only happens in Portugal - when I use VPN and go another location, it works. but all Portugal IPs in ProtonVPN, it returns same error

Yyigit I have tried with VPNs and seems like fixed

H

Hello, I’m Allie!•5/20/23, 10:24 PM

Depending on what your Worker is doing, it might be an edge case to do with your colo(or something else), that causes an infinite loop. If you are able to give us some insight into what your code is doing(or a repo if you got one), then we might be able to help you.

HHello, I’m Allie!Depending on what your Worker is doing, it might be an edge case to do with your...

Y

yigitOP•5/20/23, 10:24 PM

actually nothing, ordinary use of Zaraz + Cloudflare Pages - and not having any custom Workers, just using CF services with Workers

Yyigit actually nothing, ordinary use of Zaraz + Cloudflare Pages - and not having any ...

H

Hello, I’m Allie!•5/20/23, 10:27 PM

Just a full static site with Zaraz, is that what you mean?

Y

yigitOP•5/20/23, 10:27 PM

yes, it is

H

Hello, I’m Allie!•5/20/23, 10:27 PM

Hm…

H

Hello, I’m Allie!•5/20/23, 10:28 PM

I’ll try to see if there is something I can do…

Y

yigitOP•5/20/23, 10:28 PM

To me, it appears that the problem is fixed. However, if the continuous ban persists in Portugal, then the issue may recur. In such a case, the problem will likely be resolved automatically in due time.

HHello, I’m Allie!I’ll try to see if there is something I can do…

Y

yigitOP•5/20/23, 10:28 PM

thanks a lot for your close interest

don't forget to check from Portugal based IP

Yyigit thanks a lot for your close interest 🙏🏽 don't forget to check from Portugal ba...

H

Hello, I’m Allie!•5/20/23, 10:29 PM

Yup, I see it borks in Lisboa

M

matt•5/21/23, 1:56 AM

has anyone managed to get itty-router v4 types working with cloudflare's worker types? the main issue appears to be that both libraries have bespoke typings for

Request

Request

and

Response

Response

I

Ian•5/21/23, 11:46 AM

Hi guys, what is the best for simply "counting requests per user", I am have a hard time on the economics because each time a user does something a write request has to be made even just for logging, the cheapest write request is on durable objects but it still costs 1$/1M sweatguy

Z

zegevlier•5/21/23, 11:48 AM

Could #analytics-engine-beta work for your usecase?

Z

zegevlier•5/21/23, 11:49 AM

Otherwise, Durable Objects are the only thing that CF had that is really meant for strongly consistent counting

Zzegevlier Could #analytics-engine-beta work for your usecase?

I

Ian•5/21/23, 11:51 AM

It indeed does help, I am just worried because it is on beta and no pricing is available

I

Ian•5/21/23, 11:51 AM

Thanks tho

Z

zegevlier•5/21/23, 12:02 PM

That's very understandable. There was some discussion in that channel about how pricing might work but AFAIK nothing is firm on that yet

Zzegevlier That's very understandable. There was some discussion in that channel about how ...

I

Ian•5/21/23, 12:15 PM

i am not sure if I should bet on it tbh, if such a product exists for the purpose of usage-based-billing (this is what says in the docs for one of the usages apparently), it should have a much lower price if we compare it to existing storage options thonk

I

Ian•5/21/23, 12:15 PM

But then people may abuse it

S

sakuta•5/21/23, 3:30 PM

are there already type declarations for the TCP socket api?

K

kian•5/21/23, 3:51 PM

there should be

K

kian•5/21/23, 3:51 PM

not sure why there hasn't been a release

K

kian•5/21/23, 3:51 PM

K

kian•5/21/23, 3:51 PM

it's under the alpha tag for whatever reason

K

kian•5/21/23, 3:51 PM

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

M

Murder Chicken•5/21/23, 5:23 PM

Any reason why when upgrading to Wrangler 3 and using the latest

compatibility_date

compatibility_date

why creating new Request objects would result in an empty object? Using module syntax, trying to create any new requests from within a module results in

{}

{}

when outputting it to console even with

console.log(JSON.stringify(req))

console.log(JSON.stringify(req))

... bit stumped as this was working just fine before I tried migrating things to Wrangler v3 and updated my

compatibility_date

compatibility_date

... any ideas?

This is being done to create new Requests with custom cookies attached to pull information from an external website.

M

Murder Chicken•5/21/23, 5:26 PM

Any easy way to inspect the Request object created? Suddenly, this block of code (where

requests

requests

is an array of Request objects)...

const responseData = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))

const responseData = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))

... no longer works resulting in this error...

Cannot read properties of undefined (reading 'map')
TypeError: Cannot read properties of undefined (reading 'forEach')

Cannot read properties of undefined (reading 'map')
TypeError: Cannot read properties of undefined (reading 'forEach')

Which has me baffled... trying to figure out where it's failing.

M

Murder Chicken•5/21/23, 5:28 PM

Yeah, just realized it's incomplete, one sec.

M

Murder Chicken•5/21/23, 5:34 PM

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

M

Murder Chicken•5/21/23, 5:36 PM

I think I got it.

Similar Threads