Author Topic: Error 500 after SSL with Letsencrypt  (Read 15424 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Error 500 after SSL with Letsencrypt
« on: July 08, 2016, 09:29:54 AM »
Hello together,
I just tried Letsencrypt . but this I always get Error 500 when I want to access the page with https . With http it works . Does somebody has any idea?

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #1 on: July 08, 2016, 10:01:42 AM »
I have:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.


Error log shows me:

[Fri Jul 08 12:06:12 2016] [error] [client 109.175.***.***] No user or group set - set suPHP_UserGroup

what your error log's show?

Checked config files few time but didn't find any problem in them or in permissions or owners.
« Last Edit: July 08, 2016, 10:05:37 AM by zakrpa »

Offline
*****
Re: Error 500 after SSL with Letsencrypt
« Reply #2 on: July 08, 2016, 12:23:24 PM »
go to cwp dashboard >> user account >>> fic permission >>>> select your website's user >>>>> hit fix permission

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #3 on: July 08, 2016, 03:21:56 PM »
It does not work

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #4 on: July 09, 2016, 08:27:13 AM »
Hello
I checked everything seems fine with permissions and owners group. and for just to be 100% I did fixing permissions in panel but did not fork. strange.

After installation port 443 was closed does it have some problems because I use varnish and apache?
Can I just open in configuration like port 80 with line: Listen 443?

Regards
« Last Edit: July 09, 2016, 11:16:42 AM by zakrpa »

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #5 on: July 10, 2016, 01:19:23 AM »
The error log shows a usergroup issue, so I edited the apache letsencrypt vhosts file, and inside the directory tags, added the suPHP_UserGroup line.

Example:

<Directory "/home/xx/public_html">
    AllowOverride All
    suPHP_UserGroup xx xx
</Directory>

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #6 on: July 10, 2016, 01:34:09 AM »
yes you can open a port 443 by simply adding Listen 443 in apache configuration.
usergroups exists in configuration so its strange that is missing in your apache vhost file letsencrypt.conf
AntiDDoS Protection (web + mail)
http://centos-webpanel.com/website-ddos-protection-proxy

Join our Development Team and get paid !
http://centos-webpanel.com/develope-modules-for-cwp


Services Monitoring & RBL Monitoring
http://centos-webpanel.com/services-monitor


Do you need Fast and FREE Support included for your CWP linux server?
http://centos-webpanel.com/noc-partner-list
Installation Instructions
http://centos-webpanel.com/installation-instructions
Get Fast Support Here
http://centos-webpanel.com/support-services

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #7 on: July 10, 2016, 09:16:47 AM »
The error log shows a usergroup issue, so I edited the apache letsencrypt vhosts file, and inside the directory tags, added the suPHP_UserGroup line.

Example:

<Directory "/home/xx/public_html">
    AllowOverride All
    suPHP_UserGroup xx xx
</Directory>

did work after that?

Ok edited and worked fine but seem when I checked all vhosts file there is nowhere defined suphp_usergroup for directory :)

Thanks its working now
« Last Edit: July 10, 2016, 09:31:04 AM by zakrpa »

Offline
***
Re: Error 500 after SSL with Letsencrypt
« Reply #8 on: July 21, 2016, 09:50:34 AM »
Try this
Go to the home folder (replace your username account)
cd /home/user_name/public_html

Fix permission of folders
find ./ -type d -exec chmod 755 {} \;

Fix permission of files
find ./ -type f -exec chmod 644 {} \;

Offline
*
Re: Error 500 after SSL with Letsencrypt
« Reply #9 on: May 25, 2017, 09:00:12 AM »
The error log shows a usergroup issue, so I edited the apache letsencrypt vhosts file, and inside the directory tags, added the suPHP_UserGroup line.

Example:

<Directory "/home/xx/public_html">
    AllowOverride All
    suPHP_UserGroup xx xx
</Directory>


thank you so much . my problem was solved by this code