-
Notifications
You must be signed in to change notification settings - Fork 2
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
Not registering any node #37
Comments
This appears to be running correctly, but please note that it expects to be run with an Apache reverse proxy in front of it, otherwise the mDNS announcements do not match up with the port it runs on. The Apache configuration required is held in https://github.com/bbc/nmos-registration/blob/master/debian/ips-api-registration.conf and https://github.com/bbc/nmos-reverse-proxy/blob/master/etc/apache2/sites-available/ips-reverseproxy-common.conf |
I got it to work by modifying line:87 to "current_priority = 100" Thank you and sorry for the late reply. |
Glad it's working. It should be possible to resolve this without having to adjust the code. By default the Registration API runs with a priority of '100' which is outside of the recommended range and is intended to prevent it disturbing a running system. If you want to put it into 'production' mode then this should be set between 0 and 99. You can do this using the configuration file as noted here: https://github.com/bbc/nmos-registration#configuration |
I am not sure why it didn't work without adjusting the code. |
I am not sure if registration is working properly or not as no nmos node seem to register the services and I get this output:
Also on running the nmos-mdns-bridge output:
The text was updated successfully, but these errors were encountered: