Please note that this feature is available only for advanced users, as it can be quite challenging to run your own server. We are unable to provide any form of support at this time for unmanaged servers.
You can use the Virtual Studio web application to create references to JackTrip and Jamulus servers that you manage yourself. The web interface will not actively control any aspect of the server's configuration or operation. You may want to use this, for example, if you live in a geographical location that is not yet covered by our managed servers. Unmanaged servers will appear in the list of "Audio Servers." Although all features will not be available, the Virtual Studio web application can be used to make it easy to manage subscriptions and connect Virtual Studio audio devices to them.
To create an unmanaged server, follow the same process except disable the "Managed Server" toggle at the top of the form. This will add additional prompts for you to input the "Server Host" and "Server Port." Please note that all settings you specify here (Port, Rate, Period, etc.) must match what you have configured on your server.
Unmanaged servers will always be displayed with the state of "Running." You can tell that a server is unmanaged when it has the text "Unmanaged" in place of a START or STOP button.
Comments
2 comments
Unfortunately your servers are too far away from Europe. We ran an unmanaged server by installing jack and jacktrip 1.2.1 from "Jacktrip remote server or raspberry pi notes" doc (Ubuntu 20.04 Amazon EC2 Instance). We have no luck to connect to server: jacktrip -S -p2 (trying to connect and stopped) and 100% packet lost in app panel. Maybe you have a more detailed guide for server deployment and troubleshooting?
Hi Nikolai. As it says above, the foundation itself can't provide support for unmanaged servers here, but there is information in different places online. One of the best places to get help is the jacktrip users google group:
https://groups.google.com/g/jacktrip-users
Just quickly I wonder if you need to set up the proper port forwarding on the server, since that's a common problem (and I believe EC2 instances might have a default firewall so you'd have to open the right ports). I suggest posting more specific details and error messages to the users list and also searching its archives. Good luck,
Michael
Please sign in to leave a comment.