Website beyond slow / timing out when proxying enabled
My server has been running fine for a couple months - but today when I tried to commit to my Gitea service - it times out.
This is very strange as it came out of the blue and I don't know what's causing it.
With proxying disabled, the site is fast and snappy as should be.
With proxying enabled, only basic media assets load and takes a literal 15.4-15.6 extra seconds while the index times out
Anything anyone can think of that can solve this? (I've tried restarting server, renewing cert, double-checking my namecheap + cloudflare config)
10 Replies
Are you able to run
mtr 1.1.1.1 on the server? https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites/#perform-a-mtr
Also, where is it hosted (if at home, which ISP)im using XFINITY and heres the mtr output
Also another one,
curl https://reidlab.online/cdn-cgi/trace
mostly interested in the colo and fl lines, if you show the whole thing note that it includes your IP address (which I don't need)Thanks
With proxying disabled, the site is fast and snappy as should be.Does it work for other users as well when you do that? If you're on the same local network as the server, it will route traffic internally over LAN and ignore any rules on firewalls and etc. while it may fail from outside that network. It feels in this case like some kind of firewall (either at the server, router, or ISP level) is blocking or throttling incoming connections to those ports. I tried curl to the origin IP behind that site both from a Cloudflare server and from my local machine but neither of them succeed to connect. Since you're on the same network that firewall or whatever is blocking/throttling wouldn't apply and may cause you to believe it's working when it isn't. This kind of problem is unfortunately common for consumer ISPs, in those scenarios I would personally recommend using Cloudflare Tunnel with an outbound connection which has a much easier time: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/ https://erisa.dev/exposing-a-web-service-with-cloudflare-tunnel/
oh weird, you are correct, i wonder why it just stopped accepting outside connections
ill ask my dad for the router password and see if i can configure some firewall settings there
No problem, hope you get it sorted in the end
damn, seems to be an issue with xfinity as we have our firewall disabled :(
ill just keep proxying off for the time being
My understanding was that even with proxy off it still only works within your network
And my recommendation for hosting at home would be setting up Cloudflare Tunnel
yeah i thought it didn't, but you're right
i'll go ahead and mark this as solved because we know the root issue, thanks for the help!
i had to turn off "Generate firewall rules automatically (UPnP)" and "Generate firewall rules automatically (Port Forwarding)" and then turn it back on again 😅😅 at least i fixed it