Internal 500 error after v1.7.8 upgrade

Community Support
1

Hi Hestia Support forum
I’ve found myself in a pickle after upgrading to v1.7.8
I followed some threads and found out that both Apache and Nginx had an issue with the ports.conf file.

I’ve followed the fix by restoring the old ports.conf file and now I get an internal 500 error
I ran the command below and the following results were returned:

root@hcp:~# netstat -tulpn | grep :80
tcp 0 0 10.0.0.xxx:80 0.0.0.0:* LISTEN 1092/nginx: master
tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 1046/nginx: master
tcp 0 0 127.0.0.1:8081 0.0.0.0:* LISTEN 4438/apache2
tcp 0 0 127.0.0.1:8084 0.0.0.0:* LISTEN 1092/nginx: master
tcp6 0 0 :::8080 :::* LISTEN 4438/apache2

I read that the virtual host should be on port 8085. I’m running on Ubuntu 20.04.4 LTS at the moment. Is there a support resource available which addresses this issue?

Thanks for the assist

2

Hi everyone,

Fixed the issue with the internal 500 server error.
I restored the old apache2.conf file and my websites are functioning again.
I’m assuming that the apache2 upgrade changed some directives in the *.conf file that is not compatible systemwide. Would have to study the old and new files to see the differences.

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.