We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
error 500 on https after update
-
- Posts: 4
- Joined: Fri Aug 25, 2017 1:10 pm
- Os: Ubuntu 15x
- Web: apache + nginx
error 500 on https after update
I was using vesta on auto update mode and with the last update every https website is returning a 500 error.
I´m using Ubuntu 16.04.2 and vesta 0.9.8 release 18.
I´ve already tried to recreate the user, disable and enable ssl certificate for the domain, restart web, restart server.
here is the apache error log for my domain:
Anybody has a similar issue?
Thanks.
I´m using Ubuntu 16.04.2 and vesta 0.9.8 release 18.
I´ve already tried to recreate the user, disable and enable ssl certificate for the domain, restart web, restart server.
here is the apache error log for my domain:
Code: Select all
2018/01/05 19:03:02 [error] 8043#8043: *162 SSL_do_handshake() failed (SSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol) while SSL handshaking to upstream, client: 177.45.131.20, server: brunomagrini.com.br, request: "GET / HTTP/1.1", upstream: "https://176.31.254.186:8443/", host: "brunomagrini.com.br"
2018/01/05 19:03:02 [error] 8043#8043: *162 SSL_do_handshake() failed (SSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol) while SSL handshaking to upstream, client: 177.45.131.20, server: brunomagrini.com.br, request: "GET /favicon.ico HTTP/1.1", upstream: "https://176.31.254.186:8443/favicon.ico", host: "brunomagrini.com.br", referrer: "https://brunomagrini.com.br/"
Thanks.
Re: error 500 on https after update
Same problem. Anybody can help?
Re: error 500 on https after update
have you tried upgrading the system you are using?
normally such an error only applies if you are having problems with creating the ssl connection with an endpoint that want to have an encryption your server can't handle
ergo don't answer with a HELO after SSL
normally the server is backwards compatible; but perhaps in the 18 release they have changed some security settings?
normally such an error only applies if you are having problems with creating the ssl connection with an endpoint that want to have an encryption your server can't handle
ergo don't answer with a HELO after SSL
normally the server is backwards compatible; but perhaps in the 18 release they have changed some security settings?
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: error 500 on https after update
update & upgrade your server to latest updates
restart apache or restart full server once
"rebuild web" for the website
restart apache or restart full server once
"rebuild web" for the website
-
- Posts: 4
- Joined: Fri Aug 25, 2017 1:10 pm
- Os: Ubuntu 15x
- Web: apache + nginx
Re: error 500 on https after update
Hello,
The error we were getting seamed like a nginx configuration problem but I cannot tell exactly what was. After a lot of attempts what solved our problem was running v-update-web-templates.
The error we were getting seamed like a nginx configuration problem but I cannot tell exactly what was. After a lot of attempts what solved our problem was running v-update-web-templates.
Re: error 500 on https after update
While using SSL, you need dedicated IP address per vHost (this example clearly show the request has been sent to the localhost IP. You probably have the wrong IP set in proxy_pass statement).
1. Ensure the Apache vHost/site is responding on the non-standard port (browse to : https://www.domain.tld:8443).
2. If its loading properly, then note the IP address contained within <VirtualHost 0.0.0.0:8443> of your SSL vHost, otherwise double check your Apache configuration.
3. Under your Nginx SSL vHost configuration, make sure the same IP address is in that statement “proxy_pass https://0.0.0.0:8443;“.
1. Ensure the Apache vHost/site is responding on the non-standard port (browse to : https://www.domain.tld:8443).
2. If its loading properly, then note the IP address contained within <VirtualHost 0.0.0.0:8443> of your SSL vHost, otherwise double check your Apache configuration.
3. Under your Nginx SSL vHost configuration, make sure the same IP address is in that statement “proxy_pass https://0.0.0.0:8443;“.