Access to admin not possible

Maintenance
1

Hello,

after more than 18 months using my MIAB instance (hosted on my own server) without any defects, I encounter a problem since some days.
My SSL certs had expired so I’d a connection to admin page to renew them.
Something should be wrong, because I can’t access anymore to the admin in HTTPS

But emails are sent and received with IMAP/SMTP.

A time out occured after 5-10 seconds and I get an error “connection has failed”. Tested on Firefox, Brave and Edge.
Same result if I try to connect on HTTP port 80.

I can only connect with SSH to my server, but I don’t know what to check and do for solving this problem.

I tried to reboot the server ==> no more good result
I also tried to start again the setup.sh process while I have installed the last version 0.71a some months ago.

Does someone here has some tips for me ?

2

Try sudo management/ssl_certificates.py from your mailinabox installation directory to see if you can renew the certificates from the ssh command line.

1 Like
3

Also try https://IP_Address_of_Server/admin

Then agree to all the cert warnings - that will get you into the web interface if need be

4

Thanks for this tip stylnchris, tried to connect to HTTP , but no more success :frowning:

5

Tried, but still errors :

Extract of logs (very light because I can’t post links and it seems even domain names) :

The domain has a valid certificate already. (The certificate expires in 79 days on 2025-12-31. Certificate: /home/user-data/ssl/-20251231-ab1c2def.pem, private key /home/user-data/ssl/ssl_private_key.pem)

…

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain:
Type: connection
Detail: 123.123.123.123: Fetching /.well-known/acme-challenge/L-SM5UftZeGyZMIi5L6KCyyPTSF2_O41_tcG3HfHhj0: Connection refused

While trying to connect to and , I got a timeout

Of course, I’ve checked and the firewall has been opened for port 80 (not only 443)
Also a NSLookup for and returns the correct IP address.

Should I begin to think it’s a webserver (nginx ?) problem ?

6

Don’t waste time, I think I’ve found my problem.
I’ve only tried to enable and start nginx service and everything is working fine.

Strange, because I’d already rebooted the server twice some days ago.
And it’s like the service was disabled :thinking:

7

Sometimes the service won’t start on some boxes because of conflicting ports or because the box came up to fast and something else wasn’t ready. I would check the /var/log/messages and see if you can figure that out.

1 Like
8

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