Open chronotank79 opened 1 month ago
My tests run fine, so please provide the erroneous URLs.
Just tested again, still gives same error. I've tried a bunch of different ones and none of them worked, but here's one as an example: https://www.kink.com/shoot/37781
It works for me. Attach the log file with the error, please.
Thank you, @chronotank79. Nothing special is happening on your side, but I have to figure out why you're getting a 'bad page.' I'll try it through a VPN; maybe I can reproduce the error.
Thanks for looking into it!
And FWIW, the page in question loads normally in a browser for me.
I could reproduce the error with some US IP addresses: "You are seeing this page because your state has passed a law requiring you to provide proof of your age in order to browse adult content. Please follow the simple and secure steps below to gain access to our amazing content."
@chronotank79 which country are you from?
I do live in a US state with a law like that, however I connect using a VPN and the page loads normally for me in a web browser. My IP address should appear as if I'm in Canada. Why would I get this error in the scraper and not in a web browser? (Also, why did it work normally when I first installed it, and then randomly stop working? Should I try reinstalling AMM?)
AMM uses the VPN from your system, which is how I was able to reproduce the issue. Maybe you could try another country or different software. There are some free alternatives; for example, Proton VPN could be great for testing.
I've tried switching the VPN to Canada, Germany, and Japan, and I get the same "Unsupported page" error for all of them, ONLY when trying to scrape Kink addresses. Other sites that also require age verification based on region don't cause this problem when I am using a VPN. And the Kink page itself is still loading normally when I open it in a web browser while connected thru VPN.
I'm going to try reinstalling AMM and see if it changes anything.
Updated to 1.0.1, same issue.
The Kink scraper is broken, and now returns error "Unsupported Page." It was working fine until recently. (Using release version 1.0.0)
If I go to the page manually in a browser it loads fine, so the issue must be with the scraper.