413 - Request Entity Too Large
-
@Arago44 No one is addressing this issue? It's never happened to me before. I switched to another browser (Brave), and I thought I would try clearing all cache data to see if it worked. It did for a few uploads and then it failed again. Photo sizes were reduced to less than 200K. Same thing.
-
@sabahiya try uploading something that is half the size.
I am just speculating... but it could be that you are using a 32 bit computer that goes goofy when you try to deal with a file larger than 4 gb -
@lololulu19 I have been using a Mac all these days and it never had a problem like this in the past..
-
It happen to me as well ...
Tried several times 1...2... and it works !!! ...
This is related to bandwidth / server issues or the system is currently busy ... [As well as your PC is doing multiple task] ...Regardless of pixel as long as the file size do not exceed 500 kb and you have a good bandwidth the system will accpet the process ...
The description below relating to picture pixel [width/height/dimension] Quality ... [not file size] ...
[œùæ] : " Mahirap mag dunong dunongan, Kung wala kang kaalam alam " ...
-
What does “413 Request Entity Too Large” mean?
A 413 HTTP error code occurs when the size of a client's request exceeds the server's file size limit. This typically happens when a client attempts to upload a large file to a web server, and the server responds with a 413 error to alert the client.413 - Request Entity Too Large
https://blog.hubspot.com/website/413-request-entity-too-large#:~:text=What does “413 Request Entity,error to alert the client. -
@john32123666 Thank you for pointing this out,
I have sent a message over to our SysAdmin to try and sort this out. It appears the system is not resizing the files which is causing the "Too large" error message.
DandyLion
-
@DandyLion said in 413 - Request Entity Too Large:
@john32123666 Thank you for pointing this out,
I have sent a message over to our SysAdmin to try and sort this out. It appears the system is not resizing the files which is causing the "Too large" error message.
DandyLion
Thanks I thought I was the only one having this issue lol. Please let me know when it's resolved
-
does this happen to the gaytor.rent site or the .ru site?
i just made some changes to the configuration.. hope this is fixed now.. sorry for the delay
@looselips said in 413 - Request Entity Too Large:
@DandyLion said in 413 - Request Entity Too Large:
@john32123666 Thank you for pointing this out,
I have sent a message over to our SysAdmin to try and sort this out. It appears the system is not resizing the files which is causing the "Too large" error message.
DandyLion
Thanks I thought I was the only one having this issue lol. Please let me know when it's resolved
-
@Joker said in 413 - Request Entity Too Large:
does this happen to the gaytor.rent site or the .ru site?
It happens most on .ru site ... cause the rent revert to .ru each time we switch back to the main page ...
however we will let you know if we run into issues ... and thank you, for addressing this ...
-
J john32123666 referenced this topic on
-
J john32123666 referenced this topic on
-
J john32123666 referenced this topic on
-
@john32123666 is this bug still existing?
-
yes some say from QTM but I guest .ru and rent so far is working ...
-
@sabahiya
Same thing for me since a few hours. I systematically get a 500 Internal Server Error.
Not alone when uploading images but also the .torrent file, and even when clicking the do it button, at the bottom of the upload page.
Issue exists with Safari as well as Chrome; on gaytor.rent as well as on gaytor.rent.
️ -
J john32123666 referenced this topic on
-
@Douseikekkon I thought that changing from gaytor.rent to gaytor.rent was only a name change, and had no affect on any servers - but it looks like there is some sort of change.
I just checked.. and gaytor.rent has an ip address of xxx.21.19.219
whereas gaytor.rent has an ip address of xxx.26.8.160That is just begging for problems. They should be the same, or one of them deleted. Both are nearly exactly the same speed.
-
this should be fixed by now
-
@Joker The problem might be fixed at the source.. but the changes to ip addresses and DNS names might take a while to propagate throughout the internet worldwide.
I changed the name of a server I was running.. and it took over 6 months for it to fully propagate. In fact, sometimes things do not change unless the end user manually refreshes their browser to get the updated addresses, and cookies.
-
Try uploading pictures now
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login