The reason is there’s several cameras, and the URLs involved are the same. NethServer can’t separate them correctly.
On the old SME-Server I used the old Proxy-Path Module, which enabled forwarding paths (like NethServer) or whole domains.
How could this be done correctly (CMD-Line)? I tried a few things, but that shut down apache… ;-(
Hi @Andy_Wismer,
can you explain a little bit more exactly what you want to do?
The cameras are at one network, but where schould they be redirected? Has every camera it’s own webserver or is there one webserver who shows every camera?
Couldn’t you do it with an .htaccess file?
Hi
The cameras are all in the LAN or another trusted Network, routed and accessible from the NethServer, but not from the outside.
There IS a camera server available (Axis), but I need the individual image from each camera available extern, as cam01.domain.com, cam02.domain.com and so on.
Upon access with IP or domainname, the cameras will jump to something like http://192.168.175.52/view/viewer_index.shtml?id=117357
For this to work, I’d also have to additionally map next to /cam01/ also map a path /view/ which is why it will only work for one camera using /path/.
NethServer has a template system, I do understand how this works, but how do I get this to work?
The NethServer Docs are quite complete using /paths/, but not domains…
The DNS entries are all correct, internally and externally - this WAS working using SME Server…
I even extracted the SME template files and tried to adapt them for NethServer, that blew Apache and had to revert…
Hi
Each camera has it’s own internal IP / FQDN (Only internally accessible).
Each Camera is individual and mounted in a different spot, usually with a corresponding name, eg
SHZG-CAM-Garage -> That one monitors the entrance to the underground parking…
It’s IP is 192.168.176.51
SHZG-CAM-Extern -> This one monitors the main entrance, especially for Night Security.
It’s IP is 192.168.175.51
As you can see, they can be in different Subnets, all Subnets are routed and trusted in NethServer.
The actual routing is done by a hardware firewall…
I could make it work with nginx but had to use port 444 instead of https default port 443.
I created an nginx module for onlyoffice but it’s usable here too, it eases installation as it doesn’t use a port by default so there’s no conflict with apache:
Hi @Andy_Wismer, we’re working on a Reverse proxy UI for an entire virtual host based on Apache. The package is in testing and will be released soon. Please have a look at this thread: