Connectivity problem due to firewall, cant expose localhost

[TonyStark]

Hello
However tunnel works fine in my wifi network, but in office there is limited connectivity and only certain site and port can be accessible.
Is that possible to run tunnel in limited or firewalled network?

2022-09-16T10:54:34Z WRN If this log occurs persistently, and cloudflared is unable to connect to Cloudflare Network with `quic` protocol, then most likely your machine/network is getting its egress UDP to port 7844 (or others) blocked or dropped. Make sure to allow egress connectivity as per https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/configuration/ports-and-ips/
If you are using private routing to this Tunnel, then UDP (and Private DNS Resolution) will not work unless your cloudflared can connect with Cloudflare Network with `quic`. connIndex=0 ip=198.41.200.63
2022-09-16T10:54:39Z ERR Failed to create new quic connection error="failed to dial to edge with quic: timeout: no recent network activity" connIndex=0 ip=198.41.200.63
2022-09-16T10:54:39Z INF Retrying connection in up to 1m4s seconds connIndex=0 ip=198.41.200.63

Above log is generated while im trying to run tunnel
I also see that ngrok http tunnel works fine in my office limited internet and it can expose localhost to internet world
But somehow cloudflared doesnt seem to work.
I also tried with http2 h2mux protocol but not workind either.
So anyway to bypass firewall and expose localhost to internet using cloudflared??

Thank you

[schack]

Did you try HTTP2 instead of QUIC ?

[TonyStark]

yes
http2 and h2mux using --protocol
but not worked

[TonyStark]

using --protocol http2
OUTPUT:

2022-09-17T08:30:27Z ERR Unable to establish connection with Cloudflare edge error="DialContext error: dial tcp 198.41.200.73:7844: i/o timeout" connIndex=0 ip=198.41.200.73
2022-09-17T08:30:27Z ERR Serve tunnel error error="DialContext error: dial tcp 198.41.200.73:7844: i/o timeout" connIndex=0 ip=198.41.200.73
2022-09-17T08:30:27Z INF Retrying connection in up to 32s seconds connIndex=0 ip=198.41.200.73

OS: WINDOWS10

[schack]

You should show your company security guy this page: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/do-more-with-tunnels/ports-and-ips/
If company security policies allows, perhaps he will open up the required ports

[TonyStark]

Ok
is that possible to connect cloudflare server with 443 port instead 7844?
DialContext error: dial tcp 198.41.200.73:7844: i/o timeout
if 7844 replace with 443 then i am sure i can able to make connection :)

[abelinkinbio]

You'll need to ensure that the machine where cloudflared is running is allowed to egress via TCP (and UDP if you're connecting over QUIC instead of HTTP/2) to port 7844 to talk out to Cloudflare. This is a requirement to connect cloudflared to the edge.

[TonyStark]

My machine can egress via tcp only but only allowed limited port and host.
if cloudflared edge server can be accessible by 443 port then im sure i can successfully run cloudflared tunnel.

[gvccvwangmingn2]

My machine can egress via tcp only but only allowed limited port and host. if cloudflared edge server can be accessible by 443 port then im sure i can successfully run cloudflared tunnel.

since day 0 it's always been port 7844. if you and/or your IT team is not able to open port 7844, then I think this product is not for you.

port 7844 TCP is ok, you can still connect through http2 method.

[TonyStark]

Oh, I hope that cloudflare team will add 443 port in future to connect edge server.
Thank you :)