Yeah … I had to delete the ssl directory as the key seemingly did not come through with the backup — as there have been other reports of. I ran the script to issue the certs from the command line so that the system was up with SSL. I am not 100% certain at what point I reran setup but I know that I have at least once. It doesn’t hurt anything to rerun it so I shall try it again in a bit.
Re-ran set up. No change. It did remind me of the Nextcloud issues that are seemingly caused when migrating…
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed
Maintenance mode is kept active
Reset log level
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Exception: Updates between multiple major versions and downgrades are unsupported.
Update failed
Maintenance mode is kept active
Reset log level
But that is another issue … one of no real importance to me as NextCloud is not actively used.
As ya know from earlier interactions, I am not overly familiar with the various logs … that said …
/var/log/syslog shows nothing relevant … it does show the daily cron jobs for /management/daily_tasks.py and one successful dns entry (see below) … as far as ‘systemctl status mailinabox’, I assume that was a command line that you wanted me to run … and if so, it came back with ‘systemctl: command not found’.
No luck … I removed the ssl directory and ran the ssl_certificates.py and it failed as it could not find the ssl directory … (odd as I thought that py file was to issue the certs and create the directory). I then reran mailinabox and then NO admin pages would come up! After that, I ran the ssl_certificates.py and it issued the cert(s) for the domains which are actually pointed to the box. So now, seemingly back to where I started … but no! The system status checks page did not come up still until I tried all pages, then tried it again and it worked … but still no TLS page.
After several tests and reviewing log files looking for an error that we could not find it seems that the box times out if there are over about 20-22 subdomains. It has not been clear exactly what causes the issue but once I cleaned out some unused subdomains things magically began to work normally.
A thank you to @murgero for all of his help in PM.
My conclusion is that although there are no stated specific limits as to how many domains MiaB can handle. There IS a limiting factor somewhere. As this project is not specifically geared towards “enterprise” use and the typical user will have one maybe two domains, I do not know that this issue is worth looking in to further. Maybe @JoshData should decide that.
After that, I ran the ssl_certificates.py and it issued the cert(s) for the domains which are actually pointed to the box. So now, seemingly back to where I started … but no! The system status checks page did not come up still until I tried all pages, then tried it again and it worked … but still no TLS page.