Forget my earlier reply! Now it works with Fritz!Box!
What I did was simply to upgrade to the latest Firmware (my 7360 had a 2 year old version before), and maybe it was also helpful to enable the option "access Fritz!Box-services from outside" (even if I had to choose another port than 443 there). I don't know, but at least one of these measures helped.
So, on to the next "not reverse-proxyable" site, I thought. And (with just compiled nginx version 1.5.6) it now worked from the beginning with the "standard" configuration:
server {
listen 443;
server_name <dyndns-address>;
ssl on;
location / {
proxy_pass http://<local-address>;
proxy_redirect default;
}
}
But when I tried to access the same page from outside my local network the screen again was empty and again I was stuck.
Obviously some code of this webpage depends on the location of the webbrowser. So I tried google to find out which nginx command might be helpful, but honestly I didn't understand quite a bit. Unfortunately the nginx help pages weren't quite helpful, too:
- What exactly can "proxy_set_header" do for me in my case?
- What exactly can "rewrite" do for me in my case?
- What exactly can "sub_filter" do for me in my case?
- Are there other commands to solve the problem?
I'm lost here. I don't know what the webserver might need (it's the configuration page of my "yaVDR" media server) and I have no idea how to probably analyse the communication between nginx and the webserver to check the effects of the various nginx commands.
But for you that problem sounds easy to solve, doesn't it? Any suggestions are welcome...
ako673de
What I did was simply to upgrade to the latest Firmware (my 7360 had a 2 year old version before), and maybe it was also helpful to enable the option "access Fritz!Box-services from outside" (even if I had to choose another port than 443 there). I don't know, but at least one of these measures helped.
So, on to the next "not reverse-proxyable" site, I thought. And (with just compiled nginx version 1.5.6) it now worked from the beginning with the "standard" configuration:
server {
listen 443;
server_name <dyndns-address>;
ssl on;
location / {
proxy_pass http://<local-address>;
proxy_redirect default;
}
}
But when I tried to access the same page from outside my local network the screen again was empty and again I was stuck.
Obviously some code of this webpage depends on the location of the webbrowser. So I tried google to find out which nginx command might be helpful, but honestly I didn't understand quite a bit. Unfortunately the nginx help pages weren't quite helpful, too:
- What exactly can "proxy_set_header" do for me in my case?
- What exactly can "rewrite" do for me in my case?
- What exactly can "sub_filter" do for me in my case?
- Are there other commands to solve the problem?
I'm lost here. I don't know what the webserver might need (it's the configuration page of my "yaVDR" media server) and I have no idea how to probably analyse the communication between nginx and the webserver to check the effects of the various nginx commands.
But for you that problem sounds easy to solve, doesn't it? Any suggestions are welcome...
ako673de