Hi Willi, I think, I found the problem. DocumentRoot was correctly set and rewriting or redirecting was not enabled in this part.
But: the option overwritewebroot was set. Commenting it out, all seems okay. I'll check back now if the calendar-error is also gone. Roman Am 16.02.2016 um 13:58 schrieb [email protected]: > Hi, > > what is DocumentRoot of your https://owncloud.servername/ part of apache > config? > > Do you use rewriting or redirecting in the https://owncloud.servername/ > part of apache? > > Willi > > > Am 16.02.2016 um 12:42 schrieb Roman Dilken: >> Hi, >> >> I have an owncloud-installation which uses user_ldap as User-Backend. >> >> If I use the url https://servername/owncloud everything goes fine but if >> I use the url https://owncloud.servername/ the userid provided to the >> plugin is empty so there will never be a successfull login. >> >> I also had to set a symlink from /var/www/owncloud/owncloud to >> /var/www/owncloud so there seems to be a loop within the subdomain-setting. >> >> I've added https://owncloud.servername/ to the trusted domains but this >> doesn't result in giving over the username to the app. >> >> It seems that this behaviour occurs only on the webinterface, remote.php >> seems to login successfull. >> >> Also there is an error with DAV, which don't wants to provide the >> principal-lists of calendars and contacts, contacting every single >> calendar works. >> >> Any hint? >> >> Greetings, >> >> Roman >> _______________________________________________ >> User mailing list >> [email protected] >> http://mailman.owncloud.org/mailman/listinfo/user >> > > _______________________________________________ > User mailing list > [email protected] > http://mailman.owncloud.org/mailman/listinfo/user > _______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
