action #25532

Combine z-push and owncloud vHosts

Added by flacco almost 5 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


A lot of possible recipients of an owncloud share-link are behind of a proxy server. The most proxy servers block the access to ports different from the standard http(s) ports 80 and 443.


#1 Updated by flacco almost 5 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

I added the ownCloud apache configuration to the z-push vHost. In cases we have this vHost activated (with kopano Groupware for example), we ship ownCloud over this vHost.

It's not tested yet.

#2 Updated by kfreitag almost 5 years ago

Can you briefly explain what the problem with ownCloud is here? The share links are also going via the standard ports, no? What do I overlook? Thanks :-)

#3 Updated by ingogoeppert almost 5 years ago

It is not a "ownCloud" problem, it is a problem with our default apache configuration. We run the different applications (our portal, z-push, webapp, owncloud...) on different ports. It is "historisch gewachsen" ;-) We will change this to use the default ports (80, 443) in future.

#4 Updated by flacco over 4 years ago

  • % Done changed from 50 to 80

invis servers apache vhost setup is renewed, now we have to test it.

#5 Updated by flacco over 4 years ago

  • % Done changed from 80 to 90

First invis-servers with the new vHost setup are in productive use. Everything looks good.

#6 Updated by ingogoeppert over 4 years ago

  • Project changed from invis-server to invisAD-setup
  • Category deleted (Developement)
  • Target version deleted (13.1)

#7 Updated by flacco over 4 years ago

  • Target version set to 13.1

#8 Updated by flacco over 4 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

I close this ticket. For the future we have to have a closer look at our apache setup.

Also available in: Atom PDF