I'm uploading several thousand files through the Box API, and after a few hundred uploads I'm getting a 502 Server Connection Closed error (and the response is HTML, not JSON as I would expect). Average file size is 0.5M
The errors seem to be mostly affecting the larger files, but this could just be because it is more likely for the larger files to be mid-upload when the upload fails.
I'm also retrying files on 502 failures, and I sometimes get a general 500 error response, or sometimes a local ETIMEDOUT or a socket hang up error (I'm uploading using the Node request library).
Any thought as to what is the problem here? Is it that Box is somehow having trouble with the amount of stuff I'm uploading from my local computer? (I would doubt that though.)
It seems like this the problem was just overloading Box with requests. I was doing uploads in parallel, and after lowering the parallelism the 502 errors stopped coming up. If I kept parallelism high, when I retried requests that errored out enough times, the requests eventually went through.
Related
I uploaded my Laravel project to infinityfree.net, but get this error:
This page isn’t working right now sitename.epizy.com can't currently handle this request.
HTTP ERROR 500
How to fix this?
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.
Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the 500 Internal Server Error is reporting a general error on the web site's servers and not your computer, the server error may only be temporary. Trying the page again will often be successful.
Come back later. The 500 Internal Server Error message is one of the most common error message seen when checking out during an online purchase so sales are often disrupted. This is usually a great incentive to resolve the issue very quickly.
3.Try Clearing your cache and browser history. It could be possible that the page you are seeing is a cached version, so after the cache is cleared it will go away.
You can check the error log button in cPanel under the logs section to see what errors are being given if you have cPanel hosting with us. Sometimes 500 errors can be due to syntax errors in a .htaccess file or other things you may be able to quickly fix yourself.
You need to "error mood" on in php config file(you can search it in cpanel).error mood off to error mood on to see error log.after you checked the error and solved it change error mood setting.(error mood on to error mood off).I hope this will help you a little.
To give some background, I'm an (unpaid) intern, and I'm unrelated to dealing with this kind of stuff. My employers wanted to update some pictures, and they did locally but didn't know how to upload the new version to the server.
I used the publish settings that were saved in Visual Studio from when the previous intern deployed the server (he was specialized in web site stuff) and it worked on deploy ... then I refreshed the page and I'm getting 502 server error.
Steps I have taken:
Connect to the VM and restart it - didn't solve it. it's using Microsoft server 2016.
Open the VM trough RDP, check if there are errors. There were 3 services not running, and I start them manually. One still isn't running, Downloaded Maps Manager. Ok... I google it and it's not a necessary service so I disable it. Now there are no errors and all services are running but I still am getting this error.
I tried pinging the IP of the server, and the URL itself and it works.
I believe it might be something to do with the load balancer, but I had one HTML class and nothing dealing with actually publishing stuff. If you could point me in the right direction I would appreciate it. The only reason why I'm trying to fix this myself is that I didn't make some kind of backup, and I feel so stupid having taken the site down.
Edit: I've gone to "load balancing" and it says service unhealthy. I tried going to the IPs there and it brings me to the same 502 server error page. From what I've gathered this is a configuration error, it's impossible they messed something with the site itself, right? It did work that first time, and if I run it from Visual Studio it works on the local machine ...
I'm currently creating a web application through linux OS (debian), using php7, codeIgniter 3, Nginx and Mysql.
Few months ago, all my PHP errors used to be reported in the default nginx log error (located at : /var/log/nginx/)
But recently, I have configured CodeIgniter in purpose to report those errors inside the folder of my application.
It seemed to work, because I noticed that my current errors were repported in this new log file.
However, "some" errors don't seem to be reported. For example, I have a form in my web application, running aswell with Javascript (ajax use). Once I send the form, I can notice in my browser's console an Error 500 (internal server error). However, this error is not reported in my error log file ! (and I already checked in the former log file belonging to Nginx, there's nothing too)
What am I supposed to do ?
Thanks you.
At my job, we use the debugging tool Charles Proxy a lot. So I always have it running in the background. Sometimes it's recording, other times it's not.
However, lately it has started acting up. For every web request I do, there is a 1-3% chance that it will fail to connect with the reason: "Connect: Connection timed out: connect"
Test case
I did a test with Charles: Use the 'repeat advanced' option on a file to fetch it 50 times:
As you can see, 2 of them failed. (And it took it 21 seconds to timeout). The 98 other times, it took ~4ms to complete the request.
I did the same test with Charles closed and Fiddler opened instead.
After 400 requests of the file, not a single one had failed.
Happens on normal usage
Here, it happened when I opened the company game site. A rather important request failed and thus, the site never fully loaded.
I have tried
I tried restarting my computer.
I tried updating to the newest version of Charles.
I tried uninstalling and installing Charles.
I tried disconnecting from the VPN we're on.
I tried closing down Charles and that seems to fix it. But I need to have Charles running and I don't want to open and close it all the time.
I tried using Firefox instead of Chrome and it seemed to happen very rarely or almost never. However Firefox is really bad to use when working with Flash.
Edit (Chrome net-internals)
I logged the output from chrome://net-internals/#events when trying to load a file that failed.
Pastebin dumps: http://pastebin.com/dgMaLMKc then http://pastebin.com/dAGpJCJy
It would seem this was caused by the program Ad Muncher. After closing it down, the timed out connections has apparently stopped.
I'm facing a problem with a 3-tier application. It uses IIS and SQL Server. And the problem is that sometimes (longer requests cause higher probability) client does not receive response from IIS. It hangs when there is no activity ON SQL Server, and when even when I kill an SQL Process I get no response with an exception. When I examine data after these hangs I find that my SQL requests have succeeded, so the problem appears to be on IIS. Unfotunately I don't have much control over the place where the application is hosted and I cannot reproduce the problem. There can be many answers to this question, but at least I need a hint in what direction I should investigate.
UPDATE: I also have an app running on the same server that does a small job: it inserts around a 100 lines line-by-line into a database. Artificially I made it run for about 10 minutes (by putting xlock on the table). After removing the xlock the process on IIS continued running and successfully inserted those 100 lines. However, control never returned to the client thereafter, it just waited indefinitely. It looks like this is a problem when returning a response to the client after a long running process.
BTW, this is not a website, but a WinForms app that uses Remoting.
If you're sure that SQL Server is returning to IIS, then you might want to check the IIS logs to see what might be happening to the request. The normal location for these logs is %SystemRoot%\system32\Logfiles\<service_name>.
If you're not sure about SQL Server, you might access the SQL logs, run Profiler, or check the Windows system logs for errors, run your site in debug in Visual Studio or add your own logging to your app to figure out which step it's hanging on.
I have finally figured out where the problem is. The application is run on a web farm and there is a balancer server between the client and IIS. There was a too small timeout on the balancer. For some reason it is not quite friendly with .net remoting and it doesn't return any timeout exceptions to the client. The issue has been solved by increasing the timeout.