I have an Ubuntu 18.04.6 TLS server with ISPConfig Version: 3.2 and many websites installed. The web server broke and all websites just show the Apache2 Ubuntu Default Page, but the other services work fine. Also, port 8080 is not listening and I can no longer access the ISPConfig panel. On top of that, the apt-get command doesn't work and I can't install anything. Since I can't access the panel, I'm wondering if it's possible to set up another server with Ubuntu 18.04 LTS and install everything from the backup file that I get from the ISPConfig update command? Does it make sense?
Repairing your current server is likely easier than trying to restore a backup. So, I would suggest repairing the current setup and, when it works again, using the Migration Tool to move your system over to a new, clean Ubuntu 22.04 system. The backups contain a copy of the /etc folder, unpack the tar.gz of the /etc folder and then copy over /etc/apache2 from the backup to your system to restore the apache2 config, then restart apache2. Ensure that you preserver permissions when copying the config files over (cp -prf .......) and before you start, make a backup of the /etc/apache2 folder. If you need help with that via remote login, then you might want o contact Thom here: https://www.ispconfig.org/get-support/
No. The backups are just tar.gz archives of the relevant folders like /etc and /usr/local/ispconfig, plus a database dump of the database content (not tables). There is nothing ISPConfig specific to restore this, you just unpack what you need and then copy the parts you need back to their original location, like I mentioned above. Maybe you should consider contacting ISPConfig business support or any other experienced Linux admin to help you with that.
I have one last problem now... after fixing the web server, the email stopped working and shows this error message: Code: SMTP Error (451): Failed to add recipient "[email protected]" (4.3.5 <localhost[127.0.0.1]>: Client host rejected: Server configuration error). I set up Postfix with an SMTP relay service (Mailgun). This is the maill.log output: Code: May 4 07:02:34 servidor1 postfix/smtpd[13494]: connect from localhost[127.0.0.1] May 4 07:02:34 servidor1 postfix/smtpd[13494]: 3416B9C0E74: client=localhost[127.0.0.1] May 4 07:02:34 servidor1 postfix/proxymap[15740]: warning: mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf is unavailable. open /etc/postfix/mysql-virtual_outgoing_bcc.cf: Permission denied May 4 07:02:34 servidor1 postfix/cleanup[13495]: warning: proxy:mysql:/etc/postfix/mysql-virtual_outgoing_bcc.cf lookup error for "[email protected]" May 4 07:02:34 servidor1 postfix/cleanup[13495]: warning: 3416B9C0E74: sender_bcc_maps map lookup problem -- message not accepted, try again later May 4 07:02:34 servidor1 amavis[15593]: (15593-02-2) Negative SMTP response to data-dot (<[email protected]>): 451 4.3.0 Error: queue file write error, dt: 0.2 ms May 4 07:02:34 servidor1 amavis[15593]: (15593-02-2) (!)aM9H34o4D6Og FWD from <[email protected]> -> <[email protected]>, BODY=7BIT 451 4.3.0 from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error May 4 07:02:34 servidor1 postfix/proxymap[15740]: warning: mysql:/etc/postfix/mysql-virtual_forwardings.cf is unavailable. open /etc/postfix/mysql-virtual_forwardings.cf: Permission denied May 4 07:02:34 servidor1 postfix/cleanup[13495]: warning: proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf lookup error for "[email protected]" May 4 07:02:34 servidor1 postfix/cleanup[13495]: warning: 347CC9C0E74: virtual_alias_maps map lookup problem for [email protected] -- message not accepted, try again later May 4 07:02:34 servidor1 postfix/smtpd[13494]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=0/1 commands=3/4 May 4 07:02:34 servidor1 amavis[15593]: (15593-02-2) Blocked MTA-BLOCKED {TempFailedInbound}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: aM9H34o4D6Og, Hits: 0, size: 670, 22298 ms May 4 07:02:34 servidor1 postfix/smtp[13286]: 8A78F9C0E7C: to=<[email protected]>, orig_to=<root>, relay=127.0.0.1[127.0.0.1]:10024, conn_use=2, delay=453, delays=175/255/0/22, dsn=4.3.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.3.0 id=15593-02-2 - Temporary MTA failure on relaying, from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error (in reply to end of DATA command)) May 4 07:02:34 servidor1 postfix/proxymap[15740]: warning: mysql:/etc/postfix/mysql-virtual_relaydomains.cf is unavailable. open /etc/postfix/mysql-virtual_relaydomains.cf: Permission denied May 4 07:02:34 servidor1 postfix/smtp[13286]: warning: fast_flush_domains: proxy:mysql:/etc/postfix/mysql-virtual_relaydomains.cf: table lookup problem May 4 07:02:34 servidor1 postfix/smtp[13286]: warning: 8A78F9C0E7C: flush service failure
You wrote in #1 Was e-mail working then? To find out what is wrong now, follow this: https://forum.howtoforge.com/threads/please-read-before-posting.58408/ Next time, post ISPConfig questions on ISPConfig forum.
