Erreur HTTP sur les fichiers volumineux

french

#1

Bonsoir,

J’ai une erreur http lors de l’envoie d’un gros fichier, si je désactive le service et que je remet les dns d’origine tout est ok.
Y a t’il un réglage pour ça dans la version free ? ou est-ce que la version free est bridée ?

Merci d’avance


Files can not be downloaded
#2

Hopefully Google Translate will be sufficient here :slight_smile:

I have an http error when sending a big file

What do you mean by “sending” a big file? Cloudflare doesn’t handle email traffic.


#3

Considering it’s an HTTP error, it’s gotta be an HTTP upload or download. If only they posted the exact error message.


#4

#5

hi guys, sorry my english isn’t very good, so i said the problem was sending big file like 150 mb (uploads), and i see limit in free plan so i delete all soundcloud dns reset for default dns of my isp and all is ok now.
thanks for your answers :o)

Merci :o)


#6

Bonjour @djkikudj,

La limite d’upload fixée en mode Free n’est pas modifiable, si vous souhaitez pouvoir uploader des fichiers plus volumineux, vous devez upgrader votre zone pour un plan supérieur.

La liste des limites est disponible à : https://www.cloudflare.com/plans/#compare-features

Free: 100MB
Pro: 100MB
Business: 200MB
Enterprise: +500MB (sur devis)

A bientôt sur les internets !


#7

Bonjour Stéphane,

Merci c’est ce que j’ai vu en regardant un peu partout sur le site Cloudflare, et du coup j’ai tout enlevé car ça me bloque. Dommage, bonne continuation


#8

Bonne continuation !


#9

Bonjour

Moi j’ai une erreur 520, sur des fichiers ( images, css, … ) faisant plus de 50ko. Est-ce normal ?
en dessous de 50ko aucun souci.

il ne s’agit pas d’upload, mais d’afficher des images par exemple.
exemple : https://marketplace.nextclic.com/media/wysiwyg/home/home-eco.jpg

Merci d’avance


#10

Can you look at your server logs? A 520 is a general error caused by a bad response by your web server.


#11

i don’t have any error in error.log, i have a line in the access.log

127.0.0.1 - - [05/Nov/2017:23:49:11 +0000] “GET /media/wysiwyg/home/home-eco.jpg HTTP/1.1” 200 82839 “https://marketplace.nextclic.com/media/wysiwyg/home/home-eco.jpg
This is Nginx that serves the static files


#12

A 200 should work. Does everything work if you :grey: DNS for marketplace?

It’s a mystery since so many other files work with no problem. It’s also not consistent for me. I would get a lot of 520 and 521 errors for .js files, but later they would all work. Right now, only styles-m.css and home-eco.jpg aren’t loading. Those are the two that never work for me (in Firefox). In Chrome, only home-eco.jpg isn’t loading.


#13

One thing that doesn’t make sense to me is home-eco.jpg is tagged as being type ‘html’. I don’t know if it’s because the response error is in HTML from Cloudflare, or somehow your server is telling Cloudflare it’s HTML when it’s really JPG.


#14

i have to say that if i reduce the weight of the image with photoshop , under 50ko , … it will work


#15

it looks like that it comes from my nginx configuration…
nginx nok : http://marketplace.nextclic.com/image.jpg
apache ok : http://marketplace.nextclic.com:82/image.jpg


#16

ok was due to a bad configuration of varnish…