:8000/upload:1 POST http://localhost:8000/upload 500 (Internal Server Error)
createError.js:17 Uncaught (in promise) Error: Request failed with status code 500
at createError (createError.js:17)
at settle (settle.js:19)
at XMLHttpRequest.handleLoad (xhr.js:78)
While I'm uploading a file I'm getting this error, can anyone help for it.
This error was because you did not handle the situation in the client when the server returns an HTTP error 500
Actually, you have to check the server application, why it does not accept the upoplad, and only returns an error.
Related
I tried many times but can't solve this error I checked server side there are all okay but got this error
I tried to upload a jsonl file for sequence labelling task and have the following in the console:
POST https://website.azurewebsites.net/v1/projects/16/upload 500 (Internal Server Error)
Error: Request failed with status code 500
at t.exports
at t.exports
at XMLHttpRequest._.onreadystatechange
What can I do ?
a few days ago i moved my frontend with NextJS to Vercel and i started experiencing this following intermittent error during build and production server. So i searched all over the internet but i cannot find the solution.
I am receiving the following error when my App tries to make HTTPS request:
Compiled successfully.
09:47:13.026 Automatically optimizing pages...
09:47:15.212 Error at BlogService.getRecentPosts, details: Error: request to https://**masked** failed, reason: write EPROTO 140256911292224:error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1550:SSL alert number 80
09:47:16.629 Error at getStaticProps on Homepage, details: Error: write EPROTO 140657767638848:error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1550:SSL alert number 80
09:47:16.654 Error at BlogService.getRecentPosts, details: Error: request to https:/**masked** failed, reason: write EPROTO 139955108906816:error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1550:SSL alert number 80
The backend destination is using a Nginx with Reverse Proxy with LetsEncrypt Certificate
So anybody can help me? I never experienced this issue
UPDATE
I changed my backend to AWS Api Gateway but the issue remains.
I already changed my frontend to just make Https requests using TLS 1.2, and the error remains intermittent
Anybody help me?
I found our Node services intercommunication (using request) will occationally report this error:
Error: Parse Error
at socketOnEnd (_http_server.js:455:20)
at Socket.emit (events.js:203:15)
at Socket.EventEmitter.emit (domain.js:448:20)
at endReadableNT (_stream_readable.js:1129:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
After some digging in _http_server.js, it turns out to be the http parser finish error. It means that util the socket close, the http parser cant correctly parse the http request.
Our service log shows that its the client timeout and close the socket and then the server report this error. So I doubt that it's this request issue cause the problem, but I have no further evidence.
Another question is why the Node server receiving a bad http request not aborting the parse phase and response with an error immediately but hanging there until the client timeout and close the socket?
Is anyone reaching the same problem?
p.s.
Using Node version: 10.16.0
After logging the socket data, I found the malformed http request. It's missing the body:
POST /internals/topics/list HTTP/1.1\r\ncontent-type: application/json\r\nx-client-host: production/user-service-5d76d998d8-wr9ws\r\nHost: topic-service.prod:3000\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\ncontent-length: 117\r\nnewrelic:xxx\r\nConnection: close\r\n\r\n
So this really is a request package problem and it's not maintained anymore, I am going to use got package instead.
Hope it helpful for others who reach the same problem.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster#gitlab.dev.sample.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.0-fips DAV/2 Phusion_Passenger/4.0.42 mod_bwlimited/1.4 mod_fcgid/2.3.9 Server at gitlab.dev.sample.com Port 80