Thanks @wbk for your response, but it doesn’t help me
The “make default” button is made to redirect the root server url. It’s not what I want, I have another url to access to my yunohost panel, and I keep this one
Morover, as nextcloud is installed on this url, I can’t use it for a default url.
For your group’s proposition : Yes, it is a solution, if my users are registered in yunohost, but it’s not the case. Some users are directly created in nextcloud (yes you can do that, without create an account in yunohost ) and those users haven’t a yunohost account. So I can’t create any group for them.
If I created users in yunohost, they could login by the yunohost portal, and my problem would be inexistant… But those users haven’t to be created in yunohost, only directly in nextcloud. Their ID and password aren’t managed by yunohost, but only nexctloud. I’m sorry if I repeat too many times the same things, it’s just to be sure that english doesn’t limit the problem understanding !
On its own subdomain.
Yes, it’s something like that !
Unfortunately not, because you can’t have more than one default domain on a yunohost server…
Bonsoir @metyun, Non je n’avais pas vu cette réponse !
C’est parfaitement ce que je cherchais !!! Merci !
Alors, pour expliquer ce que je fais, si d’autres ont le même problème :
cd /var/www/nextcloud/core/Controller
nano LoginController.php
j’ai bien
public function logout() {
$loginToken = $this->request->getCookie('nc_token');
if (!is_null($loginToken)) {
$this->config->deleteUserValue($this->userSession->getUser()->getUID(), 'login_token', $loginToken);
}
$this->userSession->logout();
$redirectUrl = $this->config->getSystemValue('logout_url',
$this->urlGenerator->linkToRouteAbsolute(
'core.login.showLoginForm',
['clear' => true] // this param the the code in login.js may be removed when the "Clear-Site-Data" is working in the browsers)
));
$response = new RedirectResponse($redirectUrl);
$this->session->set('clearingExecutionContexts', '1');
$this->session->close();
if (!$this->request->isUserAgent([Request::USER_AGENT_CHROME, Request::USER_AGENT_ANDROID_MOBILE_CHROME])) {
$response->addHeader('Clear-Site-Data', '"cache", "storage"');
}
return $response;
}
Et l’équipe de Yunohost est absolument géniale, parce qu’elle a laissé accessible le code original, dans un second fichier, stocké au même endroit, nommé LoginController.php.orig
Rien de plus simple donc, il suffit de renommer les deux fichiers :
mv LoginController.php LoginController.php.ynhmod
mv LoginController.php.orig LoginController.php
Et le tour est joué !
La question que je me pose, c’est : Est-ce qu’à la prochaine mise à jour je devrai refaire ce changement ? Je le saurai… à la prochaine mise à jour !
To explain in english :
Yunohost has done a patch to redirect NC to his own login portal. But, because they are totally awesome, they have put in same place the original file. If you want to redirect your NC to the NC login page, you have just to do this three commands :
cd /var/www/nextcloud/core/Controller
mv LoginController.php LoginController.php.ynhmod
mv LoginController.php.orig LoginController.php
there is still a question about Nextcloud update : will I have to redo the manipulation for each update?
The next update will bring the response…
Thanks !