If you registered it recently it might not be propagated fully yet. How long ago did you register it
If you registered it recently it might not be propagated fully yet. How long ago did you register it?
IThat's not something that we discuss on here; the whole point of Cloudflare is to prevent DDoS.
IIf you own the zone you can try to disable by adding a Page Rule with a level of Essentially Off (or just Off if you are Enterprise) but we can't condone bypassing if you don't own it, especially for DDoSing.
JYeh, lets not 
ISo even if you somehow bypassed Cloudflare (don't do that) it won't help; that's an issue with the actual origin server itself.
ISame reason; if you ever see that type of error page it means Cloudflare is working and it's a problem with the origin server.
IAs for Github, I have no idea why you are getting that error (maybe it's a problem with GitHub where you are)?
M...
IPlease don't ping random people on here.
MPinging the workers team is really not going to help
IThat's fine, just please don't ping people to do that.
IIf it's a true vulnerability you'll need to submit it through https://www.cloudflare.com/disclosure/
Cloudflare
This policy provides our guidelines for reporting vulnerabilities to Cloudflare.
IIf UAM is truly on and you are bypassing it (i.e. not completing the captcha and somehow visiting the origin server directly without getting it's IP), then yes that would be classified as a vulnerability.
S1 minute before sending lol
BWhich channel should I ask a question about CloudFlare Web Analytics?
JHere is good 
BLCP question in Web Analytics
Bhmm, seems odd I can't make a thread. ok
BI am trying to understand long LCP times in the Web Analytics data we receive for our site. We have SVG images which are stored in a GCP bucket with 5kms LCP times. This seems pretty long for a service with a regular latency of ~150ms. The SVGs are small, ~13k, is it perhaps the render time which is in this number? One area confusing me is that the object section show the size to be 439k, I am not sure where this number is coming from. I have a screen shot, though didn't want it to take up much of the main #general-discussions thread space
Vbut the argo tunnel does not work properly
IWhat exactly isn't working?
Vthe tunnel connects and it works on quick dns --- but on multiple host i am getting no connection
ICan you send any logs?
Vroot@ip-172-31-53-236:/home/ubuntu# cloudflared tunnel --config ~/root/.cloudflared/config.yaml run vboxtest
2022-02-08T23:09:11Z INF Starting tunnel tunnelID=
2022-02-08T23:09:11Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.Cloudflare-warp ~/Cloudflare-warp /etc/cloudflar
ed /usr/local/etc/cloudflared]
2022-02-08T23:09:11Z INF Version 2022.1.3
2022-02-08T23:09:11Z INF GOOS: linux, GOVersion: go1.17.5, GoArch: amd64
2022-02-08T23:09:11Z INF Settings: map[config:/root/root/.cloudflared/config.yaml]
2022-02-08T23:09:11Z INF Generated Connector ID: 4f21bb2f-dec2-4d46-8a7a-55dc86b85c0c
2022-02-08T23:09:11Z INF Initial protocol http2
2022-02-08T23:09:11Z INF cloudflared will not automatically update if installed by a package manager.
2022-02-08T23:09:11Z INF Starting metrics server on 127.0.0.1:37883/metrics
2022-02-08T23:09:11Z WRN Your version 2022.1.3 is outdated. We recommend upgrading it to 2022.2.0
2022-02-08T23:09:11Z INF Connection e6fdc6fc-7692-4e78-b1af-68b1916ab8e6 registered connIndex=0 location=IAD
2022-02-08T23:09:12Z INF Connection 07a37ec1-a4f4-474c-8f4a-226463bc44ca registered connIndex=1 location=IAD
2022-02-08T23:09:12Z INF Connection 7ce80b7f-793d-4bb8-bb2b-e45fe40126c6 registered connIndex=2 location=IAD
2022-02-08T23:09:14Z INF Connection 77efaf42-6a2c-43a5-9f0a-7dca137096dc registered connIndex=3 location=IAD
2022-02-08T23:09:11Z INF Starting tunnel tunnelID=
2022-02-08T23:09:11Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.Cloudflare-warp ~/Cloudflare-warp /etc/cloudflar
ed /usr/local/etc/cloudflared]
2022-02-08T23:09:11Z INF Version 2022.1.3
2022-02-08T23:09:11Z INF GOOS: linux, GOVersion: go1.17.5, GoArch: amd64
2022-02-08T23:09:11Z INF Settings: map[config:/root/root/.cloudflared/config.yaml]
2022-02-08T23:09:11Z INF Generated Connector ID: 4f21bb2f-dec2-4d46-8a7a-55dc86b85c0c
2022-02-08T23:09:11Z INF Initial protocol http2
2022-02-08T23:09:11Z INF cloudflared will not automatically update if installed by a package manager.
2022-02-08T23:09:11Z INF Starting metrics server on 127.0.0.1:37883/metrics
2022-02-08T23:09:11Z WRN Your version 2022.1.3 is outdated. We recommend upgrading it to 2022.2.0
2022-02-08T23:09:11Z INF Connection e6fdc6fc-7692-4e78-b1af-68b1916ab8e6 registered connIndex=0 location=IAD
2022-02-08T23:09:12Z INF Connection 07a37ec1-a4f4-474c-8f4a-226463bc44ca registered connIndex=1 location=IAD
2022-02-08T23:09:12Z INF Connection 7ce80b7f-793d-4bb8-bb2b-e45fe40126c6 registered connIndex=2 location=IAD
2022-02-08T23:09:14Z INF Connection 77efaf42-6a2c-43a5-9f0a-7dca137096dc registered connIndex=3 location=IAD
Vi remove the tunnel id
IOk, so the problem is your config file. See on line 3 where it says there's no config file found?
V2022-02-08T23:18:36Z ERR error=“Unable to reach the origin service. The service may
be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:8
080: connect: connection refused” cfRay=6da893fc4ae00329-MIA originService=http://loc
alhost:8080
be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:8
080: connect: connection refused” cfRay=6da893fc4ae00329-MIA originService=http://loc
alhost:8080
Vwhere should i put the config file
Vand how should i call it
IOk. So first, those first logs say that there's no config file. You can follow the guide here: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide
ISecond is that your service that you are trying to expose,
127.0.0.1:8080 is not responding. You'll want to check why that is.Vthis is my config ...tunnel: TUNNEL ID
credentials-file: /root/.cloudflared/vboxtest.json
ingress:
credentials-file: /root/.cloudflared/vboxtest.json
ingress:
- hostname: vtest1.vboxsystems.com
service: http://localhost:80 - hostname: vtest2.vboxsystems.com
service: http://localhost:81 - service: http_status:404
IOk, where is it located?
Vand its saved /root/.cloudflared/config.yaml
IOk, so then your problem is with the run command. See the
~ character that is at the front of the --config flag? You'll want to get rid of it so that it becomes /root/.cloudflared/config.yaml.Vthis is the command loudflared tunnel --config ~/root/.cloudflared/config.yaml run vboxtest
IYeah, so it should be changed to
cloudflared tunnel --config /root/.cloudflared/config.yaml run vboxtestI(Notice how I removed the
~)Vwithout the ~ it cant find the path
IOk, then make sure your config file is actually in that path. The
~ is adding your user's home directory to the path which you don't want.IIf you're still unsure see what
cat /root/.cloudflared/config.yaml says.Vthe file is there i double check and tripple check can cat and vi it without ~
IOk... which user are you running cloudflared with?
Vsudo
IOk, can you give the exact logs of what it says when it can't find the path?
Vwhere would i find that
ISo when you run
cloudflared tunnel --config /root/.cloudflared/config.yaml run vboxtest without the ~ what does it say?