Alfresco Edit/Preview behind firewall
Alfresco November 4th, 2008After puting our servers behind a new Cisco firewall, we ran into a problem with the Alfresco Virtualization Server where you could either edit and not preview, or preview and not edit. Editing was only an issue where the Web Form content type was pulling in files on the AVM drive. In this case it was an included XSD.
The reason for this is that the preview goes out to ip.alfrescodemo.net to resolve the URL, which externally accesses the virtual server on port 8180. When you click edit, the IP in virtual-server.properties is used to access the AVM drive externally. With a strong security model, that’s obviously not going to happen. So, when I changed the virtual server IP to the local 192.168 base, editing worked, but previewing didn’t. With the public IP, it was the opposite.
Even allowing access to all ports for specific IP’s wasn’t working - still not sure on why that is. Adding the public IP to the Advanced TCP/IP settings of the box
It’s not clear yet whether this causes conflicts with other setups, but it did the trick for us! Editing and previewing works like a charm.
This is the solution for KTBU-21.

February 26th, 2010 at 10:40 am
Thanks for this info - I had similar problems on Linux behind a Rackspace firewall. A similar workaround was to create an alias script for ifcfg-eth0.
sudo cp /ifcfg-eth /ifcfg-eth:0
(on a RHEL machine this looked like
sudo cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0:0
)
then changed the IPADDR to the public IP
and changed DEVICE to eth0:0
March 1st, 2010 at 2:30 pm
Nice, thanks for the Unix workaround.