+ Reply to Thread
Results 1 to 4 of 4

Thread: API external connection

  1. #1
    Join Date
    Aug 2016
    Posts
    2

    Default API external connection

    We have 3 fiery servers in our network. We want make external connection to the fiery servers for API. We open 3 ports in our router/load balancer to the 3 fiery servers. When we open https://192.168.1.3/live/api/v3/version i get: {"AgaliVersion":"3.0.00.26","RubyVersion":"1.9.03.150c","RhythmVersion":"v3.0.03","installed":"2016-03-09T07:45:12+01:00"}

    But when i go to https://IP:PORT/live/api/v3/version i get ERR_CONNECTION_REFUSED

    I think that i must open a port at the fiery server. I tested port 3389, thats work fine.

  2. #2
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    55

    Default

    Hi there,

    Are the 3 Fiery servers you have identical? or mixed models?
    If it's mixed. Please try, https://IP:PORT/live/api/v2/version
    If you get a proper response then the server doesn't have Fiery API v3.0.
    You can get the latest installer from developer.efi.com or you can just use /live/api/v2/version for all of you servers since they are backward compatible.

    I hope this helps!

    Yusuke

  3. #3
    Join Date
    Aug 2016
    Posts
    2

    Default

    Hey Yusuke,

    If i test a local link it's working. Only from external connection i get a connection error

  4. #4
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    55

    Default

    Hi there,

    Sorry looks like I misread your problem!
    I don't think we restrict any ports. The SSL port is default to 443.

    One of our engineers guessed that you are trying to setup an external load balancer that forward the request to one of your 3 servers? This setup could be tricky since each server will have its own cookie session making the cookie from Server A being not compatible with Server B or C. This could be solvable but it's outside of Fiery API scope, unfortunately.

    Thanks,
    Yusuke

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts