Unable to access JIO Router behind reverse proxy

[ssrahul96]

@JB701 , May be jio router is explictly blocking reverse proxies as like hassio?

In hassio, we need to add few config to make it work with reverse proxy. Ref : Reverse proxy using NGINX

 

[JB701]

oh i see you are using cloudflare, still shouldn't cause any problems though not sure why it isnt working

 

[vishalrao]

@ssrahul96 are you not able to add an entry in the npm UI itself? Just try different subnet mask like 255.255.255.0 or 255.255.0.0

Or if it's CIDR notation then try /24 or /16 ?

 

[ssrahul96]

@vishalrao , yea, i am adding the entry in npm UI itself, How to add subnet mask in npm UI?

 

[vishalrao]

My bad, I'm not 100% proficient with NPM... I had done a lot of googling to set up my network (but I dont have Jio router) for other things.

Try searching for "nginx proxy manager custom proxy subnet" or something?

@ssrahul96

 

[JB701]

@ssrahul96

Does the jio router connect through https by default on LAN? If so change the proxy_pass to https://192.168.29.1;

and add

proxy_ssl_name "192.168.29.1";

to the config file

 

---

[ssrahul96]

My bad, I'm not 100% proficient with NPM... I had done a lot of googling to set up my network (but I dont have Jio router) for other things.

Try searching for "nginx proxy manager custom proxy subnet" or something?

@ssrahul96

I think, what you are suggesting is for allowing nginx proxy manager to allow certain subnet, But the case here is, jio router is not allowing access from reverse proxy

 

[ssrahul96]

@ssrahul96

Does the jio router connect through https by default on LAN? If so change the proxy_pass to https://192.168.29.1;

and add

proxy_ssl_name "192.168.29.1";

to the config file

no luck either, same issue

 

[ssrahul96]

@ssrahul96

Does the jio router connect through https by default on LAN? If so change the proxy_pass to https://192.168.29.1;

and add

proxy_ssl_name "192.168.29.1";

to the config file

quick update, i was trying with nginx proxy manager which was running as a docker image, it was not working with that,

now i ve installed nginx on the Host VM itself, not it works fine, its wierd though

 

[JB701]

oh it could be because nginx was accessing the page using its interface ip (172.16.x.x). not sure. could just as likely be some bug in npm, have you tried recreating the container after deleting all data? use sqlite database its the easiest.