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.

Sign up for GitHub

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

Jump to bottom

Using TwitRSSme Docker behind a proxy #71

Open
Tux-Panik opened this issue Feb 24, 2019 · 1 comment
Open

Using TwitRSSme Docker behind a proxy #71

Tux-Panik opened this issue Feb 24, 2019 · 1 comment

Comments

@Tux-Panik
Copy link

Tux-Panik commented Feb 24, 2019 •
edited

Hi,
Thank you for this great tool.

Unfortunately, due to Twitter rate-limit, I must raise my own instance.
As calls come from a Docker service, I decided to pull, build and run the Docker version on the same server.

My infrastructure owns a proxy, which has been set using the export http_proxy (https_proxy too).
When I try to get a feed, I reach the following error:
<html><head></head><body><h2>ERR: Can&#8217;t screenscrape Twitter</h2><p>Redirecting you back to <a href="http://twitrss.me">TwitRSS.me</a> in a few seconds. You might have spelled the username wrong or something</p></body></html>

I guess it's a proxy error.
So, how should I declare properly a proxy configuration to retrieved feeds?

Thanks in advance for your suggestions,
Kind regards,
Julien
@Tux-Panik Tux-Panik changed the title Using TwitRSSme docker behind a proy Using TwitRSSme Docker behind a proxy Feb 24, 2019
@Tux-Panik
Copy link
Author

Hi,
I'm still facing this issue, so if you have any idea do not hesitate to provide some tips.
I just tried this workaround as the scripts use "LWP::UserAgent"

I set in a Terminal:
export http_proxy="http://my.proxy:3128"
export PERL_LWP_ENV_PROXY=1

But, unfortunately, it doesn't help.
Kind regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Tux-Panik