Cant Add SRT Stream File - New Amazon EC2(Windows) 4.8.5 build

[Michael_Beaumont1]

Hi

I’m in the process of trying to build a new Wowza server using the Amazon Marketplace AMI version 4.8.5 (built many previous ones with version 4.8 in past)

However with a completely clean install…if i add a stream file to the live application with the following details:
srt://0.0.0.0:7001 (for example)

Whenever i try to start it, i get the error
Unknown action: connect

Looking at the log files, this is what is reported

REST API: Unknown action: connect Class: com.wowza.wms.rest.vhosts.applications.streamfiles.StreamFileAppConfig: java.lang.reflect.InvocationTargetException|at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)|at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)|at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)|at java.base/java.lang.reflect.Method.invoke(Unknown Source)|at com.wowza.wms.rest.ActionBase.get(ActionBase.java:177)|at com.wowza.wms.rest.ActionBase.put(ActionBase.java:125)|at com.wowza.wms.rest.vhosts.applications.streamfiles.StreamFileAppAction.put(StreamFileAppAction.java:73)|at org.restlet.resource.ServerResource.doHandle(ServerResource.java:434)|at org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:666)|at org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:348)|at org.restlet.resource.ServerResource.handle(ServerResource.java:1020)|at org.restlet.resource.Finder.handle(Finder.java:236)|at org.restlet.routing.Filter.doHandle(Filter.java:150)|at org.restlet.routing.Filter.handle(Filter.java:197)|

Any ideas?
This worked fine in previous server builds?

Thanks

Mike

[Rose_Power-Wowza_Com]

Hi @Michael_Beaumont1 I know this can be frustrating to have happen when you upgrade, but for any ugrade issues or log reviews, tech support requrires a support ticket. It’s because they need full access in order to test. They also don’t want to guess in the forums since this has major impact on your entire streaming architecture.

I can tell you that I have seen that error occur before for people who did not have a compatible operating system, another time it was resolved by upgrading to CentOS 8 because there is a required component in that version for SRT to work.

These are just guesses though and we’d need to accurately diagnose in a ticket. We want you to have everything working correctly.