I am asked to help an owner of an old Battlefield Bad Company 2 server who's a victim on ongoing and

I am asked to help an owner of an old Battlefield Bad Company 2 server who's a victim on ongoing and recurring DDoS attacks. I recommend him using Cloudflare, but I am not sure how this could be setup. Could anybody point me in the right direction?

soos•2/17/24, 5:04 PM

general-helpWebsocket HLS stream can't be received

would streaming like this be against cloudflare TOS? its just LHLS tunnel for a security camera that wouldn't be on 24/7

Ssimplenotezy I am asked to help an owner of an old Battlefield Bad Company 2 server who's a v...

Jaren•2/17/24, 5:06 PM

cloudflare is probably not going to be your solution to this. you can do this with spectrum on the enterprise plan, but it would be a lot of money

Original message was deleted

soos•2/17/24, 5:07 PM

what could I use as an alternative so that I don't have to port open

Original message was deleted

soos•2/17/24, 5:35 PM

Thank you so much that worked

Andy•2/17/24, 10:10 PM

redirect rules are free forever right?

Andy•2/17/24, 10:10 PM

no matter how many requests get it?

Walshy•2/17/24, 10:10 PM

yep

Erisa•2/18/24, 12:22 AM

Not to my knowledge but you could totally build one on Workers

EErisa cloudflared in docker won't run on the same network as your localhost, 127.0.0.1...

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:35 AM

it's not working now

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:35 AM

it keeps giving me 502

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:35 AM

i tried reinstalling cloudflared but that didn't work

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:35 AM

i didn't change anything

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:36 AM

 ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 172.17.0.5:80

 ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 172.17.0.5:80

Erisa•2/18/24, 12:36 AM

The error is self explanatory, double check that the service is listening on that IP and port

Erisa•2/18/24, 12:36 AM

Not much i can suggest other than since I have no access to your environment, it's a local configuration issue

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:36 AM

docker can change IPs over time?

Erisa•2/18/24, 12:37 AM

If you recreate the container then sure

Erisa•2/18/24, 12:37 AM

but maybe there is an issue with the container or its stopped or many other reasons, so have a check to make sure its running properly and listening on the right IP

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:38 AM

oh shoot, i think it has to do with the way i started the containers?

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:39 AM

like if i start x container first, it always goes to 172.17.0.1?

E1337 NOTORඞOUS The PRESTඞGඞOUS•2/18/24, 12:39 AM

but if i started after y container, it goes to 172.17.0.2?

Erisa•2/18/24, 12:40 AM

I think there is an option to specify the IP as well

Erisa•2/18/24, 12:40 AM

I usually use