Page 1 of 1
http sites won't load after yum update
Posted: Fri Dec 08, 2017 12:39 pm
by umizoomi
Hey, im running the latest vestacp on centos 7. This morning I did a yum update, after that everything on the server loading without ssl isn't working.
See for instance:
http://mmmaxi.me/ it downloads a file with some numbers. however https works fine.
I've tried rebooting, using default nginx proxy config. All doesnt seem to be working.
Could I have updated something that doesnt work with vestacp? As far as I know I dont have anything else running on this VPS
Anyone care to help me out :)?
Thanks!
Re: http sites won't load after yum update
Posted: Fri Dec 08, 2017 12:58 pm
by sysdop
umizoomi wrote:Hey, im running the latest vestacp on centos 7. This morning I did a yum update, after that everything on the server loading without ssl isn't working.
See for instance:
http://mmmaxi.me/ it downloads a file with some numbers. however https works fine.
I've tried rebooting, using default nginx proxy config. All doesnt seem to be working.
Could I have updated something that doesnt work with vestacp? As far as I know I dont have anything else running on this VPS
Anyone care to help me out :)?
Thanks!
@umizoomi which lines are the ones you have in the nginx.conf and snginx.conf located in /home/USER/conf/web?
Are you using Nginx + Php-FPM true? You can try changing the template to Wordpress2, maybe this will solve your problem in most cases.
Re: http sites won't load after yum update
Posted: Tue Dec 12, 2017 4:00 pm
by umizoomi
sysdop wrote:umizoomi wrote:Hey, im running the latest vestacp on centos 7. This morning I did a yum update, after that everything on the server loading without ssl isn't working.
See for instance:
http://mmmaxi.me/ it downloads a file with some numbers. however https works fine.
I've tried rebooting, using default nginx proxy config. All doesnt seem to be working.
Could I have updated something that doesnt work with vestacp? As far as I know I dont have anything else running on this VPS
Anyone care to help me out :)?
Thanks!
@umizoomi which lines are the ones you have in the nginx.conf and snginx.conf located in /home/USER/conf/web?
Are you using Nginx + Php-FPM true? You can try changing the template to Wordpress2, maybe this will solve your problem in most cases.
Hey, I reinstalled the server and vestacp. It worked for a while. but now its giving the same problem again. Heres my nginx config:
Code: Select all
server {
listen 37.97.223.231:443;
server_name rasidi.nl ;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.rasidi.nl.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.rasidi.nl.key;
error_log /var/log/httpd/domains/rasidi.nl.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/rasidi.nl/public_html;
access_log /var/log/httpd/domains/rasidi.nl.log combined;
access_log /var/log/httpd/domains/rasidi.nl.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/rasidi.nl/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.rasidi.nl.conf*;
}
server {
listen 37.97.223.231:443;
server_name mmmaxi.me www.mmmaxi.me;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.mmmaxi.me.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.mmmaxi.me.key;
error_log /var/log/httpd/domains/mmmaxi.me.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/mmmaxi.me/public_html;
access_log /var/log/httpd/domains/mmmaxi.me.log combined;
access_log /var/log/httpd/domains/mmmaxi.me.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/mmmaxi.me/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.mmmaxi.me.conf*;
}
server {
listen 37.97.223.231:443;
server_name dewoudbloem.nl www.dewoudbloem.nl;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.dewoudbloem.nl.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.dewoudbloem.nl.key;
error_log /var/log/httpd/domains/dewoudbloem.nl.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/dewoudbloem.nl/public_html;
access_log /var/log/httpd/domains/dewoudbloem.nl.log combined;
access_log /var/log/httpd/domains/dewoudbloem.nl.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/dewoudbloem.nl/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.dewoudbloem.nl.conf*;
}
server {
listen 37.97.223.231:443;
server_name melodyboorsma.nl www.melodyboorsma.nl;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.melodyboorsma.nl.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.melodyboorsma.nl.key;
error_log /var/log/httpd/domains/melodyboorsma.nl.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/melodyboorsma.nl/public_html;
access_log /var/log/httpd/domains/melodyboorsma.nl.log combined;
access_log /var/log/httpd/domains/melodyboorsma.nl.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/melodyboorsma.nl/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.melodyboorsma.nl.conf*;
}
server {
listen 37.97.223.231:443;
server_name jamil.io www.jamil.io;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.jamil.io.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.jamil.io.key;
error_log /var/log/httpd/domains/jamil.io.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/jamil.io/public_html;
access_log /var/log/httpd/domains/jamil.io.log combined;
access_log /var/log/httpd/domains/jamil.io.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/jamil.io/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.jamil.io.conf*;
}
server {
listen 37.97.223.231:443;
server_name swagmail.nl www.swagmail.nl;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.swagmail.nl.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.swagmail.nl.key;
error_log /var/log/httpd/domains/swagmail.nl.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/swagmail.nl/public_html;
access_log /var/log/httpd/domains/swagmail.nl.log combined;
access_log /var/log/httpd/domains/swagmail.nl.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/swagmail.nl/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.swagmail.nl.conf*;
}
server {
listen 37.97.223.231:443;
server_name swekt.nl www.swekt.nl;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.swekt.nl.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.swekt.nl.key;
error_log /var/log/httpd/domains/swekt.nl.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/swekt.nl/public_html;
access_log /var/log/httpd/domains/swekt.nl.log combined;
access_log /var/log/httpd/domains/swekt.nl.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/swekt.nl/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.swekt.nl.conf*;
}
server {
listen 37.97.223.231:443;
server_name taartartnederland.nl www.taartartnederland.nl;
ssl on;
ssl_certificate /home/mcjambi/conf/web/ssl.taartartnederland.nl.pem;
ssl_certificate_key /home/mcjambi/conf/web/ssl.taartartnederland.nl.key;
error_log /var/log/httpd/domains/taartartnederland.nl.error.log error;
location / {
proxy_pass https://37.97.223.231:8443;
location ~* ^.+\.(jpeg|jpg|png|gif|bmp|ico|svg|tif|tiff|css|js|htm|html|ttf|otf|webp|woff|txt|csv|rtf|doc|docx|xls|xlsx|ppt|pptx|odf|odp|ods|odt|pdf|psd|ai|eot|eps|ps|zip|tar|tgz|gz|rar|bz2|7z|aac|m4a|mp3|mp4|ogg|wav|wma|3gp|avi|flv|m4v|mkv|mov|mpeg|mpg|wmv|exe|iso|dmg|swf)$ {
root /home/mcjambi/web/taartartnederland.nl/public_html;
access_log /var/log/httpd/domains/taartartnederland.nl.log combined;
access_log /var/log/httpd/domains/taartartnederland.nl.bytes bytes;
expires max;
try_files $uri @fallback;
}
}
location /error/ {
alias /home/mcjambi/web/taartartnederland.nl/document_errors/;
}
location @fallback {
proxy_pass https://37.97.223.231:8443;
}
location ~ /\.ht {return 404;}
location ~ /\.svn/ {return 404;}
location ~ /\.git/ {return 404;}
location ~ /\.hg/ {return 404;}
location ~ /\.bzr/ {return 404;}
include /home/mcjambi/conf/web/snginx.taartartnederland.nl.conf*;
}
Re: http sites won't load after yum update
Posted: Thu Dec 14, 2017 1:42 pm
by skurudo
will show is or not problems with configs.
PS: Sites from config looks fine, what problem was ?