1.2 so I guess I'm stuck.
Eventually it will be a DNS name so I wonder if I can trick matterhorn into making it work. The outside world would see matterhorn.wiu.edu on the public address and the matterhorn server would see it point to itself. I may be able to test that theory tomorrow. Is there a tentative release timeframe for 1.3? Thanks, Matt ----- Original Message ----- From: "Hank Magnuski" <[email protected]> To: "Matterhorn Users" <[email protected]> Sent: Tuesday, January 10, 2012 3:59:54 PM Subject: Re: [Matterhorn-users] Matterhorn Behind a Load Balancer What release of Matterhorn are you running. If 1.3 you are facing a multi-tenant configuration issue which Tobias fixed in the latest 1.3.x On Tue, Jan 10, 2012 at 1:50 PM, Matt Mencel < [email protected] > wrote: I have an F5 load balancer. It is listening on https://10.10.221.168 and forwarding those requests on to my matterhorn server which is running at http://10.15.129.168:8080 . The problem I think is with the public address I've defined in the config.properties file. I've set it to the public address out on the load balancer... org.opencastproject.server.url= https://10.10.221.168 But when I connect I'm getting errors in the opencast log like this... 2012-01-10 15 :47:48 WARN (OrganizationFilter:96) - No organization is mapped to handle http://10.15.129.168:8080/login.html Which I think means that matterhorn doesn't like that the public address defined in config.properties does not match the IP configured on the matterhorn server. Am I right? If so is there a fix or workaround for this? Thanks, Matt _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
