There really was something there
{"redirected_urls": {"exmple.com/": "exmple.com/lstu"}}
But even after deleting the file it didn’t help and also tried to restart nginx
not helping. The exact same problem
- Is your domain registered in Yunohost?
- Does
'yunohost tools regen-conf nginx --dry-run'returns anything ?
English please 
Yes
And yes
Then what does it returns …
Success! The configuration would have been updated for category ‘nginx’
nginx:
applied:
/etc/nginx/conf.d/exmple.com.conf:
status: created
/etc/nginx/conf.d/exmple.com.d/yunohost_local.conf:
status: created
/etc/nginx/conf.d/global.conf:
status: managed
/etc/nginx/conf.d/ssowat.conf:
status: managed
/etc/nginx/conf.d/yunohost_admin.conf:
status: managed
/etc/nginx/conf.d/yunohost_admin.conf.inc:
status: managed
/etc/nginx/conf.d/yunohost_api.conf.inc:
status: managed
/etc/nginx/conf.d/yunohost_panel.conf.inc:
status: managed
/var/www/.well-known/exmple.com/autoconfig/mail/config-v1.1.xml:
status: created
pending:
Then let’s run yunohost tools regen-conf nginx --force
Thanks!!!
It works now !!!
Hope these issues are resolved in the next version
Will I have to run this command after each app installation?
And thanks again
Weeeell nope you shouldn’t have to … it’s not clear how that happened, it looks like 2 overlapping issues …
Can you tell if you did anything special about adding/removing domains ? Like is this domain you’re using right now the one you defined during the post-install ? Or did you add/remove domains in the meantime ? (Not that you shouldn’t do this but I’m trying to figure out a possible origin for the bug)
No, I did not remove the domain I use
I just set it in post-install and that’s it
I did not change anything in the domain after the post-install
Well I forgot about all the context of this post and all the issues that popped up … I don’t understand why so many things exploded …
The initial issue was also about a dovecot configuration not matching the regen-conf … I don’t understand how the system ended up in that state …
Does running 'yunohost tools regen-conf --dry-run' display other things ?
(maybe dnsmasq but that’s expected)
Success! The configuration would have been updated for category 'nginx'
nginx:
applied:
/etc/nginx/conf.d/exmple.com.conf:
status: created
/etc/nginx/conf.d/exmple.com.d/yunohost_local.conf:
status: created
/etc/nginx/conf.d/global.conf:
status: managed
/etc/nginx/conf.d/ssowat.conf:
status: managed
/etc/nginx/conf.d/yunohost_admin.conf:
status: managed
/etc/nginx/conf.d/yunohost_admin.conf.inc:
status: managed
/etc/nginx/conf.d/yunohost_api.conf.inc:
status: managed
/etc/nginx/conf.d/yunohost_panel.conf.inc:
status: managed
/var/www/.well-known/exmple.com/autoconfig/mail/config-v1.1.xml:
status: created
pending:
root@apps:~# yunohost tools regen-conf nginx --force
Success! Configuration updated for 'nginx'
nginx:
applied:
/etc/nginx/conf.d/exmple.com.conf:
status: force-created
/etc/nginx/conf.d/exmple.com.d/yunohost_local.conf:
status: force-created
/etc/nginx/conf.d/global.conf:
status: managed
/etc/nginx/conf.d/ssowat.conf:
status: managed
/etc/nginx/conf.d/yunohost_admin.conf:
status: managed
/etc/nginx/conf.d/yunohost_admin.conf.inc:
status: managed
/etc/nginx/conf.d/yunohost_api.conf.inc:
status: managed
/etc/nginx/conf.d/yunohost_panel.conf.inc:
status: managed
/var/www/.well-known/exmple.com/autoconfig/mail/config-v1.1.xml:
status: force-created
pending:
root@apps:~# nano /etc/nginx/conf.d/exmple.com.conf
root@apps:~# yunohost tools regen-conf --dry-run
Info: The configuration file '/etc/default/glances' is now managed by YunoHost (category glances).
Success! The configuration would have been updated for category 'glances'
Info: The configuration file '/etc/metronome/metronome.cfg.lua' is now managed by YunoHost (category metronome).
Success! The configuration would have been updated for category 'metronome'
Info: The configuration file '/etc/postfix/master.cf' is now managed by YunoHost (category postfix).
Info: The configuration file '/etc/postfix/main.cf' is now managed by YunoHost (category postfix).
Info: The configuration file '/etc/default/postsrsd' is now managed by YunoHost (category postfix).
Success! The configuration would have been updated for category 'postfix'
Success! The configuration would have been updated for category 'rspamd'
Info: The configuration file '/etc/default/dnsmasq' is now managed by YunoHost (category dnsmasq).
Info: The configuration file '/etc/dnsmasq.conf' is now managed by YunoHost (category dnsmasq).
Success! The configuration would have been updated for category 'dnsmasq'
Info: The configuration file '/etc/fail2ban/jail.conf' is now managed by YunoHost (category fail2ban).
Success! The configuration would have been updated for category 'fail2ban'
Info: The configuration file '/etc/mysql/my.cnf' is now managed by YunoHost (category mysql).
Success! The configuration would have been updated for category 'mysql'
Info: The configuration file '/etc/avahi/avahi-daemon.conf' is now managed by YunoHost (category avahi-daemon).
Success! The configuration would have been updated for category 'avahi-daemon'
Success! The configuration would have been updated for category 'slapd'
avahi-daemon:
applied:
/etc/avahi/avahi-daemon.conf:
status: new
pending:
dnsmasq:
applied:
/etc/default/dnsmasq:
status: new
/etc/dnsmasq.conf:
status: new
/etc/dnsmasq.d/exmple.com:
status: created
/etc/resolv.dnsmasq.conf:
status: created
pending:
fail2ban:
applied:
/etc/fail2ban/filter.d/yunohost.conf:
status: created
/etc/fail2ban/jail.conf:
status: new
/etc/fail2ban/jail.d/yunohost-jails.conf:
status: created
pending:
glances:
applied:
/etc/default/glances:
status: new
pending:
metronome:
applied:
/etc/metronome/conf.d/exmple.com.cfg.lua:
status: created
/etc/metronome/metronome.cfg.lua:
status: new
pending:
mysql:
applied:
/etc/mysql/my.cnf:
status: new
pending:
postfix:
applied:
/etc/default/postsrsd:
status: new
/etc/postfix/header_checks:
status: created
/etc/postfix/ldap-accounts.cf:
status: created
/etc/postfix/ldap-aliases.cf:
status: created
/etc/postfix/ldap-domains.cf:
status: created
/etc/postfix/main.cf:
status: new
/etc/postfix/master.cf:
status: new
/etc/postfix/sender_canonical:
status: created
/etc/postfix/smtp_reply_filter:
status: created
pending:
rspamd:
applied:
/etc/dovecot/global_script/rspamd.sieve:
status: created
/etc/rspamd/local.d/dkim_signing.conf:
status: created
/etc/rspamd/local.d/metrics.conf:
status: created
pending:
slapd:
applied:
/etc/default/slapd:
status: managed
/etc/ldap/ldap.conf:
status: managed
/etc/ldap/schema/mailserver.schema:
status: managed
/etc/ldap/schema/sudo.schema:
status: managed
/etc/ldap/schema/yunohost.schema:
status: managed
/etc/ldap/slapd.conf:
status: managed
pending:
It turns out that I copied a bit more
Well then … You should probably run yunohost tools regen-conf --force
But that’s really weird, like … When you ran the postinstall initially, didn’t you saw a bunch of errors ? Did it even complete …?
He failed at Firewall but everything “worked” 
so I thought he just couldn’t do it.
After running it, the Monitoring also works now
é_è
What hardware are you running ?
If you have some patience it would be nice to investigate the postinstallation log … :
yunohost log list | grep postinstall | grep name | awk '{print $2}'
should show some ID … then using that ID :
yunohost log display --share <the ID you found>
Alright so the original issue during postinstall is a bit hidden but :
ValueError: unknown locale: en_IL
Same error as earlier so that explains many things about why the regen-conf was not performed … Thanks
So all the problems were because of the unknown locale: en_IL?
Really annoying …
Yeah … So it’s fixed now
But the fact that half the postinstall crashed because of the firewall failing to reload is also debatable
(On the other hand, having zero firewall is really not cool for a server)