https://community.cloudflare.com/top?period=daily
I am trying to upload wordpress file which is around 150mb. But I get below error in network resopnse:
413 Request Entity Too Large
413 Request Entity Too Large
cloudflare
My A record is set to DNS only. If I ping my domain - tradewithjazz.com I get my server’s IP. But if I upload the file, I still get above error. Does this mean the traffic is still going through Cloudflare? I don’t want to change nameservers at domain as it might affect emails. What would be the solution?
Your origin server is returning that error. You will need to see if your host is willing to increase the limit or find and alternate means to transfer the file. SFTP access may be one possibility. You will need to consult with your hosting provider.
@epic.network Thank you for your reply.
But I have done all necessary changes on server. Set the limits to 500 mb.
Last time when I was not aware of DNS only config, I had changed the name servers at domain and it worked imeediately so surely not server issue.
If I create same server with same config but with different domain which is pointing direcltly (no Cloudflare), it works.
The error clearly says “Cloudflare” in response.
You are correct. This is because you did not make the DNS updates that were recommended in the the previous topic.
Connecting to your apex name did use your origin IP, as we can see below. (I masked the last two octets in case you enable
curl -Iiv tradewithjazz.com
* Trying 148.66.X.X:80...
* Connected to tradewithjazz.com (148.66.X.X) port 80 (#0)
> HEAD / HTTP/1.1
> Host: tradewithjazz.com
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Date: Thu, 27 Apr 2023 14:59:47 GMT
Date: Thu, 27 Apr 2023 14:59:47 GMT
< Server: Apache
Server: Apache
< X-Redirect-By: WordPress
X-Redirect-By: WordPress
< Location: http://www.tradewithjazz.com/
Location: http://www.tradewithjazz.com/
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
We see that connection told us to come back on your www hostname. Fine. Let’s do that.
curl -Iiv www.tradewithjazz.com
* Trying 2606:4700:3037::6815:5aca:80...
* Connected to www.tradewithjazz.com (2606:4700:3037::6815:5aca) port 80 (#0)
> HEAD / HTTP/1.1
> Host: www.tradewithjazz.com
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Thu, 27 Apr 2023 15:00:12 GMT
Date: Thu, 27 Apr 2023 15:00:12 GMT
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
< Connection: keep-alive
Connection: keep-alive
< Link: <http://www.tradewithjazz.com/wp-json/>; rel="https://api.w.org/"
Link: <http://www.tradewithjazz.com/wp-json/>; rel="https://api.w.org/"
< CF-Cache-Status: DYNAMIC
CF-Cache-Status: DYNAMIC
< Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=beXryWrxlsA3oH2B56psmmu9cxX%2FMQ1jnMyqhhTnb6fATFHsN0r6URwCoMmC6q6hrkP%2FG%2BLtwcOHtEVkvdkeflyMR17Dp0gsoUO0%2FbaImt96tVOziPFZ8k8%2F0fUXi1wlXoAVo3rd2UBtRsbHftBvF9Yp5tg%3D"}],"group":"cf-nel","max_age":604800}
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=beXryWrxlsA3oH2B56psmmu9cxX%2FMQ1jnMyqhhTnb6fATFHsN0r6URwCoMmC6q6hrkP%2FG%2BLtwcOHtEVkvdkeflyMR17Dp0gsoUO0%2FbaImt96tVOziPFZ8k8%2F0fUXi1wlXoAVo3rd2UBtRsbHftBvF9Yp5tg%3D"}],"group":"cf-nel","max_age":604800}
< NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< Server: cloudflare
Server: cloudflare
< CF-RAY: 7be7ef030ecec397-SEA
CF-RAY: 7be7ef030ecec397-SEA
< alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
You have a redirect at your origin from your apex to www, which would be fine if you had not left www set to
Right, but a ping won’t follow a redirect where your browser will.
If you follow the guidance @sandro offered in your prior topic, you should be uploading directly to your origin server.
1 Like
@sandro had suggested to delete AAAA records with name tradewithjazz.com
I have done this. What more you want me to follow from his instructions?
sandro
April 27, 2023, 3:32pm
14
For the record, I suggested to drop all Cloudflare addresses.
But the assessment of @epic.network certainly is - as always - spottest onest
1 Like
@sandro by all you mean all? AAAA, MX , CNAME ?
MX and CNAME records point to hostnames, not IP addresses, so those would not be included in:
Confirm that your www has only an A record and that it has the same IP as your apex name. Make sure that both the apex and the www are set to DNS Only . This should resolve your current situation where you are a redirecting your
1 Like
This might be a dumb question, but do I need to do something where I’ve purchased my domain?
Coz there I have added Cloudflare nameserver so anything there should not affect.
At Cloudflare, I have www A record which points to same IP.
No.
Good. Now switch it from
1 Like
As seen in screenshot attached in last thread, I’ve already set it to DNS only. It was the first thing I did.
I am sorry.
There were www entries under AAAA which I had ingored. Now I have deleted those and was able to upload the file.
Thank you @sandro and @epic.network
1 Like
system
May 13, 2023, 11:11am
26
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
in the future.)
DNS Only. This should resolve your current situation where you are a 