When creating websites : issue with defaut page langage ... always english template ...

I've choosen FR (and client is french), but when i create a web site ... default web page of the site is in english ..

Forum : is very slow to diuplsay message part ... (reply, create etc)

 

Did you set both FR as a language and France as a country for the client?

 

yep , langage AND country

 

so in tools \ password & langage ? that's it ? (of the client )

Because my admin is in english

 

done with ansible.

 

hum ...

i do :

- name: Modele site web ISPCONFIG EN 1/2 (Serveur Debian/Centos)
copy:
src: "{{ '/etc/ansible/roles/masterisation/files/ispconfig_standard_index.html_en' }}"
dest: /usr/local/ispconfig/server/conf/index/standard_index.html_en
owner: root
group: root
mode: '0750'

- name: Modele site web ISPCONFIG EN 2/2 (Serveur Debian/Centos)
copy:
src: "{{ '/etc/ansible/roles/masterisation/files/ispconfig_user_standard_index.html_en' }}"
dest: /usr/local/ispconfig/server/conf/index/user_standard_index.html_en
owner: root
group: root
mode: '0750'

- name: Modele site web ISPCONFIG FR 1/2 (Serveur Debian/Centos)
copy:
src: "{{ '/etc/ansible/roles/masterisation/files/ispconfig_standard_index.html_fr' }}"
dest: /usr/local/ispconfig/server/conf/index/standard_index.html_fr
owner: root
group: root
mode: '0750'

- name: Modele site web ISPCONFIG FR 2/2 (Serveur Debian/Centos)
copy:
src: "{{ '/etc/ansible/roles/masterisation/files/ispconfig_user_standard_index.html_fr' }}"
dest: /usr/local/ispconfig/server/conf/index/user_standard_index.html_fr
​

always default web site page ... in english !!
Need i restart php-fpm ? (i already do nginx)

 

+ $conf['language'] = 'fr';
in : /usr/local/ispconfig/interface/lib/config.inc.php

Is there something i 've missing ?

Notice that :
/usr/local/ispconfig/interface/lib/config.inc.php
/usr/local/ispconfig/server/lib/config.inc.php


Edit :Which one to take ?
update this value on panel server or on other web server ?

Final edit : It's WORKS
Must take /usr/local/ispconfig/interface/lib/config.inc.php
BUT ... on the server where ipsconfig panel is installed !!!
(with ansible, i deploy template file -fr- and -en- then favicon on every server !!)

 

something strange : when create new website for a client, ispconfig create a new unix user each time ?

 

so,what is it the aim to having language choice in webgui if we must ... set them in config.inc .php ? (permanently)

 

ok i see , i discover everything here , newbie in ispconfig ;-)!
Why ispconfig do not delete user when ; the client delete his websites ? (they are no usefull after that ...)
EDIT : hummmm, ouchh, arghhhh : i discover that because, with ansible i manage user (unix) allowed to connect to web servers too.
Then disable user (/...../nologin) when not in a playbook list , then all user with id > 1000 are concerned, playbook disable users if they are not in this list !!!!

I use that :

List of groups user will be added to. When set to an empty string '', the user is removed from all groups except the primary group.
Before Ansible 2.3, the only input format allowed was a comma separated string.
Mutually exclusive with​

==> so using groups: '' , then remove users of all groups (including sudo), Did ispconfig put user or ispconfig user to some groups ?

SO according to you i shouldn't do that, am i breaking ispconfig user management ?
thank Till.

 

users aren't deleted when the user deletes their websites because they may recreate those websites, or they may have email accounts, or dns still with you, and maybe host the site elsewhere.

i'm not sure exactly what your saying about the unix users and ansible, but whatever's happening, it'll be because you've told ansible to run some command that will change user details/settings. if you're using ansible to install all the required software and settings, then that is all it should do. doing anything like

is not part of the perfect server tutorial, so you're using ansible to do something that is not required. you shouldn't need to do anything with any user accounts via ansible, either the apt install <package> will create the required system/user accounts and settings, or the ispconfig control panel install and usage will.

 

i understand, clearly.
I must NOt do anything on ISPconfig server (multi server setup).
i m' used to manage on each server : ntp client, resolv.conf, sshd file , allowed users , sudo users, crontab, ufw firewall, motd, ... according to you i must stop that ?

 

ok. it's allow me testing ispconfig in real situtation.
i will resinstall, and upgrade my ispconfig installation "how to" doc !
i hope to share with you this howto.

 

you can still use ansible to make changes, but you do need to be more circumspect about what you change.

as you've noticed, ispconfig will create user accounts itself, it will create ssh logins etc. it will recreate website vhost configs, it will, on updates/upgrades or on admin initiated changes to settings in the panel, rebuild various configuration file changes for apache/nginx, postfix etc, so any changes you make that affect any of those settings/files outside of ispconfig will be lost. similarly any changes to user account settings, apache/nginx/postfix/fail2ban/ufw etc outside of ispconfig can break the correct functioning of your ispconfig setup.

if you want to make changes to certain area's you need to make sure those changes are in ispconfig's conf-custom folder or subfolders, so that ispconfig can retain those changes after updates/reconfigurations. similarly you need to test and ensure that any changes you want to make outside of ispconfig don't break the correct functioning of ispconfig, which blocking the login of any user's with a uid greater than 1000 certainly will.

yes, client user accounts are added to the www-data group, if a client creates an ssh login for a site, the web## user account is added to the sshusers group

 

i understand ;-) that's why i will reinstall ispconfig and ... then remove some of our ansible playbooks ;-)