New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
More than happy to try help (free with the forum spirit) if you post your specific issue or questions
Will be happy to help if needed
it is easy to become an expert yourself, just read this page
https://www.nginx.com/resources/admin-guide/reverse-proxy/
Caching reverse proxy?
Taken from my codebase, the location block should have everything you need, replace $proxyHost with the address/upstream(s) and you should be fine.
It works fine for me, PM if you need a full .ZIP that has everything that you can simply include in your config
So here is my problem.
Im trying to do a reverse proxy to a website called extratorrent.cc, just for me and some of my friends in the uk, which have it blocked by their ISP.
The main problem is that, with my nginx config, after a while proxing, extratorrent gives a redirect to one of his own proxies, with a strange meta refresh thing, which i saw by debugging with firefox, will post it in some minutes.
So, Im looking for a solution to this, to dont redirect to one of their proxies. I see many proxies of extratorrent online havent that redirect, so i wonder how do they managed to avoid that redirection? The redirect happens when the proxy starts to get some traffic.
Here is my nginx conf: http://pastebin.com/xTG88MSF
Here is my domain.conf: http://pastebin.com/wvDQ023s
Nginx is the version 1.10.0, compiled with https://github.com/yaoweibin/ngx_http_substitutions_filter_module and https://github.com/openresty/headers-more-nginx-module.git
Any help is appreciated.
Will post in a moment the exact redirect string.
The string : http://pastebin.com/eVBMxynL
I remember can do this in the past... It wont redirect but has kind of overlay text notice blablabla.. ET has its own protection against reverse proxy and set limit per connections.
The important part is that I need it to not redirect, do you have any advice?
if you know thats a meta refresh, so based inside the proxied content and no header itself, you may want to look into this http://nginx.org/en/docs/http/ngx_http_sub_module.html to filter for the url given in that meta refresh or the meta refresh itself to replace and therefore disable it.
edit: just seen you are already using subs_filter within your domain.conf - what is keeping you from replacing that meta refresh with this type?
Don't have time for this of thing now, but just from seeing have you try to "edit" the /scripts/script.js
or look at other .js files, usually redirect came from javascript load with localhost or IP
edit: just seen you are already using subs_filter within your domain.conf - what is keeping you from replacing that meta refresh with this type?
hello falzo, I already tried to remove completely that meta, but somehow it keeps refreshing infinitely, might have found a solution which im testing, will let know you guys soon...
Nop, my results didnt gave the hoped results, still looking for some guru!
Of course, if you give a working solution, I might be paying something.
thanks!
Thought about it and probably they are just rewriting every request to that refresh/redirect thing after they detected you as using a proxy.
So there probably is nothing you can do from your side if you reach that point. You may have to guess what makes them able to detect that your nginx is just a proxy.
Could be easier to use that vps just as an vpn...
They are rewriting requests from domains not "listed" as their own I presume.
BUT, there are some others who did managed to make it working, and I wonder how they could do that. For that reason is like a challenge for me, to learn or find someone who can teach me those meccanisms...
Still no Solution for me, still looking for some "gurus" who can teach me
could be a lot, like cookie related (there are some nginx rules to deal with cookiedomains and such) or they have something in their code which tries to connect/load some url, pix or else and if that fails, because it doesn't go through your proxy at all, they know it's not a direct connection and so on.
you probably have to analyze the sourcecode of the pages and js indeed (maybe it's doing some ajax calls or such things) looking for urls which you would than have add to your rewriting filters to have them send to your proxy.
as said its probably a lot easier to just setup a vpn instead to use that ;-)