Search results

  1. M

    CDN - failed to connect to origin server

    @Max Similar to playHLS api aithentication from backend server, how can I authenticate CDN streaming (HLS) at viewer side using my backend authorization?
  2. M

    CDN - Multiple origins and edge servers clarification

    Update: CORS issue got fixed by following the link in above thread. Max, but it doesn't reflect immediately after restarting the server. Is there any cache configuration with flashphoner properties file? Also, can you share any good tuning and performance recommendations for CDN streaming...
  3. M

    CDN - Multiple origins and edge servers clarification

    Okay Max. Thanks for the response. I have configured the Origin (2 servers behind a load balancer) and Edge servers (2 servers behind a load balancer). I can abe to publish the stream to origin servers. But when I tried to view through the stream using HLS from edge servers I am recieving CORS...
  4. M

    CDN - Multiple origins and edge servers clarification

    Hi, I have a question on how multiple origin servers will work for streaming and playing with edge servers through CDN. Based on this link https://docs.flashphoner.com/display/WCS52EN/CDN+2.0, it seems multiple origins and edge servers are supported. But my question is what will be the...
  5. M

    CDN - failed to connect to origin server

    I am seeing some other errors like
  6. M

    CDN - failed to connect to origin server

    I figured out the issue. I have enabled acl_auth and it seems when Edge URL tries to authenticate from my backend server, it is breaking something. Is there any guidelines to follow acl_auth for edge servers? But still I am seeing errors in the server_logs/flashphoner.log file. This error in...
  7. M

    400 BadRequest with RestAPI

    Okay. Thank you Max.
  8. M

    CDN - failed to connect to origin server

    Yes. I am playing the correct urls with port (8082). But I am getting this error. Please see the log file
  9. M

    CDN - failed to connect to origin server

    Thanks Max for the quick response. Just to confirm, is the above Edge and Origin server configuration is correct? I am getting following error when I checked with the server logs And to get HLS URL, we can use the Edge domain url with port 8082. right?
  10. M

    Manager log is not generated in logs folder

    Thank you Max. Let me check with CDN.
  11. M

    CDN - failed to connect to origin server

    Hi, I am trying to do live stream using CDN. I have two load balancers (AWS), one for origin and another for edge. I followed the steps with dynamic CDN and I am getting "Failed to connect error" in edge server. Edge: cdn_enabled=true cdn_ip={ip_local} cdn_point_of_entry=origin.demo.com...
  12. M

    400 BadRequest with RestAPI

    okay. If I have multiple servers attached to the load balancer, how can I get all the streams published in different servers?
  13. M

    400 BadRequest with RestAPI

    Yes. Its working There is only one instance attached to this Load balancer. So requests should be routed to that server only.
  14. M

    400 BadRequest with RestAPI

    Hello Max, I am connecting this rest api through AWS Load balancer endpoint (HTTPS) which connects to port 8081 in WCS. Is there any issue with this configuration?
  15. M

    Manager log is not generated in logs folder

    Oh okay. Thanks Max. I have another question.Is there any proper documentation how Flashphoner handles the servers that is attached to AWS load balancer? I mean I want to know, if there are instances scaled up or down in Load balancer will the following conditions work 1) Lets consider there...
  16. M

    Manager log is not generated in logs folder

    As per this link https://docs.flashphoner.com/display/WCS5EN/Starting+and+stopping, I have restarted the web call server. But I can able to see only one process runnning and there is no flashphoner-manager.log file in logs folder. Can anyone tell me why it is not generated?
  17. M

    playHLS custom backend server enpoint not working

    okay. Thanks Max. Let me check.
  18. M

    400 BadRequest with RestAPI

    Hi, I am trying to access the REST API (https://docs.flashphoner.com/display/WCS5EN/API+overview) in http port 8081 and I am always getting 400 Bad Request as a response. Do I need to configure anything additionally?
  19. M

    playHLS custom backend server enpoint not working

    Thank you. I returned 403 with publishStream REST hook but still it get published. Do I have to do anything further?
  20. M

    playHLS custom backend server enpoint not working

    Thank for the quick response. It worked. And can we follow the same pattern if a stream is started from publisher side? I mean we can restrict the publishStream similar to playHLS. right?
Top