Hi, Jesse with ls -l I get the following root@vps622713:~# ls -l total 8 -rw-r--r-- 1 root root 0 Apr 20 22:08 htf-common-issues.php -rw-r--r-- 1 root root 278 Apr 4 11:03 letsencrypt-renewal.sh drwx------ 3 root root 4096 Apr 4 11:25 snap root@vps622713:~# with curl -v http://gitplace.net/pixcept/ispconfig-tools/raw/stable/htf-common-issues.php get the following root@vps622713:~# < -bash: syntax error near unexpected token `newline' root@vps622713:~# <html> -bash: syntax error near unexpected token `newline' root@vps622713:~# <head><title>301 Moved Permanently</title></head> -bash: syntax error near unexpected token `<' root@vps622713:~# <body bgcolor="white"> -bash: syntax error near unexpected token `newline' root@vps622713:~# <center><h1>301 Moved Permanently</h1></center> -bash: syntax error near unexpected token `<' root@vps622713:~# <hr><center>nginx/1.14.2</center> -bash: syntax error near unexpected token `<' root@vps622713:~# </body> -bash: syntax error near unexpected token `newline' root@vps622713:~# </html> -bash: syntax error near unexpected token `newline' root@vps622713:~# * Curl_http_done: called premature == 0 -bash: Accept:: command not found root@vps622713:~# * Connection #0 to host gitplace.net left intact -bash: Accept:: command not found root@vps622713:~# root@vps622713:~# clear -bash: root@vps622713:~#: command not found root@vps622713:~# clear root@vps622713:~# curl -v http://gitplace.net/pixcept/ispconfig-tools/raw/stable/htf-common-issues.php * Trying 116.203.199.227... * TCP_NODELAY set * Connected to gitplace.net (116.203.199.227) port 80 (#0) > GET /pixcept/ispconfig-tools/raw/stable/htf-common-issues.php HTTP/1.1 > Host: gitplace.net > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Server: nginx/1.14.2 < Date: Thu, 21 Apr 2022 15:02:53 GMT < Content-Type: text/html < Content-Length: 185 < Connection: keep-alive < Location: https://gitplace.net/pixcept/ispconfig-tools/raw/stable/htf-common-issues.php < <html> <head><title>301 Moved Permanently</title></head> <body bgcolor="white"> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> * Curl_http_done: called premature == 0 * Connection #0 to host gitplace.net left intact root@vps622713:~#
a question I have downloaded a copy of the complete website and database. If I reinstall the entire Debian 9 OS and completely reinstall ISPConfig again from The Perfect Server - Debian 9 (Stretch) with Apache, BIND, Dovecot, PureFTPD and ISPConfig 3.1 and upload the copy of the website and the database back to the buckups folder. Could I get it working again?
So that confirms that wget did not download the php script, which is why it doesn't run. That looks correct. If you request the https url, do you get the file contents? ie. 'curl -v https://gitplace.net/pixcept/ispconfig-tools/raw/stable/htf-common-issues.php' You can also try changing the protocol to https in the wget command and see if that downloads the file or not; wget should follow the redirect, but I suppose could be configured to not do so. Or maybe there's a certificate verification issue or similar.
Well, the general idea of "backup my data, rebuild a new server and restore the backup" can work (though it seems much overkill for your issue), but I would not recommend you do that, as it takes some understanding of things and troubleshooting/fix ability when things don't work right the first time; if it comes to that point, I would recommend you hire help to perform the backup/restore.
Hi Jesse The possible solutions that you are giving me do nothing. They don't give any results I can connect to my server by WINscp and by console but I can't enter the ISPconfig panel, and I can't see the web https://51.75.254.67:8080/ It can not be connected and with http protocol, it is the same connection error
Regarding your initial issue, we need a lot more info to be able to know what direction to head in resolving it, so you were directed to download and run a script which gathers a lot of that info and makes it easy to share and generally saves time; my suggestions at this point are trying to assist you in downloading that script so you can provide more info to troubleshoot what is going on. It would help if you would answer questions asked of you and follow directions given, as numerous times in this thread you have not done that, but (surely with the best of intentions), you instead go off in your own direction. You could try rebooting the server, it may or may not help (I suspect not). At this point I tested and, as you, I cannot connect to port 8080 on your ip; there are two possibilities, either apache is not listening on that port, or something is blocking the connection (eg. some modem/router type devices do this). What do you get from 'lsof -i :8080' and from 'apachectl -S' ? Please post the output here in a code block (see the "Please read before posting!" post in this forum if it is unclear what that means).
Hi Jesse Regarding your initial issue, we need a lot more info to be able to know what direction to head in resolving it, so you were directed to download and run a script which gathers a lot of that info and makes it easy to share and generally saves time; my suggestions at this point are trying to assist you in downloading that script so you can provide more info to troubleshoot what is going on. It would help if you would answer questions asked of you and follow directions given, as numerous times in this thread you have not done that, but (surely with the best of intentions), you instead go off in your own direction. Since I started this thread, I am doing what you tell me. I have repeated several times that the script does not download or does not work. I do not know how to explain it. I have made a small video for you to see. I have followed your instructions repeating the process several times, without getting any information. I don't think I'm that stupid You could try rebooting the server, it may or may not help (I suspect not). Restarting the server I have already done several times, even before opening this thread. I have not been successful At this point I tested and, as you, I cannot connect to port 8080 on your ip; there are two possibilities, either apache is not listening on that port, or something is blocking the connection (eg. some modem/router type devices do this). I think it must be an apache problem. What do you get from 'lsof -i :8080' i get nothing. the command returns to root and from 'apachectl -S' this is the response i get root@vps622713:~# apachectl -S VirtualHost configuration: *:80 vps622713.ovh.net (/etc/apache2/sites-enabled/000-default.conf:1) ServerRoot: "/etc/apache2" Main DocumentRoot: "/var/www/html" Main ErrorLog: "/var/log/apache2/error.log" Mutex authdigest-opaque: using_defaults Mutex watchdog-callback: using_defaults Mutex rewrite-map: using_defaults Mutex ssl-stapling-refresh: using_defaults Mutex authdigest-client: using_defaults Mutex ssl-stapling: using_defaults Mutex proxy: using_defaults Mutex ssl-cache: using_defaults Mutex default: dir="/var/run/apache2/" mechanism=default PidFile: "/var/run/apache2/apache2.pid" Define: DUMP_VHOSTS Define: DUMP_RUN_CFG Define: ENABLE_USR_LIB_CGI_BIN User: name="www-data" id=33 Group: name="www-data" id=33 root@vps622713:~# I repeat I think it must be an apache problem Thanks Jesse
When I execute the script that you tell me, I don't get anything. This is a copy of what appears on the console root@vps622713:~# wget -q -O htf-common-issues.php "http://gitplace.net/pixcept/ispconfig-tools/raw/stable/htf-common-issues.php" root@vps622713:~# I have tried it many times, even after restarting the server
This shows that you don't have any vhosts created, as well as the ispconfig vhost is missing. From your initial post I understood that you had ISPConfig setup with some websites in place, is that correct? Do you have any vhost files under /etc/apache2/sites-available/ ? Do you still have the ispconfig installation files under /usr/local/ispconfig/ ? You are getting an empty reply from the http url, which itself should redirect you to https, which is why I asked you: At this point the htf-common-issues.php script is irrelevant, we have the pertinent info, that nothing is listening on port 8080, and further that apache seems to have lost all vhost definitions in sites-enabled except for the default. So now we try to determine what state your system is in, to know what to do to repair it. You don't happen to have a backup prior to this happening, do you?
Hi Jesse I answer each of your questions This shows that you don't have any vhosts created, as well as the ispconfig vhost is missing. From your initial post I understood that you had ISPConfig setup with some websites in place, is that correct? I have this ISPConfig with a website that has been working well for more than a year and a half, until this problem with which I have opened this thread has happened Do you have any vhost files under /etc/apache2/sites-available/ ? Yes I have 3 files with vhost apps.vhost caminseivissa.org.vhost (is the name of the website) ispconfig.vhost Do you still have the ispconfig installation files under /usr/local/ispconfig/ ? Yes I have 3 folders interface security server with all the files inside the folders You don't happen to have a backup prior to this happening, do you? yes i have a backup I have a copy of the website and the database for several days and how can I access by Winscp, I have a backup copy of ISPConfig By WinSCP or FTP, I can access all the files on the server, it is a VPS this problem has appeared when renewing the let's encrypt SSL certificate
You could try: Code: ln -s /etc/apache2/sites-enabled/000-ispconfig.conf /etc/apache2/sites-available/ispconfig.conf ln -s /etc/apache2/sites-enabled/000-ispconfig.vhost /etc/apache2/sites-available/ispconfig.vhost ln -s /etc/apache2/sites-enabled/100-caminseivissa.org.vhost /etc/apache2/sites-available/caminseivissa.org.vhost systemctl reload apache2 That may get things back, or might just generate an error, eg. if one of the vhost files points to certificate files which don't exist or something. That is of course not normal, was this renewal a command you ran manually or ??
Hi,Jesse I reply to your comments ln -s /etc/apache2/sites-enabled/000-ispconfig.conf /etc/apache2/sites-available/ispconfig.conf returns the following ln: failed to create symbolic link '/etc/apache2/sites-available/ispconfig.conf': File exists ln -s /etc/apache2/sites-enabled/000-ispconfig.vhost /etc/apache2/sites-available/ispconfig.vhost ln: failed to create symbolic link '/etc/apache2/sites-available/ispconfig.vhost': File exists ln -s /etc/apache2/sites-enabled/100-caminseivissa.org.vhost /etc/apache2/sites-available/caminseivissa.org.vhost ln: failed to create symbolic link '/etc/apache2/sites-available/caminseivissa.org.vhost': File exists systemctl reload apache2 Does nothing That is of course not normal, was this renewal a command you ran manually or ?? Yes but I couldn't tell you what it was
Sorry, those were in wrong order: Code: ln -s /etc/apache2/sites-available/000-ispconfig.conf /etc/apache2/sites-enabled/ispconfig.conf ln -s /etc/apache2/sites-available/000-ispconfig.vhost /etc/apache2/sites-enabled/ispconfig.vhost ln -s /etc/apache2/sites-available/100-caminseivissa.org.vhost /etc/apache2/sites-enabled/caminseivissa.org.vhost systemctl reload apache2
Okay I have executed the three command lines ln -s /etc/apache2/sites-available/000-ispconfig.conf /etc/apache2/sites-enabled/ispconfig.conf ln -s /etc/apache2/sites-available/000-ispconfig.vhost /etc/apache2/sites-enabled/ispconfig.vhost ln -s /etc/apache2/sites-available/100-caminseivissa.org.vhost /etc/apache2/sites-enabled/caminseivissa.org.vhost In principle they have not given any error I have executed systemctl reload apache2, and gives this error Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
So now you need to look at what eror(s) is(are) causing the issue, eg. run the two commands shown there and/or check the apache error.log, and fix the error(s).
root@vps622713:~# systemctl status apache2.service ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2022-04-22 18:38:28 C EST; 6s ago Process: 9112 ExecStop=/usr/sbin/apachectl stop (code=exited, status=1 /FAILURE) Process: 8272 ExecReload=/usr/sbin/apachectl graceful (code=exited, st atus=1/FAILURE) Process: 9437 ExecStart=/usr/sbin/apachectl start (code=exited, status =1/FAILURE) Main PID: 1109 (code=exited, status=0/SUCCESS) Apr 22 18:38:28 vps622713 systemd[1]: Starting The Apache HTTP Server... Apr 22 18:38:28 vps622713 apachectl[9437]: apache2: Syntax error on line 225 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites- enabled/ispconfig.conf: No such file or directory Apr 22 18:38:28 vps622713 apachectl[9437]: Action 'start' failed. Apr 22 18:38:28 vps622713 apachectl[9437]: The Apache error log may have more in formation. Apr 22 18:38:28 vps622713 systemd[1]: apache2.service: Control process e xited, code=exited status=1 Apr 22 18:38:28 vps622713 systemd[1]: Failed to start The Apache HTTP Se --More-- these are the apache2 error files Which one can I send you? access access.log.1 error error.log.1 other_vhosts_access other_vhosts_access.log.1
the journalctl -xe command outputs this root@vps622713:~# journalctl -xe -- Logs begin at Fri 2022-04-22 09:41:29 CEST, end at Fri 2022-04-22 18:53:02 CE ST. -- Apr 22 18:12:41 vps622713 freshclam[907]: Fri Apr 22 18:12:41 2022 -> ^downloadF ile: Unexpected response (403) from https://database.clamav.net/daily-26440.cdif f Apr 22 18:12:41 vps622713 freshclam[907]: Fri Apr 22 18:12:41 2022 -> ^getpatch: Can't download daily-26440.cdiff from https://database.clamav.net/daily-26440.c diff Apr 22 18:12:42 vps622713 freshclam[907]: Fri Apr 22 18:12:42 2022 -> ^downloadF ile: Unexpected response (403) from https://database.clamav.net/daily-26440.cdif f Apr 22 18:12:42 vps622713 freshclam[907]: Fri Apr 22 18:12:42 2022 -> ^getpatch: Can't download daily-26440.cdiff from https://database.clamav.net/daily-26440.c diff Apr 22 18:12:42 vps622713 freshclam[907]: Fri Apr 22 18:12:42 2022 -> ^downloadF ile: Unexpected response (403) from https://database.clamav.net/daily-26440.cdif f Apr 22 18:12:42 vps622713 freshclam[907]: Fri Apr 22 18:12:42 2022 -> ^getpatch: Can't download daily-26440.cdiff from https://database.clamav.net/daily-26440.c diff Apr 22 18:12:42 vps622713 freshclam[907]: Fri Apr 22 18:12:42 2022 -> ^Increment al update failed, trying to download daily.cvd Apr 22 18:12:42 vps622713 freshclam[907]: Fri Apr 22 18:12:42 2022 -> ^downloadF --More--
Hi Jesse Is it possible to continue with your help to fix this problem? WHICH ERROR FILE DO YOU NEED DATA?
Does that host have a properly working connection to the Internet? It is difficult to help you when you do not answer questions and make video files of the text a command prints. Try to avoid doing those. So, paste the command output as text in CODE tags, the editor on this forum has in Instert icon tags for that. Even if the common issues script can not be downloaded to your host, you should still read this article: https://www.howtoforge.com/community/threads/please-read-before-posting.58408/ Now to see if connection to Internet works, ping some host that surely is up and answers to ping, for example do these two commands: Code: ping -c 3 8.8.8.8 ping -c 3 ping.funet.fi And paste the output here as text in CODE tags. Then these commands and again paste as text in CODE tags: Code: systemctl --state=failed Code: lsb_release -a cat /etc/debian_version Code: uptime free -h df -hT
Hi Taleman ping -c 3 ping.funet.fi Outcome PING ns-secondary.funet.fi (128.214.248.132) 56(84) bytes of data. 64 bytes from ns-secondary.funet.fi (128.214.248.132): icmp_seq=1 ttl=49 time=29.2 ms 64 bytes from ns-secondary.funet.fi (128.214.248.132): icmp_seq=2 ttl=49 time=29.3 ms 64 bytes from ns-secondary.funet.fi (128.214.248.132): icmp_seq=3 ttl=49 time=29.3 ms --- ns-secondary.funet.fi ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 29.295/29.343/29.375/0.200 ms ping -c 3 8.8.8.8 Outcome PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=110 time=4.99 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=110 time=7.01 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=110 time=5.08 ms --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 4.993/5.699/7.018/0.933 ms systemctl --state=failed Outcome UNIT LOAD ACTIVE SUB DESCRIPTION ● apache2.service loaded failed failed Th e Apache HTTP Server ● clamav-daemon.service loaded failed failed Cl am AntiVirus userspace daemon LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 2 loaded units listed. Pass --all to see loaded but inactive units, t oo. To show all installed unit files use 'systemctl list-unit-files' lsb_release -a Outcome No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.13 (stretch) Release: 9.13 Codename: stretch cat /etc/debian_version Outcome 9.13 uptime Outcome 19:09:10 up 5 days, 9:15, 1 user, load average: 0.23, 0.17, 0.22 free -h Outcome total used free shared buff/cache available Mem: 1.9G 648M 86M 36M 1.2G 1.1G Swap: 0B 0B 0B df -hT Outcome Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 967M 0 967M 0% /dev tmpfs tmpfs 196M 21M 176M 11% /run /dev/sda1 ext4 20G 16G 3.7G 81% / tmpfs tmpfs 979M 0 979M 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 979M 0 979M 0% /sys/fs/cgroup /dev/loop3 squashfs 111M 111M 0 100% /snap/core/12834 /dev/loop4 squashfs 44M 44M 0 100% /snap/certbot/1888 /dev/loop1 squashfs 112M 112M 0 100% /snap/core/12941 /dev/loop2 squashfs 62M 62M 0 100% /snap/core20/1405 /dev/loop0 squashfs 44M 44M 0 100% /snap/certbot/1952
