New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Have you tried contacting GVH? There are many reasons why you are receiving that message with that little information.
IPtables? port 80.
run
iptables -F
Then try your site.
Should work.
After that learn how to configure iptables properly.
Should totally work in case for example the HTTP server has crashed, yeah.
That'll help immensely too.
online in control panel. but can you ssh it?
there can be several reasons. I faced this situation and the cause were, dns crashed, apache crashed, port 80 or 443 used by another aplication and makes the apache failed to start. are you using cpanel?
iptables v1.4.7: no command specified
Try `iptables -h' or 'iptables --help' for more information.
Yes, Vesta CP. It has been working perfectly, before the provider has ddos attack.
could you verify the apache with php and the dns are working?
this happened to me the other day. I installed lighttpd, and it wouldn't load. I restarted it, and it said it had started successfully but still wouldn't load in a browser. it ended up being because apache was installed, even though it wasn't running, and when I removed apache and started lighttpd it worked again. no idea why.
I have not changing anything on my VPS...
I'm assuming you were expecting to see a site on port 80, so the issue would have been that if Apache was installed first, it would have taken port 80. Removing Apache and restarting Lighttpd would have fixed the issue for you, as Lighttpd would have been able to listen on 80 with Apache gone.
OP, why not try restarting Apache manually and see if you receive any error message?
Vestacp disables iptables & Selinux (under 1gb ram) as default. Suggested minimal centos. It wouldn't even install without a "-f" if anything that it is going to depend on or conflict is present and reconfigures the entire system to what is required, so it is good to go from the start without any additional reconfiguring.
So, it should be a VPS networking issue rather than what you've done with the vps itself
EDIT
The below are the processes running on a default vestacp server, "top" and compare, all (most) of these should be running.
1162 apache 20 0 78796 9744 3736 S 1.3 1.9 0:00.35 httpd 1039 mysql 20 0 343m 33m 6148 S 0.7 6.6 0:02.94 mysqld 1 root 20 0 2900 1368 1184 S 0.0 0.3 0:00.01 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd/9882 3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper/9882 135 root 16 -4 2464 568 332 S 0.0 0.1 0:00.00 udevd 494 root 20 0 35972 1364 1036 S 0.0 0.3 0:00.00 rsyslogd 507 named 20 0 71400 10m 2720 S 0.0 2.0 0:00.00 named 522 dbus 20 0 3000 860 668 S 0.0 0.2 0:00.00 dbus-daemon 534 root 20 0 8944 1044 540 S 0.0 0.2 0:00.00 sshd 544 root 20 0 7176 644 268 S 0.0 0.1 0:00.00 vsftpd 580 root 20 0 3044 1324 1120 S 0.0 0.3 0:00.02 mysqld_safe 1076 root 20 0 2876 776 592 S 0.0 0.1 0:00.00 dovecot 1078 dovecot 20 0 2740 980 836 S 0.0 0.2 0:00.00 anvil 1079 root 20 0 2736 1044 820 S 0.0 0.2 0:00.00 log 1084 root 20 0 3872 2192 868 S 0.0 0.4 0:00.00 config 1092 exim 20 0 15100 1380 720 S 0.0 0.3 0:00.00 exim 1111 root 20 0 78128 13m 8408 S 0.0 2.5 0:00.16 httpd 1121 root 20 0 28436 1096 448 S 0.0 0.2 0:00.00 nginx 1122 nginx 20 0 28588 1428 568 S 0.0 0.3 0:00.19 nginx 1123 nginx 20 0 28916 2184 980 S 0.0 0.4 0:00.05 nginx 1124 nginx 20 0 28440 1328 576 S 0.0 0.3 0:00.01 nginx 1132 root 20 0 17820 876 304 S 0.0 0.2 0:00.00 vesta-nginx 1133 admin 20 0 17820 1004 420 S 0.0 0.2 0:00.00 vesta-nginx 1136 root 20 0 13572 2056 864 S 0.0 0.4 0:00.07 vesta-php 1137 admin 20 0 13572 1720 520 S 0.0 0.3 0:00.00 vesta-php 1138 admin 20 0 13572 1720 520 S 0.0 0.3 0:00.00 vesta-php 1144 root 20 0 3956 1204 644 S 0.0 0.2 0:00.01 crond 1152 root 20 0 2008 500 444 S 0.0 0.1 0:00.00 mingetty 1153 root 20 0 2008 500 444 S 0.0 0.1 0:00.00 mingetty 1155 apache 20 0 79316 10m 3728 S 0.0 2.0 0:00.48 httpd 1156 apache 20 0 78804 9988 3980 S 0.0 1.9 0:00.25 httpd 1157 apache 20 0 78808 9980 3964 S 0.0 1.9 0:00.20 httpd 1158 apache 20 0 78792 9956 3952 S 0.0 1.9 0:00.40 httpd 1159 apache 20 0 78808 9976 3960 S 0.0 1.9 0:00.32 httpd 1160 apache 20 0 78804 9932 3924 S 0.0 1.9 0:00.19 httpd 1161 apache 20 0 78796 9980 3976 S 0.0 1.9 0:00.23 httpd 4483 root 20 0 11996 3808 3048 S 0.0 0.7 0:00.04 sshd 4485 root 20 0 3048 1544 1312 S 0.0 0.3 0:00.00 bash 4724 root 20 0 2568 1076 880 R 0.0 0.2 0:00.00 topBut how can I solve this situation please?
fix it yourself, by google or find some website admin, but not here just ask HOWTO without any first investigation.
Kovacsak,
Can you restart your web server application and see if there are any errors when starting up. According to your other thread I saw the IP address to the VPS in question and everything is working except port 80/443. Also when someone told you to try iptables -F that was good advice but it seems you didn't type it in correctly. make sure you type exactly 'iptables -F' as root. If everything starts up fine can you post an output for netstat -anp | grep apache. Also what exact OS are you running.
Good Luck!
take a backup of your website... Reinstall os (Centos minimal 6.5 works the best and the safest best) run ... and reinstall vestacp... dont tweak / configure anything else. if it doesnt work still... then you can be sure your vps wasnt configured correctly...
Doing all this shouldnt take you than 20-25 minutes from the starting the reinstall... much quicker than trying to troubleshoot
Not a techie... but starting from a clean state is the best way to go
If you are going to do all that try simply restarting the VPS First! =P
obviously...
you checked logs?
There is an error meassage, when I would like to start httpd:
[Tue Sep 16 12:28:16 2014] [warn] NameVirtualHost 23.95.50.5:8443 has no VirtualHosts
Update: I have fixed this:
[root@vps /]# service httpd start
Starting httpd: [ OK ]
Are you deliberately trying to run a site on port 8443?
It is already fixed, I updated the post.
So your site is running and you've apologised to GVH Support?
No, sorry, because I have tried after that to restart my server and it is not start properly 20 minutes ago. Not that great!
I honestly think OP doesn't know how to configure Apache.
It's not GVH fault here.
VestaCP is using apache and nginx as a cache
It is OK, problem is solved, but I can not restart my server. After it is stopped it can not start properly.
Your VPS is up, I just pinged it.
you should pay much more to buy a "Managed" VPS, then everything you can find the support to fix for you.