Server-wide cert not working for cgi-bin
What could be missing?
We get "not found" when attempting to use a perl script loaded in an account's cgi-bin under the "shared" ssl.
<-- "not found"
Is it looking for a symbolic link 'cathyweb' to be in the /usr/local/apache/htdocs folder? How is it working then anyway for pages outside of the cgi-bin ? Why doesn't the server place this link at account creation time if it's necessary and userdir has been enabled?
Is it looking for a symbolic link 'cathyweb' to be in the /usr/local/apache/htdocs folder? How is it working then anyway for pages outside of the cgi-bin ? Why doesn't the server place this link at account creation time if it's necessary and userdir has been enabled?
-
The reason is hundreds of legacy clients who have been using shared cert to protect their contact forms and the like for years .... It was *OUR* decision to shut down an older server with a competing panel and migrate the accounts to a cpanel server. We're not about to force all those clients to purchase SSL, nor to cover that expense ourselves. Let's Encrypt can't be integrated soon enough. ;) We've since found under the shared SSL that DirectoryIndex is not working either... in case it helps diagnose in case it's related? <-- "not found" 0 -
Hello :) What PHP handler is enabled on this server? Have you verified the CGI files have 0755 permissions? This document also may help: Per-user web directories - Apache HTTP Server Version 2.4 Thank you. 0 -
suphp and suexec The CGI scripts have 755 else they wouldn't work for the domain proper. It seems we can easily fix this by creating symbolic links like /usr/local/apache/htdocs/cathyweb -> /home/cathyweb/public_html Yet it seems like it is an incorrect configuration rather than missing links since calling pages outside of the cgi-bin works perfectly fine without such a link. 0 -
Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you. 0
Please sign in to leave a comment.
Comments
5 comments