-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
Changing Port not working #27
Comments
Do you follow this issue? #15 Camera will still use an old port (80) and trying to do request via it, if you didn't see these requests in logs then something wrong with a proxy. Use configs in provided above issue |
Yeah right have the nginx on port 80 which redirects to 8080. I also did all the steps by vale-max in the issue... What is the POST /app/api/ApiServer/getA9ConfCheck?devicesCode=0800c01A079A&random=DEFGHI&token=c42bf98af0 |
I mention exactly about this request. This is an initial camera configuration request. Camera tries to retrieve server parameters. If you see it, then proxy able to forward request to the server, but the question is camera receive an answer? You can use wireshark to check this. This is definitely proxy misconfiguration. |
after getting it to run once, i've only been having trouble with this. I am as far as @DJTechMo , getting still in
Can't seem to find the issue for this problem. |
Hi there,
first, thank you for your work.
I already got things working and am tweaking the setup now.
As the port 80 is used by multiple services on the server, i had to install a proxy and forward the request to another port.
I chose 8080 as it is free at the moment.
I have a DNS Server to redirect the naxcom adresses to that machine.
And opening http://v720.naxclow.com/dev/list gives the empty device list from another windows pc, so this seems to work.
Unfortunately the camera does not appear in the device list.
With port 80 everything worked/works.
Below is the log, so there appears the call from the camera.
Why is it not registered as device?
Did i miss something?
The text was updated successfully, but these errors were encountered: