-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Returns 500 Error in Docker Environment but Works Locally #17
Comments
Quick update: I built the Docker image locally and it works fine. The issue was with the |
Yup I see the same thing.
Fixes the issue. Edit See my comments below, all of this was caused by my own errors, the dockerhub version is working just fine for me again. |
Note The dockerhub image did work yesterday, but stopped working after an automatic reboot this morning. Not sure if there is some bug related to the reboot. |
That part seems weird because that image never worked properly on my end to begin with. Did you have the chance to see if that behavior happens with the manually built image? |
it looks like your container does not start after reboot. |
Edit See next comment, I really have no idea happened. No it restarts, it returned HTTP Code 500.
|
Ugh, I don't know what I did now. Everything seems to be working again for me. Here are the things that I can verify:
I went back to try and recreate the error with the dockerhub version and did the following:
I honestly don't know what to think, if the container isn't running, I get a fetch timeout not a response of Possibly I did something else different, or maybe it will break again after some time. I dunno, sorry for the confusion. |
Funny enough, there are some websites that cf-clearance-scraper just shits itself and returns a Request Timeout. Specially if the website happens to NOT be protected by cloudflare (like https://httpbin.org). @krkeegan Could you try and fetch "https://httpbin.org/headers" using cf-clearance-scraper and check if you get this same problem? Note: I'm using a HTTP/HTTPS proxy for all my requests |
OK, I figured out how I was dumb. I am pretty sure when my machine rebooted it restarted an older version of cf-clearance. That is why it was still running and returning a 500 error. So, nothing to see here, just my own mistakes.
Yup, agree that returns |
Thanks a bunch. I might try to debug it another day |
The library has been updated. It should now run smoothly. I am closing this issue, please let me know if you have any problems by writing a message through this issue. Thank you. |
Description:
I've encountered an issue where the API returns
{"code":500,"message":"Request Timeout"}
when running within a Docker container. However, the API functions correctly when run directly on my local machine using Node.js.Steps to Reproduce:
http://localhost:3000/cf-clearance-scraper
).Expected Behavior:
The API should return a successful response as it does when running locally.
Actual Behavior:
The API returns a 500 error with the message:
{"code":500,"message":"Request Timeout"}
.Additional Information:
Questions:
Any insights or suggestions would be greatly appreciated!
The text was updated successfully, but these errors were encountered: