Can´t renew and create Let’s Encrypt certificates anymore

rockyIII · September 7, 2022, 3:51pm

Hardware: VPS
YunoHost version: 1.0.9.14 just updated few hours ago
**I have access to my server :yes local ip, https domain & ssh working

can ´t renew and create Let’s Encrypt certificates anymore

it used to work just fine - i had to run the diagnosis test and return to the /cert-management page and than i could create the Let’s Encrypt certificates but today i noticed it does not work anymore that way

if i want to create a new one for a new domain i just can´t click the button “Install Let’s Encrypt certificate”
and
if i try to renew a certificate for an old domain manually i get a warning like this:

The DNS records for domain ‘xyz.domain.tld’ is different from this server’s IP. Please check the ‘DNS records’ (basic) category in the diagnosis for more info. If you recently modified your A record, please wait for it to propagate (some DNS propagation checkers are available online). (If you know what you are doing, use ‘–no-checks’ to turn off those checks.)

What could i try ? - Thanks for help

Aleks · September 7, 2022, 9:43pm

So what does the diagnosis says about your domain ?

rockyIII · September 8, 2022, 6:21am

https://paste.yunohost.org/raw/ijuzenumiz

Aleks · September 8, 2022, 6:50am

Du coup comme expliqué dans le diagnostique, tu as des enregistrements AAAA pour tes noms de domaines alors que ton serveur n’a pas (ou plus) d’IPv6 …

rockyIII · September 8, 2022, 7:02am

the server never had IPv6 records

rockyIII · September 8, 2022, 7:05am

Ok I will try to sett this records by Setting up IPv6 | Yunohost Documentation

how do i find out the IPv6 gateway ?

rockyIII · September 8, 2022, 7:44am

there seams a problem with networking.service on my server

admin@admin:~$ systemctl status networking.service
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)                                                               
     Active: failed (Result: exit-code) since Thu 2022-09-08 09:35:27 CEST; 2min 55s ago
       Docs: man:interfaces(5)                                                                                                                              
    Process: 4134044 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
   Main PID: 4134044 (code=exited, status=1/FAILURE)                                                                                                        
        CPU: 43ms

How to deal with it? THANKS

rockyIII · September 8, 2022, 9:23am

admin@admin:~$ sudo service networking restart                                                                                              
Job for networking.service failed because the control process exited with error code.                                                       
See "systemctl status networking.service" and "journalctl -xe" for details.                                                                 
admin@admin:~$ systemctl status networking.service                                                                                          
● networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)                                               
     Active: failed (Result: exit-code) since Thu 2022-09-08 11:21:53 CEST; 11s ago
       Docs: man:interfaces(5)                                                                                                              
    Process: 4146836 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
   Main PID: 4146836 (code=exited, status=1/FAILURE)                                                                                        
        CPU: 27ms                                                                                                                           
admin@admin:~$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.                                                                
      Users in groups 'adm', 'systemd-journal' can see all messages.                                                                        
      Pass -q to turn off this notice.                                                                                                      
Sep 07 22:40:03 admin.domain.tld su[4064530]: pam_unix(su:auth): authentication failure; logname=admin uid=1007 euid=0 tty=pts/1 ruser>
Sep 07 22:40:06 admin.domain.tld su[4064530]: FAILED SU (to root) admin on pts/1                                                       
Sep 07 22:56:10 admin.domain.tld sshd[4021153]: Read error from remote host 92.216.156.129 port 52400: Connection reset by peer        
Sep 07 23:05:00 admin.domain.tld su[4066046]: pam_unix(su:auth): authentication failure; logname=admin uid=1007 euid=0 tty=pts/1 ruser>
Sep 07 23:05:03 admin.domain.tld su[4066046]: FAILED SU (to root) admin on pts/1                                                       
Sep 07 23:05:38 admin.domain.tld su[4067952]: (to root) admin on pts/1                                                                 
Sep 07 23:05:38 admin.domain.tld su[4067952]: pam_unix(su:session): session opened for user root(uid=0) by admin(uid=1007)             
Sep 07 23:21:26 admin.domain.tld su[4067952]: pam_unix(su:session): session closed for user root                                       
Sep 08 08:43:37 admin.domain.tld systemd[4128442]: Failed to determine supported controllers: No such process
Sep 08 08:43:37 admin.domain.tld systemd[4128442]: Failed to allocate manager object: No such process
Sep 08 08:46:16 admin.domain.tld sudo[4129116]:    admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/ping6 ip6.allmen>
Sep 08 08:46:16 admin.domain.tld sudo[4129116]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 08:46:16 admin.domain.tld sudo[4129116]: pam_unix(sudo:session): session closed for user root                                   
Sep 08 09:35:27 admin.domain.tld sudo[4134034]:    admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/sbin/service network>
Sep 08 09:35:27 admin.domain.tld sudo[4134034]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 09:35:27 admin.domain.tld sudo[4134034]: pam_unix(sudo:session): session closed for user root                                   
Sep 08 11:03:05 admin.domain.tld systemd[4143550]: Failed to determine supported controllers: No such process
Sep 08 11:03:05 admin.domain.tld systemd[4143550]: Failed to allocate manager object: No such process
Sep 08 11:04:14 admin.domain.tld sudo[4143870]:    admin : TTY=pts/1 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/ping6 ip6.allmen>
Sep 08 11:04:14 admin.domain.tld sudo[4143870]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 11:04:14 admin.domain.tld sudo[4143870]: pam_unix(sudo:session): session closed for user root                                   
Sep 08 11:04:37 admin.domain.tld sudo[4144017]:    admin : TTY=pts/1 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/ping6 ip4.allmen>
Sep 08 11:04:37 admin.domain.tld sudo[4144017]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 11:04:37 admin.domain.tld sudo[4144017]: pam_unix(sudo:session): session closed for user root                                   
Sep 08 11:05:43 admin.domain.tld sudo[4144166]:    admin : TTY=pts/1 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/sbin/service network>
Sep 08 11:05:43 admin.domain.tld sudo[4144166]: pam_unix(sudo:session): session closed for user root(uid=0) by admin(uid=1007)         
                                                                                                                                            
Sep 08 11:06:24 admin.domain.tld sudo[4144259]:    admin : TTY=pts/1 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/sbin/service network>
Sep 08 11:06:24 admin.domain.tld sudo[4144259]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 11:06:24 admin.domain.tld sudo[4144259]: pam_unix(sudo:session): session closed for user root                                   
Sep 08 11:06:52 admin.domain.tld sudo[4144403]:    admin : TTY=pts/1 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/systemctl status>
Sep 08 11:06:52 admin.domain.tld sudo[4144403]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 11:06:52 admin.domain.tld sudo[4144403]: pam_unix(sudo:session): session closed for user root                                   
Sep 08 11:21:23 admin.domain.tld systemd[4146693]: Failed to determine supported controllers: No such process
Sep 08 11:21:23 admin.domain.tld systemd[4146693]: Failed to allocate manager object: No such process
Sep 08 11:21:53 admin.domain.tld sudo[4146827]:    admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/sbin/service network>
Sep 08 11:21:53 admin.domain.tld sudo[4146827]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)         
Sep 08 11:21:53 admin.domain.tld sudo[4146827]: pam_unix(sudo:session): session closed for user root

rockyIII · September 27, 2022, 6:42am

now the main domain of my YH installation is also not working anymore because the Let’s Encrypt certificates was not renewed automatically…
than I did a manual update - i get a green light saying that the Let’s Encrypt is now valid for 40 dasys - but the site is still nor reachable

system · October 27, 2022, 6:42am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.