Hi Chris,
Thanks for the suggestion - we tried it, and found something odd...
Perhaps we misconfigured it, I don't know.
We changed the public access name from publicproxyhost.tld/teamowncloud
to publicproxyhost.tld/owncloud and it worked.
So then wanting to, if possible, conserve the /teamowncloud, we thought
we'd simply move from privatehost/owncloud to privatehost/teamowncloud...
And that did not work. Even from the intranet we didn't have permissions
to upload/create files. I'm not sure if this is a bug or a
misconfiguration somewhere.
Has anyone ever tried to host owncloud on an alias other than /owncloud?
Thanks,
Jon
Software Engineer
DPCG
GAIA project
University of Geneva
On 09/21/2016 05:43 PM, Chris wrote:
Hi,
maybe start with a clean proxy setup without any modifications of requests
like "Header edit Location" or similar?
The documentation about reverse proxies and ownCloud here might also contain
some additional info:
https://doc.owncloud.org/server/9.1/admin_manual/configuration_server/reverse_proxy_configuration.html
--
View this message in context:
http://owncloud.10557.n7.nabble.com/web-interface-permission-error-when-going-through-proxy-tp17692p17693.html
Sent from the Users mailing list archive at Nabble.com.
_______________________________________________
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user
_______________________________________________
User mailing list
User@owncloud.org
http://mailman.owncloud.org/mailman/listinfo/user
