Skip to main content
A
Anonymous
September 15, 2014
Answered

Can not connect from other computer

  • September 15, 2014
  • 1 reply
  • 612 views

I can not access the media on the server. I am running CentOS 7 with the latest Media Starter Server. What I am able to do is access the admin console, and stream on the adobe local host page and even place a player code to a video file into a Weebly web page and it play on the server computer. But once I try to do that from another computer, in or out of the network, it does not connect. The odd thing is that the admin console will show an attempted connection when I do that. Port tester shows all ports are success. I am not sure what to check at this point. Can anyone give me some ideas?

This topic has been closed for replies.
Correct answer hparmar

I did have them open the ports listed and they also forwared them to the server's ip address. I think the default for 1111 on ams is block. I can access the admin from the server but not from outside the network. I have not tried on another computer within the network. I thought that 1935 should show open and that is why I called Charter and they told me the open and forwarded status. From what I read the rtmp tries to run on 1935 then falls back to 80. If you would like to see certain files I can copy them tomorrow if you tell me which ones you need to see. I am not sure what is meant by Custom tcp/udp rule listed above. Unfortunately I don't have direct access to the modem/router configuration, something I am not really happy about.


No rtmp always runs on 1935 and there is no fall back on 80...However you can configure rtmp to run on any port other than 1935, which however is not recommended. If 80 is the only port then instead of rtmp you can try using rtmpt(i.e rtmp tunneled over http) which runs on 80, since underlying http runs on 80.

I am pretty confident that the issue is your network setup and ports/IPs  being blocked.IMHO, It has nothing to do with AMS setup.

1 reply

H
Adobe Employee
hparmar
Adobe Employee
September 16, 2014

Please add appropriate crossdomain.xml to webroot folder.

A sample crossdomain.xml looks like as below:

<?xml version="1.0"?>

<!-- http://www.adobe.com/crossdomain.xml -->

<cross-domain-policy>

  <allow-access-from domain="*" />

</cross-domain-policy>


Please modify it suitably as per your security guidelines.

A
Anonymous
September 16, 2014

I thought that this might have helped but it did not. The file was not in existence. I reinstalled Adobe media server and the Apache folder showed up this time. but there was no webroot folder under Apache2.2. The hppd.conf file only showed ::webroot. There is a webroot folder in the directory that also contains Apache2.2. Just to make sure I took the crossdomain file from the download zip file, make it a least restrictive as possible, and placed it in the existing webroot folder and also added a webroot folder under Apache2.2 with a copy in it. I restarted and rebooted a couple of times.

This appears to have made no difference as it acting the same as it was doing before.

H
Adobe Employee
hparmar
Adobe Employee
September 16, 2014

Yes i was referring to the webroot directory inside AMS installation folder i.e /opt/adobe/ams/webroot.

Did you try with turn off the firewall on your centos e.g service iptables stop and service ip6tables stop.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices