You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use two instances of Kresus and issue appears at the second installation.
I used admin panel to install Kresus.
I changed the original "libellé" and url which is by default "kresus".
I used "picsou" instead of the default.
The issue appears in the nginx configuration file : /etc/nginx/conf.d/MY_DOMAIN/kresus__2.conf where directives @xxxxx stays with @kresus instead of the name of the url I asked.
I do not know if this a bug or not and sorry for the noise if not.
Context
Hardware: old sff computer at home
YunoHost version: 11.0.10.2
I have access to my server: Through SSH and through the webadmin and direct access via keyboard / screen
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
Steps to reproduce
Throught the webadmin panel, just install an new instance of kresus and change libellé and url.
I guess the root cause is url and not libellé of course
Expected behavior
Nginx configuration for the new instance with right value for nginx "@xxxxx" directives.
Logs
No logs but if you tell me where to find logs I can give them to you
Many thanks
regards
The text was updated successfully, but these errors were encountered:
Hi,
I use two instances of Kresus and issue appears at the second installation.
I used admin panel to install Kresus.
I changed the original "libellé" and url which is by default "kresus".
I used "picsou" instead of the default.
The issue appears in the nginx configuration file :
/etc/nginx/conf.d/MY_DOMAIN/kresus__2.conf
where directives@xxxxx
stays with@kresus
instead of the name of the url I asked.I made the replacement by myself and it worked :
I do not know if this a bug or not and sorry for the noise if not.
Context
Steps to reproduce
Throught the webadmin panel, just install an new instance of kresus and change libellé and url.
I guess the root cause is url and not libellé of course
Expected behavior
Nginx configuration for the new instance with right value for nginx "@xxxxx" directives.
Logs
No logs but if you tell me where to find logs I can give them to you
Many thanks
regards
The text was updated successfully, but these errors were encountered: