Skip to content
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

Getting 502 Bad Gateway Errors #241

Open
syberphunk opened this issue Sep 27, 2024 · 2 comments
Open

Getting 502 Bad Gateway Errors #241

syberphunk opened this issue Sep 27, 2024 · 2 comments

Comments

@syberphunk
Copy link

I have IP address overrides specified in my /etc/hosts for a domain.

If I directly wpull an URL from one of the addresses, it resolves fine, I get the file I expect using the override IP address.

If I use grab-site, and it finds one of these domains, I get a 502 gateway error, setting --debug doesn't tell me any further information, just that now for some reason I'm pulling a html page instead of say, a png image I'm expecting.

I've set dns wait times, --no-http-keep-alive, and --no-skip-getaddrinfo but I really can't nail down what's causing this problem when wpull is called via grab-site to access this domain.

The venv doesn't have its own proxy or dns settings.

I'm really at a loss for narrowing down what grab-site is doing or how to debug it or ensure it's connecting to the domain properly to not cause this problem.

We have access to the server-side, and it's not even really hitting the site properly to grab the image. I'm bypassing any cdn we have.

It's weird.

@TheTechRobo
Copy link
Contributor

Are you using --no-skip-getaddrinfo or --wpull-args=--no-skip-getaddrinfo ? The former won't work.

@syberphunk
Copy link
Author

Are you using --no-skip-getaddrinfo or --wpull-args=--no-skip-getaddrinfo ? The former won't work.

The latter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants