Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Logs are reporting “HTTP request returned status code 403:” When importing with the CLI. #417

Closed
guillaumesoucy94 opened this issue Mar 21, 2022 · 1 comment

Comments

@guillaumesoucy94
Copy link

Hello,

I’m not able to import the half of the links from an .html file generated by Mozilla Firefox, the logs are reporting a lot of “HTTP request returned status code 403:”

This is an example:

https://www.rapidtables.com/calc/electric/electricity-calculator.html: https://www.rapidtables.com/calc/electric/electricity-calculator.html is not reachable. HTTP request returned status code 403:”

When visiting the site by entering the link in Mozilla Firefox, I’m able to visit the website without any issues.

How to bypass this HTTP 403 error? Using tag –skip-meta-generation in my syntax doesn’t change anything.

About the environment, I’m using the latest LinkAce version running on Ubuntu Server 20.04 LTS. Everything is up-to-date on the machine.

Thank-you,

Guillaume

@Kovah
Copy link
Owner

Kovah commented Mar 21, 2022

Hi there.
There is probably not much you can do about that. LinkAce does not use a regular browser to access the websites to generate titles and descriptions, therefore some website block all "non-human" visits. That's why you see a 403 in LinkAce but access the site in your browser without issues.
You can try to add regular User Agents to your configuration, see this documentation. But it's probably more about your server IP address, some sites block all visits from hosting providers.

Repository owner locked and limited conversation to collaborators Mar 21, 2022
@Kovah Kovah converted this issue into discussion #418 Mar 21, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants