nginx:
applied:
pending:
/etc/nginx/conf.d/sandbox.cryptpad.domaine.tld.conf:
diff: @@ -1,75 +0,0 @@
-# Note this is a mostly a copy of https://github.com/YunoHost/yunohost/blob/dev/conf/nginx/server.tpl.conf
-# But with some cleanup of all not necessary things
-
-server {
- listen 80;
- listen [::]:80;
- server_name sandbox.cryptpad.domaine.tld;
-
- include /etc/nginx/conf.d/acme-challenge.conf.inc;
-
- location ^~ '/.well-known/ynh-diagnosis/' {
- alias /var/www/.well-known/ynh-diagnosis/;
- }
-
- # Note that this != "False" is meant to be failure-safe, in the case the redrect_to_https would happen to contain empty string or whatever value. We absolutely don't want to disable the HTTPS redirect *except* when it's explicitly being asked to be disabled. #}
- location / {
- return 301 https://$host$request_uri;
- }
-
- include /etc/nginx/conf.d/yunohost_http_errors.conf.inc;
-
- access_log /var/log/nginx/cryptpad.domaine.tld-access.log;
- error_log /var/log/nginx/cryptpad.domaine.tld-error.log;
-}
-
-server {
- listen 443 ssl http2;
- listen [::]:443 ssl http2;
- server_name sandbox.cryptpad.domaine.tld;
-
- include /etc/nginx/conf.d/security.conf.inc;
-
- ssl_certificate /etc/yunohost/certs/cryptpad.domaine.tld/crt.pem;
- ssl_certificate_key /etc/yunohost/certs/cryptpad.domaine.tld/key.pem;
-
- more_set_headers "Strict-Transport-Security : max-age=63072000; includeSubDomains; preload";
-
- include /etc/nginx/conf.d/cryptpad-shared.conf.inc;
-
- # We consider that the CA is letsencrypt but yes it could be not allways the case
- # This should be improved mybe at some point if this is a problem in some cases
-
- # OCSP settings
- ssl_stapling on;
- ssl_stapling_verify on;
- ssl_trusted_certificate /etc/yunohost/certs/cryptpad.domaine.tld/crt.pem;
- resolver 1.1.1.1 9.9.9.9 valid=300s;
- resolver_timeout 5s;
-
- access_log /var/log/nginx/cryptpad.domaine.tld-access.log;
- error_log /var/log/nginx/cryptpad.domaine.tld-error.log;
-
- location / {
- proxy_pass http://localhost:3000;
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header Host $host;
- proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
- client_max_body_size 150m;
-
- proxy_http_version 1.1;
- proxy_set_header Upgrade $http_upgrade;
- proxy_set_header Connection upgrade;
- }
-
- location ^~ /cryptpad_websocket {
- proxy_pass http://localhost:3003;
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header Host $host;
- proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-
- proxy_http_version 1.1;
- proxy_set_header Upgrade $http_upgrade;
- proxy_set_header Connection upgrade;
- }
-}
status: unmanaged
just be careful, yesterday upgrading to 12.1.32, I have do a yunohost tools regen-conf --force and it’s the first time it have deleted the file /etc/nginx/conf.d/sandbox.cryptpad.domaine.tld.conf…
So I have edited manually this file looking in the repo how it need to be written and in the settings of the application for the keys needed, and the restarted cryptpad… The better way will be first do a copy of this file before…
cp -a /etc/nginx/conf.d/sandbox.cryptpad.domaine.tld.conf
But anyway, here you haven’t a proposed regen-conf for postfix and/or dnsmasq, so it is not the worry… Are the ports 25 and 587 open ? yunohost firewall list ?
Is the services running ? yunohost service status postfix and yunohost status service dovecot ?
Je ne sais pas pourquoi Spamhaus ZEN décide de bloquer comme bon lui semble.
Je n’envoie pas de mail à qui que ce soit, pour quoi que ce soit, je me sers de la boite mail juste pour recevoir les notifs de Mastodon, pour les mises à jour, les renew cert et rien d’autre…
Hier, avant-hier, tout était correct et voilà que Spamhaus ZEN a décidé de me faire comprendre que je ne peux ni envoyer, ni recevoir de mails, alors que je ne l’utilise pas pour autre chose que le serveur.
Dans ce que tu indiques il n’y aucune information qui permet de voir ou confirmer ou comprendre ce qui se passe … si tu as un message d’erreur qui parle de Spamhaus, il faut le partager, on ne peut pas lire dans les boules de cristal
, je sature complètement 