Hi First off, please note I am new to this server related stuff. I had successfully installed ISPConfig on a new Ubuntu Server. And all was fine, I created some websites, FTP users etc. But then got stuck trying to uplad files to the server and ended up messing around with directory ownership and permissions, when all of a sudden I couldnt access ISPConfig anymore from myip:8080 I have been trouble shooting for days now, and dont know what to do, please help. SPECS: Code: root@local:~# uname -a Linux local 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@local:~# php -v PHP 7.0.30-0ubuntu0.16.04.1 (cli) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.0.30-0ubuntu0.16.04.1, Copyright (c) 1999-2017, by Zend Technologies root@local:~# apache2 -v Server version: Apache/2.4.18 (Ubuntu) Server built: 2018-06-07T19:43:03 root@local:~# mysql --version mysql Ver 14.14 Distrib 5.7.23, for Linux (x86_64) using EditLine wrapper My /etc/hosts: Code: 127.0.0.1 localhost 196.41.127.180 local.localhost.co.za local # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters ERROR LOG: Code: root@local:~# vim /var/log/apache2/error.log [Sat Aug 04 19:49:52.148585 2018] [mpm_event:notice] [pid 4489:tid 140202799032192] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations [Sat Aug 04 19:49:52.148911 2018] [core:notice] [pid 4489:tid 140202799032192] AH00094: Command line: '/usr/sbin/apache2' [Sat Aug 04 19:49:58.592453 2018] [mpm_event:notice] [pid 4489:tid 140202799032192] AH00491: caught SIGTERM, shutting down [Sat Aug 04 19:49:59.837413 2018] [mpm_event:notice] [pid 4668:tid 139650455000960] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations [Sat Aug 04 19:49:59.837621 2018] [core:notice] [pid 4668:tid 139650455000960] AH00094: Command line: '/usr/sbin/apache2' [Sat Aug 04 19:52:22.672678 2018] [mpm_event:notice] [pid 4668:tid 139650455000960] AH00491: caught SIGTERM, shutting down [Sat Aug 04 19:53:11.698691 2018] [mpm_event:notice] [pid 1178:tid 139999964710784] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations [Sat Aug 04 19:53:11.723860 2018] [core:notice] [pid 1178:tid 139999964710784] AH00094: Command line: '/usr/sbin/apache2' [Sat Aug 04 22:01:18.003470 2018] [mpm_event:notice] [pid 1178:tid 139999964710784] AH00491: caught SIGTERM, shutting down [Sat Aug 04 22:01:19.175136 2018] [mpm_event:notice] [pid 10938:tid 140161656473472] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations [Sat Aug 04 22:01:19.175509 2018] [core:notice] [pid 10938:tid 140161656473472] AH00094: Command line: '/usr/sbin/apache2'
ALSO, here are the open ports: Code: root@local:~# sudo netstat -plunt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 1089/memcached tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 1170/redis-server 1 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1096/sshd tcp6 0 0 :::8080 :::* LISTEN 19459/apache2 tcp6 0 0 :::8081 :::* LISTEN 19459/apache2 tcp6 0 0 :::22 :::* LISTEN 1096/sshd udp 0 0 196.41.127.180:123 0.0.0.0:* 1316/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 1316/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 1316/ntpd udp6 0 0 fe80::250:56ff:fe9f:123 :::* 1316/ntpd udp6 0 0 ::1:123 :::* 1316/ntpd udp6 0 0 :::123 :::* 1316/ntpd
You wrote you Code: ended up messing around with directory ownership and permissions, but do not show what owners and permissions are now. I suggest starting again: install ubuntu and ispconfig, and do not change owners and permissions.
You can go back to the image copy of the server you took before installing ISPConfig. Or restore from backup the files as they were before changes to owners and permissions. If it is not possible to install Ubuntu to your virtual server, ask SP to re-image it.
I unfortunately didn't make a copy or backup, I have asked them to do exactly that for me, we'll see what they say
For me if you still have access to your virtual server control panel and you can ssh to your terminal, you can always resolve your problem provided you know how to troubleshoot. If you plan to start with current db and files, backup before you redo your server. Normally, you can simply delete your current vps volume and then fresh setup your ubuntu server + ISPConfig again.
What you saying makes sense, problem is I have tried and can't seem to troubleshoot the problem, I have my SP to mount the image, so that I can start again. I'm not really concerned about files and database, since it was a new install anyway. Now just to figure out how to do what you suggest last.
Deleting your vps volume that contains your ubuntu server or creating a new one is normally done your vps control panel, at least it works that way while I was using AWS and Scaleway some times ago. Further than that, you can use script or manually install your perfect server using ssh via terminal.
Ok so I have Ubuntu re-installed, have done nothing else. Is it better to use the script for auto instal of ISPConfig https://www.howtoforge.com/tutorial/ispconfig-automated-install-script/ or the manual tutorial https://www.howtoforge.com/tutorial...pureftpd-bind-postfix-doveot-and-ispconfig/3/
Ok I'll give that a go then. is there anything I should do first, backup or create restore point or install anything else?
With virtual hosts it is usually easy and fast to take a snapshot or restore point, what ever it is called. That is useful if something happens and you need to go back to older setup. Is there already something installed on that Ubuntu? ISPConfig installation assumes it is a plain Ubuntu when you start following the Perfect Server installation Guide.
I ended up using the tutorial, and have just finished the installation, all seems to have gone well. I'll figure out now how to take a snapshot of this point
Always keep a copy of the successful working version before you make any changes, in case you need to revert back to it. It will save a lot of time in the future by having this backup copy.
