• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

All Websites on the server is down

Kingsley

Kingsley

Silver Pleskian
Hello;

I recently move to plesk and everything is working after for 8 days now and suddenly all domains went offline. i know i should restart the server but what went wrong? what if i start restarting server every 9 days?

below is the only change i made in other to add the second IP.

Original networ code

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

iface eth0 inet6 auto
dns-nameservers 2001:19f0:300:1704::6

Edited with the second IP

Code: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo
    iface lo inet loopback

auto eth0
iface eth0 inet static
    address 45.32.193.30
    netmask 255.255.254.0
    gateway 45.32.192.1
    dns-nameservers 108.61.10.10
    post-up ip route add 169.254.0.0/16 dev eth0


auto eth0:1
iface eth0:1 inet static
    address 108.61.224.218
    netmask 255.255.255.0

#The IPV6 network interface
iface eth0 inet6 auto
dns-nameservers 2001:19f0:300:1704::6

Please i need help before restarting the server
 
Hello;

I think it's network issue, i just change the DNS to DO and it loads(plesk panel ofcourse)
 
Kingsley said:
Hello;

I think it's network issue, i just change the DNS to DO and it loads(plesk panel ofcourse)
Click to expand...

@Kingsley,

It would be nice to explain what you exactly did to get your system working, that would be beneficial for other forum members.

Please explain.

Regards...
 
trialotto said:
@Kingsley,

It would be nice to explain what you exactly did to get your system working, that would be beneficial for other forum members.

Please explain.

Regards...
Click to expand...

Hello,

It's not working after restarting the server it worked for few minutes and then went offline (all the domains are offline and unaccessible)
 
domains are not accessible they won't open but the server and everything is running this very frustrating
 
trialotto said:
@Kingsley,

It would be nice to explain what you exactly did to get your system working, that would be beneficial for other forum members.

Please explain.

Regards...
Click to expand...

I need help here please

k12o1w.png
 
If it is really urgent problem, asking assistance of Support Team would be much more effective solution.
 
IgorG said:
Yes. Support guys will check and fix this issue directly on your server. I suppose it is really more effective and faster than discussions on the forum.
Click to expand...

I will take that into consideration when i have $100+ to spend

Thanks
 
@Kingsley,

Can you provide your default nginx configuration file? That is, the /etc/nginx/nginx.conf file.

Anyway, make sure that you verify that the commands

- service plesk-php55-fpm status
- service plesk-php56-fpm status
- service plesk-php70-fpm status

indicate that the service is running for at least those FPM handlers that you used on the specific sites. If the required FPM handler is not running, just start them.

Also run the command: service php5-fpm status

The latter command is to check for the status of the FPM handler for the default "vendor package" of PHP.

Afterwards, do the command: nginx reload && service nginx restart (just to be sure).

Hope the above helps, but I am pretty sure that we still have to deal with some other underlying and/or associated issues.

Note that all relevant output is required, in order to allow us to have a look at the problem (otherwise, it would be simply guessing or even impossible).

Regards........
 
trialotto said:
@Kingsley,

Can you provide your default nginx configuration file? That is, the /etc/nginx/nginx.conf file.

Anyway, make sure that you verify that the commands

- service plesk-php55-fpm status
- service plesk-php56-fpm status
- service plesk-php70-fpm status

indicate that the service is running for at least those FPM handlers that you used on the specific sites. If the required FPM handler is not running, just start them.

Also run the command: service php5-fpm status

The latter command is to check for the status of the FPM handler for the default "vendor package" of PHP.

Afterwards, do the command: nginx reload && service nginx restart (just to be sure).

Hope the above helps, but I am pretty sure that we still have to deal with some other underlying and/or associated issues.

Note that all relevant output is required, in order to allow us to have a look at the problem (otherwise, it would be simply guessing or even impossible).

Regards........
Click to expand...

Hello;

Thanks for replying me, right now everything is down...

Default Nginx

Code: 
#user  nginx;
worker_processes  1;

#error_log  /var/log/nginx/error.log;
#error_log  /var/log/nginx/error.log  notice;
#error_log  /var/log/nginx/error.log  info;

#pid        /var/run/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;
    #tcp_nodelay        on;

    #gzip  on;
    #gzip_disable "MSIE [1-6]\.(?!.*SV1)";

    server_tokens off;

    include /etc/nginx/conf.d/*.conf;
}

# override global parameters e.g. worker_rlimit_nofile
include /etc/nginx/*global_params;

EDITED NGINX

Code: 
#user  nginx;
worker_processes  4;
worker_rlimit_nofile 50000;

#error_log  /var/log/nginx/error.log;
#error_log  /var/log/nginx/error.log  notice;
#error_log  /var/log/nginx/error.log  info;

#pid        /var/run/nginx.pid;


events {
    worker_connections  1024;
    use epoll;
    multi_accept on;
}


http {

    fastcgi_buffers 8 128k;
    fastcgi_buffer_size 256k;
    fastcgi_read_timeout 600;
    fastcgi_send_timeout 600;
    proxy_connect_timeout       600;
    proxy_send_timeout          600;
    proxy_read_timeout          600;
    send_timeout                600;
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  /var/log/nginx/access.log  main;

    sendfile        on;
    tcp_nopush      on;
    tcp_nodelay     on;

    keepalive_timeout  65;
    keepalive_requests 256;
    reset_timedout_connection on;

    gzip         on;
    gzip_disable "MSIE [1-6]\.(?!.*SV1)";
    gzip_proxied any;
    gzip_comp_level 6;
    #gzip_min_length  1000;
    gzip_types   text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript image/x-icon image/bmp image/svg+xml;
    gzip_vary    on;
    server_tokens off;

    open_file_cache max=50000 inactive=20s;
    open_file_cache_valid 30s;
    open_file_cache_min_uses 2;

    client_max_body_size 512m;

    include /etc/nginx/conf.d/*.conf;
}

# override global parameters e.g. worker_rlimit_nofile
include /etc/nginx/*global_params;
 
Here are the results for PHP status

Code: 
~# service plesk-php55-fpm status
plesk-php55-fpm: unrecognized service

~# service plesk-php56-fpm status
*  is running

# service plesk-php70-fpm status
*  is running

~# service php5-fpm status
php5-fpm start/running, process 1115
 
@Kingsley

Your edit of Nginx config files is the very likely culprit of the sites being down.

Can you also output the *global_params files?

Regards
 
Kingsley said:
healthable.org

Code: 
2016-03-09 22:33:04    Error    5.104.241.192    AH01070: Error parsing script headers    Apache error
2016-03-09 22:33:23    Error    197.242.101.41    AH01070: Error parsing script headers    Apache error
2016-03-09 23:04:43    Error    197.242.101.41    AH01070: Error parsing script headers    Apache error
2016-03-09 23:05:29    Error    81.152.59.140    AH01070: Error parsing script headers, referer: http://www.healthable.org/top-4-reasons-dental-crowns-keep-breaking/    Apache error
2016-03-09 23:05:29    Error    81.152.59.140    AH01068: Got bogus version 1, referer: http://www.healthable.org/top-4-reasons-dental-crowns-keep-breaking/    Apache error
2016-03-09 23:05:29    Error    81.152.59.140    (22)Invalid argument: AH01075: Error dispatching request to :, referer: http://www.healthable.org/top-4-reasons-dental-crowns-keep-breaking/    Apache error
2016-03-09 23:14:26    Error    209.59.141.140    AH01070: Error parsing script headers    Apache error
2016-03-09 23:15:37    Error    41.189.160.47    AH01070: Error parsing script headers, referer: http://www.healthable.org/happy-womens-day-be-proud-as-a-woman/    Apache error
2016-03-09 23:15:56    Error    41.189.160.47    AH01070: Error parsing script headers, referer: http://www.healthable.org/happy-womens-day-be-proud-as-a-woman/    Apache error
2016-03-09 23:24:00    Error    46.165.195.139    4941#0: *46552 upstream timed out (110: Connection timed out) while reading response header from upstream    nginx error
2016-03-09 23:24:01    Error    67.228.213.178    4941#0: *46554 upstream timed out (110: Connection timed out) while reading response header from upstream    nginx error
2016-03-09 23:25:52    Error    66.249.65.20    4941#0: *46676 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:27:42    Error    115.178.254.84    4941#0: *46798 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:27:52    Error    70.167.36.130    4941#0: *46806 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:29:29    Error    115.178.254.84    4941#0: *46798 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:30:49    Error    41.189.161.42    4941#0: *46999 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:30:53    Error    121.97.6.11    4941#0: *47007 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:32:21    Error    50.87.144.96    4941#0: *47095 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:32:40    Error    121.97.6.11    4941#0: *47007 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:32:41    Error    121.97.6.11    4941#0: *47110 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:32:53    Error    66.249.65.20    4941#0: *47120 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:34:28    Error    121.97.6.11    4941#0: *47110 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:34:50    Error    66.249.65.20    4941#0: *47120 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:35:55    Error    202.45.119.39    4941#0: *47316 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:36:36    Error    66.249.65.20    4941#0: *47120 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:37:42    Error    202.45.119.39    4941#0: *47316 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:38:23    Error    66.249.90.9    4941#0: *47512 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:40:07    Error    41.189.161.33    4943#0: *47636 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:41:57    Error    66.249.90.9    4943#0: *47753 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:42:40    Error    66.87.98.248    4943#0: *47807 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:43:10    Error    73.244.32.44    4943#0: *47843 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:43:51    Error    66.249.65.20    4943#0: *47876 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:45:08    Error    37.105.214.91    4943#0: *47963 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:45:49    Error    66.249.65.20    4943#0: *47876 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:47:50    Error    66.249.65.20    4943#0: *47876 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:52:19    Error    108.172.93.181    4943#0: *48396 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:52:29    Error    81.85.71.60    4943#0: *48406 recv() failed (104: Connection reset by peer) while reading response header from upstream
Click to expand...
 
Kingsley said:
mobileif.com

Code: 
2016-03-09 23:17:02    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:05    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:09    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:12    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:16    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/bcgsw    Apache error
2016-03-09 23:17:19    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:23    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:29    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:35    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:39    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/bcgsw    Apache error
2016-03-09 23:17:42    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:46    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:50    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:54    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:17:58    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/bcgsw    Apache error
2016-03-09 23:18:01    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:04    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:08    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:11    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:17    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/bcgsw    Apache error
2016-03-09 23:18:20    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:24    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:28    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:31    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/    Apache error
2016-03-09 23:18:35    Error    144.76.61.21    AH01797: client denied by server configuration: /var/www/vhosts/mobileif.com/httpdocs/bcgsw    Apache error
2016-03-09 23:28:06    Error    66.249.73.224    4941#0: *46829 recv() failed (104: Connection reset by peer) while reading response header from upstream    nginx error
2016-03-09 23:48:27    Error    208.87.233.201    4943#0: *48167 recv() failed (104: Connection reset by peer) while reading response header from upstream
Click to expand...
 
You must log in or register to reply here.

Similar threads

L
Question Outgoing mail mode - ipv6
Replies
11
Views
3K
hugosnel
hugosnel
VojinP
Resolved Problem with assigning IPv6 to new server
Replies
4
Views
1K
VojinP
VojinP
Servus
Issue Problem with /etc/network/interfaces and 2 additional IPv4 on Ionos server
Replies
9
Views
4K
carlosarmando85
carlosarmando85
A
Issue Try update Ubuntu 14 to 16 and reboot --> no more ssh / ufw don't work / no ping
Replies
0
Views
933
AxelKirk
A
Dukemaster
Issue Bad code format by adding IPv4 over Plesk Panel
Replies
1
Views
1K
UFHH01
U
Back
Top